RAN Reconfiguration Guide(RAN11.0_01)

7/27/2019 RAN Reconfiguration Guide(RAN11.0_01)

http://slidepdf.com/reader/full/ran-reconfiguration-guideran11001 1/103

RAN

11.0

Reconfiguration Guide

Issue 01

Date 2009-02-10

Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.



Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any

assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but the statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and Confidential


http://www.huawei.com/



Contents

About This Document.....................................................................................................................1

1 Changes in RAN Reconfiguration Guide..............................................................................1-1

2 RAN Reconfig uration Introduction........................................................................................2-1

2.1 RAN Reconfiguration Definition....................................................................................................................2-2

2.2 RAN Reconfiguration Tools...........................................................................................................................2-2

2.3 RAN Reconfiguration Process........................................................................................................................2-3

3 Reconfiguring the NodeB.........................................................................................................3-1

3.1 Changing the Local IP Address of a NodeB...................................................................................................3-2

3.2 Setting the IP Address of the NodeB LMT PC...............................................................................................3-2

4 Reconfiguring the RNC............................................................................................................4-1

4.1 Switching the MSC/SGSN/RNC to Another Port on an RNC........................................................................4-2

4.2 Setting the Ad justment Mode of RNC Fan Speed..................................................................... .....................4-3

4.3 Reconfiguring RNC Areas..............................................................................................................................4-3

4.3.1 Adding a Location Area.........................................................................................................................4-4

4.3.2 Adding a Routing Area..........................................................................................................................4-5

4.3.3 Adding a Service Area...........................................................................................................................4-5

4.3.4 Adding a UTRAN Registration Area.....................................................................................................4-6

4.3.5 Modifying a Location Area Code...........................................................................................................4-7

4.3.6 Modifying a Routing Area Code............................................................................................................4-8

4.3.7 Modifying a Service Area Code.............................................................................................................4-9

4.3.8 Modifying a UTRAN Registration Area ID...........................................................................................4-9

4.3.9 Modifying the Value Range of a PLMN Tag.......................................................................................4-104.4 Modifying the ID of an RNC........................................................................................................................4-11

4.5 Modifying the Original Signaling Point of an RNC.....................................................................................4-12

4.6 Reconfiguring the the Iu/Iur Interface...........................................................................................................4-13

4.6.1 Modifying a Destination Signaling Point.............................................................................................4-13

4.6.2 Modifying an Iu/Iur Adjacent Node.....................................................................................................4-14

4.6.3 Changing the IP Address of the SGSN................................................................................................4-15

4.7 Reconfiguring Transport Network Timers....................................................................................................4-17

4.7.1 Setting SCCP Protocol Timers.............................................................................................................4-17

4.7.2 Setting SAAL Protocol Timers............................................................................................................4-18

4.7.3 Setting AAL2 Protocol Timers............................................................................................................4-19

RAN

Reconfiguration Guide Contents

Issue 01 (2009-02-10) Huawei Proprietary and Confidential


i



5 Reconfiguring the Network..................................................................................................... 5-1

5.1 Reconfiguring Clock Source and Working Mode in the RAN.......................................................................5-2

5.1.1 Modifying the RNC Clock Source and the Clock Working Mode........................................................5-2

5.1.2 Modifying the NodeB Clock Source and the Clock Working Mode.....................................................5-3

5.2 Reconfiguring Time Information in the RAN.................................................................................................5-4

5.2.1 Modifying the Time Information of an RNC.........................................................................................5-4

5.2.2 Modifying the Time Information of a NodeB........................................................................................5-5

5.3 Reconfiguring a Cell.......................................................................................................................................5-6

5.3.1 Modifying the Power of a Cell...............................................................................................................5-7

5.3.2 Modifying Cell Frequencies.................................................................................................................5-10

5.3.3 Modifying the Scrambling Code of a Cell...........................................................................................5-11

5.3.4 Modifying Cell System Message Parameters.......................................................................................5-12

5.3.5 Modifying Cell Radio Link Parameters...............................................................................................5-13

5.3.6 Modifying Cell Synchronization Parameters.......................................................................................5-14

5.3.7 Modifying the Area Information of a Cell...........................................................................................5-14

5.3.8 Modifying the UTRAN Registration Area of a Cell............................................................................5-15

5.3.9 Modifying a PRACH............................................................................................................................5-16

5.3.10 Removing a PRACH..........................................................................................................................5-19

5.3.11 Modifying an SCCPCH......................................................................................................................5-21

5.3.12 Removing an SCCPCH......................................................................................................................5-25

5.3.13 Renaming a Cell.................................................................................................................................5-26

5.3.14 Changing the ID of a Cell..................................................................................................................5-27

5.4 Reconfiguring Neighboring Cells.................................................................................................................5-285.4.1 Adding an Intra-Frequency Neighboring Cell.....................................................................................5-28

5.4.2 Adding an Inter-Frequency Neighboring Cell.....................................................................................5-30

5.4.3 Adding a Neighboring GSM Cell.........................................................................................................5-32

5.4.4 Modifying a Neighboring Cell.............................................................................................................5-34

5.4.5 Removing a Neighboring Cell..............................................................................................................5-34

5.5 Reconfiguring Timeslot Cross Connection...................................................................................................5-36

5.5.1 Configuring a Timeslot Cross Connection on an RNC........................................................................5-36

5.5.2 Configuring a Timeslot Cross Connection on a NodeB.......................................................................5-37

6 RAN Reconfiguration Reference............................................................................................ 6-16.1 Transport Network Timers..............................................................................................................................6-2

6.1.1 SCCP Timers..........................................................................................................................................6-2

6.1.2 SAAL Timers.........................................................................................................................................6-2

6.1.3 AAL2 Timers.........................................................................................................................................6-2

6.2 Cell-Related Concepts.....................................................................................................................................6-2

6.2.1 Definitions of Sector, Carrier, and Cell..................................................................................................6-3

6.2.2 Definitions of Local Cell and Logical Cell............................................................................................6-4

6.2.3 Logical Cell Model.................................................................................................................................6-5

6.2.4 Areas of Logical Cells............................................................................................................................6-5

6.2.5 Physical Resources of Cells...................................................................................................................6-6

Contents

RAN


ii Huawei Proprietary and Confidential


Issue 01 (2009-02-10)



6.2.6 Cell/Channel Activation and Deactivation.............................................................................................6-9

6.2.7 Definition of Neighboring Cell............................................................................................................6-10

6.3 RAN Clock Synchronization Configuration.................................................................................................6-11

6.3.1 RNC Clock Sources.............................................................................................................................6-11

6.3.2 RNC Clock Source Strata.....................................................................................................................6-12

6.3.3 Switching Policy of RNC Clock Sources.............................................................................................6-12

6.3.4 Switching Policy of NodeB Clock Sources..........................................................................................6-13

7 Optional Function Configuration Reference........................................................................7-1

7.1 96 HSDPA Users Per Cell...............................................................................................................................7-2

7.2 96 HSUPA Users Per Cell...............................................................................................................................7-2

7.3 MSCH and MSCH Scheduling.......................................................................................................................7-3

7.4 Enhanced CELL_FACH.................................................................................................................................7-4

7.5 CPC-HS-SCCH Less Operation......................................................................................................................7-5

7.6 CPC-DTX/DRX..............................................................................................................................................7-6

7.7 MOCN.............................................................................................................................................................7-7

RAN

Reconfiguration Guide Contents



iii





Figures

Figure 3-1 IP addresses in remote maintenance mode.........................................................................................3-3

Figure 6-1 Relations between sector, frequency, and cell............... .....................................................................6-4

Figure 6-2 Logical cell configuration model............................................................. ...........................................6-5

Figure 6-3 Physical RF resources mapped from sectors onto NodeB..................................................................6-7

Figure 6-4 Mapping rules between the BTS3812E sectors and the MAFUs/MTRUs.........................................6-8

RAN

Reconfiguration Guide Figures



v





Tables

Table 2-1 RAN reconfiguration tools...................................................................................................................2-2

Table 3-1 IP parameters of LMT PC in local maintenance mode........................................................................3-4

Table 3-2 IP parameters of LMT PC in remote maintenance mode.....................................................................3-4

Table 4-1 Data to be prepared for an LA..............................................................................................................4-4

Table 4-2 Data prepared for an RA......................................................................................................................4-5

Table 4-3 Data prepared for the service area........................................................................................................4-6

Table 4-4 Data negotiated for the SCCP timers.................................................................................................4-18

Table 5-1 Data to be prepared for an intra-frequency neighboring cell.............................................................5-29

Table 5-2 Data prepared for the neighboring cell at another RNC.....................................................................5-29

Table 5-3 Data prepared for an inter-frequency neighboring cell......................................................................5-31

Table 5-4 Data prepared for the neighboring cell at another RNC.....................................................................5-31

Table 5-5 Basic data of the GSM cell.................................................................................................................5-33

Table 5-6 Data prepared for a neighboring GSM cell........................................................................................5-33

Table 7-1 Activate................................................................................................................................................7-2Table 7-2 Disable..................................................................................................................................................7-2

Table 7-3 Activate................................................................................................................................................7-3

Table 7-4 Disable..................................................................................................................................................7-3

Table 7-5 Activate................................................................................................................................................7-4

Table 7-6 Disable..................................................................................................................................................7-4

Table 7-7 Activate................................................................................................................................................7-5

Table 7-8 Disable..................................................................................................................................................7-5

Table 7-9 Activate................................................................................................................................................7-6

Table 7-10 Disable................................................................................................................................................7-6

Table 7-11 Activate..............................................................................................................................................7-6

Table 7-12 Disable................................................................................................................................................7-7

Table 7-13 Activate..............................................................................................................................................7-7

Table 7-14 Disable................................................................................................................................................7-7

RAN

Reconfiguration Guide Tables



vii





About This Document

This document describes the procedures for reconfiguring the functioning RAN based on MML

command.

Purpose

Reconfiguring the RAN means reconfiguring different types of data in the RAN when the RAN

is functioning. The RAN consists of at least one RNC and one NodeB.

This document provides the basic procedures, basic operations, and typical tasks. The data

analysis process for network optimization and the number of boards and links for capacity

expansion depend on actual network conditions. Therefore, they are not described in this

document.

Product Version

The following table lists the product versions related to this document.

Product Name Product Version

RNC V200R011

NodeB V100R011,V200R011

Intended Audience

This document is intended for:

l Field engineers

l Network operators

l System engineers

Organization

1 Changes in RAN Reconfiguration Guide

This provides the changes in the RAN Reconfiguration Guide.

2 RAN Reconfiguration Introduction

This provides the definition of RAN reconfiguration and introduces the reconfiguration tools

and process.

3 Reconfiguring the NodeB

RAN

Reconfiguration Guide About This Document



1



This describes how to reconfigure the local IP address of the NodeB and the NodeB Local

Maintenance Terminal (LMT) PC.

4 Reconfiguring the RNC

This describes how to reconfigure the RNC in the functioning RAN.

5 Reconfiguring the Network

This describes how to carry out common network reconfiguring tasks in the functioning RAN.

6 RAN Reconfiguration Reference

This describes the reference for RAN reconfiguration.

7 Optional Function Configuration Reference

This describes how to configure optional function.

Conventions

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk, which if not

avoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if not

avoided,could result in equipment damage, data loss,

performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or save

time.

Provides additional information to emphasize or supplement

important points of the main text.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

Italic Book titles are in italics.

About This Document

RAN


2 Huawei Proprietary and Confidential


Issue 01 (2009-02-10)




Courier New Examples of information displayed on the screen are in

Courier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK .

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder .

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.

RAN

Reconfiguration Guide About This Document



3



Format Description

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without moving

the pointer.

Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.

Drag Press and hold the primary mouse button and move the

pointer to a certain position.

About This Document

RAN


4 Huawei Proprietary and Confidential


Issue 01 (2009-02-10)



1 Changes in RAN Reconfiguration Guide

This provides the changes in the RAN Reconfiguration Guide.

01(2009-02-10)

This is the field trial release of RAN11.0.

Compared with issue 01(2008-03-20)of RAN10.0, the description of feature configuration is

added.

RAN

Reconfiguration Guide 1 Changes in RAN Reconfiguration Guide



1-1






About This Chapter

This provides the definition of RAN reconfiguration and introduces the reconfiguration tools

and process.

2.1 RAN Reconfiguration Definition

RAN reconfiguration refers to the data reconfiguration in the functioning RAN. RAN

reconfiguration enables the RAN to provide services to more UEs or provide improved services

after the conf iguration is changed. The RAN consists of at least one RNC and one NodeB.

2.2 RAN Reconfiguration Tools

This describes the RAN reconfiguration tools. The tools include LMT and WCDMA

Configuration Management Express (CME) that can be used at either the RNC or the NodeB.

2.3 RAN Reconfiguration Process

When reconfiguring the RAN data on the LMT, you must comply with the specific process to

minimize the impact on current services.

RAN

Reconfiguration Guide 2 RAN Reconfiguration Introduction



2-1



2.1 RAN Reconfiguration Definition

RAN reconfiguration refers to the data reconfiguration in the functioning RAN. RAN

reconfiguration enables the RAN to provide services to more UEs or provide improved services

after the configuration is changed. The RAN consists of at least one RNC and one NodeB.

RAN reconfiguration is based on following reasons:

l Network optimization

Network optimization refers to adption and optimization to network during running course

based on system running data obtained by performance measurement or rounting test.

l System capacity expanding

System capacity expanding aims to serve much more terminal users by adding hardware

or change configuration on exsisting network.

The emphases of RAN reconfiguration is to introduce the data needed preparation and the

process of reconfiguration. The analysing course for network optimization data, the confirmation

course of the hardware in systerm expanding and the link quatity are ensured by specifical

network.

2.2 RAN Reconfiguration Tools

This describes the RAN reconfiguration tools. The tools include LMT and WCDMA

Configuration Management Express (CME) that can be used at either the RNC or the NodeB.

Table 2-1 describes the RAN (including RNC and NodeB) reconfiguration tools.

Table 2-1 RAN reconfiguration tools

NE ReconfigurationTool

Description

RNC LMT By using MML commands, you can configure data for

an RNC in either online or offline mode.

l In online mode, the configuration data is directly sent

to the host of the RNC, and the data takes effect

immediately. This mode applies to data

reconfiguration.

l In offline mode, you must restart the RNC host.

Then, the configuration takes effect. This mode

applies to RNC initial configuration.

For details about the reconfiguration process, refer to

the RAN Reconfiguration Guide.


RAN


2-2 Huawei Proprietary and Confidential


Issue 01 (2009-02-10)



NE ReconfigurationTool

Description

CME You can configure the data of an RNC on the CME.

l In integrated mode, the configuration data can besent to the RNC host through the M2000

immediately or at a specified time. This mode applies

to data reconfiguration.

l In standalone mode, export the configuration file

after the operation, and then load the configuration

file to the RNC host through the LMT or M2000. The

data takes effect. This mode applies to RNC initial

configuration.

For details about how to use the CME to perform RAN

reconfiguration, refer to the RAN Reconfiguration

Guide (CME-Based).

NodeB LMT By using MML commands, you can configure data for

the NodeB online. The configuration data takes effect

immediately. This mode applies to data

reconfiguration.

For details about the reconfiguration process, refer to

the RAN Reconfiguration Guide.

CME You can configure the data of a NodeB on the CME.

In integrated and standalone modes, export the

configuration file after the operation, and then load the

file to the NodeB host through the LMT or M2000 totake effect.

For details about how to use the CME to perform RAN

reconfiguration, refer to the RAN Reconfiguration

Guide (CME-Based).

2.3 RAN Reconfiguration Process

When reconfiguring the RAN data on the LMT, you must comply with the specific process to

minimize the impact on current services.

Context

During the RAN reconfiguration, note that:

l Unless otherwise stated, the RNC data has to be reconfigured online. In online mode, you

need not restart the host. This helps to minimize the impact on current services. When a

task can be performed only in offline mode, it is indicated at that particular task.

l For a NodeB, the configuration involves reconfiguration or initial configuration.

NOTE

The Huawei NodeB has different models. The board names and MML commands vary with the NodeB

model.

RAN

Reconfiguration Guide 2 RAN Reconfiguration Introduction



2-3



Procedure

Step 1 Determine whether the RNC is involved in the reconfiguration.

If... Then...

Involved 1. Start the RNC LMT, as described in Getting Started with the RNC LMT.

2. On the RNC LMT, set the subracks of the RNC to online mode, as described

in Setting the RNC to Online Mode.

3. Perform the online reconfiguration on the RNC by referring to the RAN

Reconfiguration Guide.

4. Go to Step 2.

Not involved Go to Step 2.

Step 2 Determine whether the NodeB is involved in the reconfiguration.

If... Then...

Involved Go to Step 3.

Not involved Finish the RAN reconfiguration.

Step 3 Determine whether the NodeB data is existent.

If... Then...

Existent 1. Start the NodeB LMT, as described in Getting Started with the NodeB LMT.

2. Perform the reconfiguration on the NodeB by referring to the RAN

Reconfiguration Guide.

Nonexistent Add the initial data of the NodeB by referring to the NodeB Initial Configuration

Guide.

Step 4 Finish the RAN reconfiguration.

----End


RAN




Issue 01 (2009-02-10)




About This Chapter

This describes how to reconfigure the local IP address of the NodeB and the NodeB Local

Maintenance Terminal (LMT) PC.

3.1 Changing the Local IP Address of a NodeB

This describes how to change the local IP address of a NodeB.

3.2 Setting the IP Address of the NodeB LMT PC

This describes how to set the IP address of the NodeB LMT PC. You must set a correct IP address

for the LMT PC before logging in to the NodeB.

RAN

Reconfiguration Guide 3 Reconfiguring the NodeB



3-1



3.1 Changing the Local IP Address of a NodeB

This describes how to change the local IP address of a NodeB.

NEs Involved NodeB

Prerequisite

The NodeB works properly.

Preparation

Prepare a new local IP address for the NodeB.

Procedure

Step 1 On the NodeB LMT, run the SET LOCALIP command to change the local IP address of the

NodeB.

Step 2 Change the IP address of the LMT PC so that the IP addresses of the LMT PC and the NodeB

are in the same network segment. For details, refer to 3.2 Setting the IP Address of the NodeB

LMT PC.

Step 3 On the NodeB LMT, run the LST LOCALIP command to check whether the changed IP address

is correct.

----End

3.2 Setting the IP Address of the NodeB LMT PC

This describes how to set the IP address of the NodeB LMT PC. You must set a correct IP address

for the LMT PC before logging in to the NodeB.

Prerequisite

The TCP/IP protocol is configured on the LMT PC.

Context

Before you perform the maintenance, set the IP address for the LMT PC as follows:

l In local maintenance, IP addresses of the LMT PC and the NodeB local maintenance

channel are in the same network segment.

l In remote maintenance, you need to set the route from the LMT PC to the NodeB; IP 1 and

IP 2 are in the same network segment, as shown in Figure 3-1. IP 1 stands for the IP address

of the LMT PC. IP 2 stands for the IP address of the external network composed of the

entity directly connected to the LMT PC and the LAN where the LMT PC is located, for

example, the IP address of the RNC BAM external network.


RAN




Issue 01 (2009-02-10)



Figure 3-1 IP addresses in remote maintenance mode

CAUTION

Ensure that the IP address of the LMT PC does not conflict with the IP address of another

computer within the same local area network.

Procedure

Step 1 To set the IP address of the LMT PC with the Windows XP operating system as an example,

perform the following steps: Choose Start > Control Panel.

If... Then...

The control panel is displayed in categoryview,

Go to Step 2.

The control panel is displayed in classical

view,

Go to Step 3.

Step 2 Click Network and Internet Connections.

Step 3 Double-click Network Connections. The Network Connections window is displayed. Right-

click the icon of Local Area Connection.

Step 4 Choose Properties on the shortcut menu. The Local Area Connection Properties dialog box

is displayed.

Step 5 Select Internet Protocol (TCP/IP).

Step 6 Click Properties. The Internet Protocol (TCP/IP) Properties dialog box is displayed.

Step 7 Select Use the following IP address.

Step 8 Enter the correct IP address, subnet mask, and default gateway.

If... Then...

The LMT PC is used in local maintenance

mode,

Set the IP address, subnet mask, and default

gateway, as shown in Table 3-1.

RAN

Reconfiguration Guide 3 Reconfiguring the NodeB



3-3



If... Then...

The LMT PC is used in remote maintenance

mode,

Set the IP address, subnet mask, and default

gateway, as shown in Table 3-2.

Table 3-1 IP parameters of LMT PC in local maintenance mode

Element Description

IP Address In the same network segment as that of the NodeB local maintenance

channel

In local maintenance mode, the default NodeB IP address is 17.21.2.15.

Subnet mask Same subnet mask as that of the NodeB local maintenance channel

Default gateway -

Table 3-2 IP parameters of LMT PC in remote maintenance mode

Element Description

IP Address In the same network segment as the external IP address of RNC BAM

Subnet mask Same subnet mask as the external subnet mask of RNC BAM

Default gateway The IP address of the BAM external network is the gateway from the

LMT to the NodeB.

NOTE

The IP address in the same network segment corresponds to the same subnet mask and subnet address

(subnet mask AND IP address).

Step 9 Click OK .

----End


RAN




Issue 01 (2009-02-10)




About This Chapter

This describes how to reconfigure the RNC in the functioning RAN.

4.1 Switching the MSC/SGSN/RNC to Another Port on an RNC

This describes how to switch the MSC/SGSN/RNC to another port on a running RNC.

4.2 Setting the Adjustment Mode of RNC Fan Speed

This describes how to set the adjustment mode of the RNC fan speed.

4.3 Reconfiguring RNC Areas

This describes how to add or modify a location area, routing area, and service area. In addition,it describes how to modify the range of a PLMN tag.

4.4 Modifying the ID of an RNC

This describes how to modify the ID of an R NC.

4.5 Modifying the Original Signaling Point of an RNC

This describes how to modify the original signaling point (OSP) of an RNC, including the source

ATM address and source OSP name.

4.6 Reconfiguring the the Iu/Iur Interface

This describes how to reconfigure the RNC on the Iu/Iur interface, involving reconfiguring a

destination signaling point (DSP), an Iu/Iur adjacent node, and the IP address of the SGSN.

4.7 Reconfiguring Transport Network Timers

This describes how to reconfigure the transport network timers, including SCCP timers, SAAL

timers, and AAL2 timers.

RAN

Reconfiguration Guide 4 Reconfiguring the RNC



4-1



4.1 Switching the MSC/SGSN/RNC to Another Port on anRNC

This describes how to switch the MSC/SGSN/RNC to another port on a running RNC.

NEs InvolvedRNC

Prerequisite

l The new port works properly and is available.

l The backup mode of the interface board is set according to the port type.

– If the port is an E1/T1 port or an optical poart, the backup mode of the interface board

is set to YES.

– If the port is an Ethernet port, the backup mode of the interface board is set to YES, and

the backup mode of the port is set.

l The RNC works properly.

l The current user has the RNC control right concerning data configuration management.

The control right of data configuration management can be queried through LST

CMCTRL. If the current user does not have the RNC control right concerning data

configuration management, refer to Obtaining the RNC Data Configuration Right.

l The RNC is online.

The current data configuration mode of the RNC can be queried through the LSTCFGMODE. If the RNC user is offline, refer to Setting the RNC to Online Mode.

Procedure

l Switch over E1/T1 ports

If the port is an E1/T1 port, the backup mode of the interface board can be set only to Board

backup mode.

1. On the LMT of the RNC, run the SWP BRD to start a forced switchover from active

to standby.

2. Run the DSP BRD command to check whether the board works properly after the

switchover.

l Switch over optical ports

1. On the LMT of the RNC, run the SET MSPCMD command to perform an MSP

switchover between optical ports.

2. Run the DSP MSP command to check whether the status of the MSP protection pair

is correct.

l Switch over Ethernet ports

1. On the RNC LMT, run the DSP ETHPORT command to check the backup mode of

the Ethernet port.

2. Run the SWP ETHPORT command to switch over Ethernet ports.


RAN




Issue 01 (2009-02-10)



3. Run the DSP ETHPORT command to check whether the Ethernet ports work

properly after the switchover.

----End

4.2 Setting the Adjustment Mode of RNC Fan Speed

This describes how to set the adjustment mode of the RNC fan speed.

NEs InvolvedRNC

NOTE

As the fan speed has a direct impact on the heat dissipation of the system components, perform this operation

only when you fully understand its impact on the system.

Prerequisitel The RNC works properly.






The current data configuration mode of the RNC can be queried through the LST

CFGMODE. If the RNC user is offline, refer to Setting the RNC to Online Mode.

Preparation None.

Procedure

Step 1 On the RNC LMT, run the LST FANSPEED command to view the adjustment mode of the fan.

Step 2 If needed, run the SET FANSPEED command to set the adjustment mode of the fan.

Step 3 Run the LST FANSPEED command to check whether the setting is correct.

----End

4.3 Reconfiguring RNC Areas

This describes how to add or modify a location area, routing area, and service area. In addition,

it describes how to modify the range of a PLMN tag.

4.3.1 Adding a Location Area

This describes how to add a location area (LA) on an RNC.

4.3.2 Adding a Routing Area

This describes how to add a routing area (RA) on an RNC.

4.3.3 Adding a Service Area

RAN




4-3



This describes how to add a service area (SA) on an RNC.

4.3.4 Adding a UTRAN Registration Area

This describes how to add a UTRAN Registration Area (URA) on an RNC.

4.3.5 Modifying a Location Area CodeThis describes how to modify a location area code (LAC) on an RNC.

4.3.6 Modifying a Routing Area Code

This describes how to modify a routing area code (RAC) on an RNC.

4.3.7 Modifying a Service Area Code

This describes how to modify a service area code (SAC) on an RNC.

4.3.8 Modifying a UTRAN Registration Area ID

This describes how to modify a UTRAN Registration Area (URA) ID on an RNC.

4.3.9 Modifying the Value Range of a PLMN Tag

This describes how to modify the value range of the PLMN tag of an LAC or RAC at the RNC.

4.3.1 Adding a Location Area

This describes how to add a location area (LA) on an RNC.

NEs InvolvedRNC

Prerequisite









Preparation

Table 4-1 lists the data to be prepared for an LA. The location area code (LAC) needs to be

negotiated with the CN.

Table 4-1 Data to be prepared for an LA

CN OperatorIndex

Location AreaCode

Minimum Value ofPLMN Value Tag

Maximum Value ofPLMN Value Tag

Procedure

Step 1 Run the ADD LAC command to add an LA.

To add more LAs, repeat this step.


RAN




Issue 01 (2009-02-10)



Step 2 Run the LST AC command to view the area information and ensure that the added LAC is

correct.

----End

4.3.2 Adding a Routing AreaThis describes how to add a routing area (RA) on an RNC.

NEs InvolvedRNC

Prerequisite









l The LA where the RA is located is added. For details, refer to 4.3.1 Adding a Location

Area.

Preparation

Table 4-2 lists the data to be prepared. Except for Operator Index, other parameters are

determined by the operator.

Table 4-2 Data prepared for an RA

OperatorIndex

LocationArea Code

Routing Area Code

Minimum Valueof PLMN ValueTag

Maximum Valueof PLMN ValueTag

Procedure

Step 1 On the RNC LMT, run the ADD RAC command to add an RA.

To add more RAs, repeat this step.

Step 2 Run the LST AC command to check whether the added RA is correct.

----End

4.3.3 Adding a Service Area

This describes how to add a service area (SA) on an RNC.

NEs InvolvedRNC

RAN




4-5



Prerequisite



The control right of data configuration management can be queried through LSTCMCTRL. If the current user does not have the RNC control right concerning data





l The LA where the SA is located is added. For details, refer to 4.3.1 Adding a Location

Area.

Preparation

Table 4-3 lists the data to be prepared. The LAC and SAC are determined by the operator.

Table 4-3 Data prepared for the service area

Operator Index Location Area Code Service Area Code

Procedure

Step 1 On the RNC LMT, run the ADD SAC command to add a CS/PS SA.To add more SAs, repeat this step.

Step 2 Run the LST AC command to check whether the added SA is correct.

----End

4.3.4 Adding a UTRAN Registration Area

This describes how to add a UTRAN Registration Area (URA) on an RNC.

NEs InvolvedRNC

Prerequisite



The control r ight of data configuration management can be queried through LST






RAN




Issue 01 (2009-02-10)



Preparation

The URA ID and operator index are available.

ProcedureStep 1 On the RNC LMT, run the ADD URA command to add the URA ID. To add more URA IDs,

repeat this step.

Step 2 Run the LST URA command to check whether the added URA is correct.

----End

4.3.5 Modifying a Location Area Code

This describes how to modify a location area code (LAC) on an RNC.

NEs InvolvedRNC

The LAC may be referenced by another object, such as a routing area code (RAC), a service

area code (SAC), or a cell. Therefore, do not modify the LAC unless necessary. If you have to

modify the LAC, you must also change the reference to the old LAC into the reference to the

new one.

In this part, LACs before and after the modification are named LAC A and LAC B respectively.

Prerequisite









Preparation

None.

Procedure

Step 1 On the RNC LMT, run the ADD LAC command to add LAC B.

Step 2 Modify references of LAC A to references of LAC B.

1. Run the LST AC command to view the RACs and SACs that reference the LAC.

l If the result shows that there is an RAC that references LAC A, run the ADD RAC

command to make this RAC reference LAC B.

l If the result shows that there is an SAC that references LAC A, run the ADD SAC

command to make this SAC reference LAC B. If there are other SACs that referenceLAC A, repeat this step.

RAN




4-7



2. Run the LST ACCELL command to view the cell that references LAC A.

l If the result shows that there is a cell that references LAC A, run the MOD

CELLACINFO command to make the cell reference LAC B.

3. Run the RMV RAC command to remove the RAC that references LAC A.

4. Run the RMV SAC command to remove the SAC that references LAC A.

Step 3 Run the RMV LAC command to remove LAC A.

Step 4 Run the LST AC command to check whether LAC A is removed.

----End

4.3.6 Modifying a Routing Area Code

This describes how to modify a routing area code (RAC) on an RNC.

NEs InvolvedRNC

RAC is referenced by cells. Therefore, do not modify RAC unless necessary.

In this part, RACs before and after the modification are named RAC A and RAC B respectively.

Prerequisite









Preparation

None.

ProcedureStep 1 On the RNC LMT, run the ADD RAC command to add RAC B.

Step 2 Modify references of RAC A to references of RAC B.

1. Run the LST ACCELL command to view the cell that references RAC A.

2. If there is a cell that references RAC A, run the MOD CELLACINFO command to modify

the RAC to B. If there are other cells that reference RAC A, repeat this step.

Step 3 Run the RMV RAC command to remove RAC A.

Step 4 Run the LST AC to check whether RAC A is removed.

----End


RAN




Issue 01 (2009-02-10)



4.3.7 Modifying a Service Area Code

This describes how to modify a service area code (SAC) on an RNC.

NEs InvolvedRNC

One SAC may be referenced by multiple objects, for example, classified zone and cell.

Therefore, do not modify SAC unless necessary.

In this part, SACs before and after the modification are named SAC A and SAC B respectively.

Prerequisite








Preparation

None.

Procedure

Step 1 On the RNC LMT, run the ADD SAC command to add SAC B.

Step 2 Modify references of SAC A to references of SAC B.

1. Run the LST ACCELL command to view the cell that references SAC A.

2. If there is a cell that references SAC A, run the MOD CELLACINFO command to modify

the SAC to B. If there are other cells that reference SAC A, repeat this step.

Step 3 Run the RMV SAC command to remove the CS/PS SAC A.

Step 4 Run the LST AC command to check whether the SAC A is removed.

----End

4.3.8 Modifying a UTRAN Registration Area ID

This describes how to modify a UTRAN Registration Area (URA) ID on an RNC.

NEs InvolvedRNC

The URA ID may be referenced by another object, for example, a cell. Therefore, do not change

URA ID unless necessary.

In this part, the URA IDs before and after the change are called URA A and URA B respectively.

RAN




4-9



Prerequisite








Preparation

None.

Procedure

Step 1 On the RNC LMT, run the ADD URA command to add URA B.

Step 2 Modify references of URA A to references of URA B.

1. Run the LST URACELL command to view the cell that references URA A.

2. If there is a cell that references URA A, run the ADD CELLURA command to add B as

URA ID of this cell.

3. If there is a cell that references URA A, run the RMV CELLURA command to remove

the reference of this cell to URA A.

NOTE

If URA A is referenced by another RNC, remove the reference on this RNC and then add the reference

to URA B.

Step 3 Run the LST CELLURA command to check whether the references of cells to URA A is

removed.

If... Then...

All the references are removed, Skip to Step 4.

Not all the references are removed, Go to Step 2.

Step 4 Run the RMV URA command to remove URA A.

Step 5 Run the LST URA command to check whether URA A is removed.

----End

4.3.9 Modifying the Value Range of a PLMN Tag

This describes how to modify the value range of the PLMN tag of an LAC or RAC at the RNC.

NEs InvolvedRNC


RAN




Issue 01 (2009-02-10)



Prerequisite








Preparation

None.

Procedure

Step 1 On the RNC LMT, run the LST AC command to view the specified area information of the

RNC.

Step 2 Run the MOD PLMNVALTAGRANGE command to modify the value range of the PLMN

tag of the LAC or RAC.

Step 3 Run the LST AC command to check whether the modification is correct.

----End

4.4 Modifying the ID of an RNCThis describes how to modify the ID of an RNC.

NEs InvolvedRNC

NOTE

Restarting the RNC can disrupt all services on the RNC.

CAUTION

l The existing license file becomes invalid after the RNC ID is modified. Therefore, you

should obtain a new license file before the modification.

Prerequisite




CMCTRL. If the current user does not have the RNC control right concerning dataconfiguration management, refer to Obtaining the RNC Data Configuration Right.

RAN




4-11



Preparation

l RNC ID

l A new license file matching the new RNC ID is available.

Procedure

Step 1 Copy the new license file into different paths according to the different versions of the RNC.

NOTE

l In the V200R100 version of the RNC, copy the license file to BAM active workspace\FTP

\LICENSE.

l In the V100R100 version of the RNC, copy the license file toFTP\LICENSE.

Step 2 Run the SET OFFLINE command to set all the RNC subracks to offline mode.

Step 3 Run the MOD RNCBASIC command to modify the RNC ID.

Step 4 Run the LST RNCBASIC command to check whether the modification is correct.

Step 5 Run the RST RNC command to reset the RNC.

Step 6 Run the SET ONLINE command to set all the RNC subracks to online mode.

Wait at least 10 minutes before performing the next step.

Step 7 Run the ACT LICENSE command to activate the license that matches the RNC ID.

Step 8 Run the DSP LICENSE command to query the license configuration of the BAM.

Step 9 Run the CMP LICENSE command to check consistency between the running license on the

FAM and the current license on the BAM.

----End

4.5 Modifying the Original Signaling Point of an RNC

This describes how to modify the original signaling point (OSP) of an RNC, including the source

ATM address and source OSP name.

NEs InvolvedRNC

NOTE

l The services carried on the RNC with the original OSP will be disrupted because of modifying the

OSP.

l MOD OPC is an offline command, which can be used only in offline mode. The added data takes

effect after the RNC host (or subracks, boards) is restarted.

Prerequisite




CMCTRL. If the current user does not have the RNC control right concerning dataconfiguration management, refer to Obtaining the RNC Data Configuration Right.


RAN




Issue 01 (2009-02-10)






Preparation None.

Procedure


Step 2 Run the LST OPC command to query the information of the OSP of an RNC.

Step 3 Run the MOD OPC command to modify the attributes of the OSP of an RNC.

Step 4 Run the LST OPC command to check whether the modification is correct.



----End

4.6 Reconfiguring the the Iu/Iur Interface

This describes how to reconfigure the RNC on the Iu/Iur interface, involving reconfiguring a

destination signaling point (DSP), an Iu/Iur adjacent node, and the IP address of the SGSN.

4.6.1 Modifying a Destination Signaling Point

This describes how to modify a destination signaling point (DSP) when the RNC is working.

The modifiable attributes include the signaling route mask, STP function switch, adjacent flag,

and DSP name.

4.6.2 Modifying an Iu/Iur Adjacent Node

This describes how to modify an Iu/Iur adjacent node when the RNC is running.

4.6.3 Changing the IP Address of the SGSN

This describes how to refresh the data at the RNC after the IP address of the SGSN in the PS

domain is changed.

4.6.1 Modifying a Destination Signaling Point

This describes how to modify a destination signaling point (DSP) when the RNC is working.

The modifiable attributes include the signaling route mask, STP function switch, adjacent flag,

and DSP name.

NEs InvolvedRNC

NOTE

l The services carried on the original DSP are disrupted because of modifying the DSP.

lMOD N7DPC is an offline command that can be used only in offline mode. The added data takeseffect after the RNC host (or subracks, boards) is restarted.

RAN




4-13



Prerequisite





Preparation

None.

Procedure


Step 2 Run the LST N7DPC command to view the index of the DSP to be modified.

Step 3 Run the MOD N7DPC command to modify the data of the DSP.

Step 4 Run the LST N7DPC command to check whether the modification is correct.



----End

4.6.2 Modifying an Iu/Iur Adjacent NodeThis describes how to modify an Iu/Iur adjacent node when the RNC is running.

NEs InvolvedRNC

NOTE

Services to this adjacent node are disrupted during the operation.

Prerequisite

l

The RNC works properly.l The current user has the RNC control right concerning data configuration management.







Preparation

None.


RAN




Issue 01 (2009-02-10)



Procedure

Step 1 On the LMT of the RNC, run the LST ADJNODE command to view the settings of the adjacent

node to be modified.

Step 2 Run the MOD ADJNODE command to modify the adjacent node.

Step 3 Run the LST ADJNODE command to check whether the settings are correct.

----End

4.6.3 Changing the IP Address of the SGSN

This describes how to refresh the data at the RNC after the IP address of the SGSN in the PS

domain is changed.

NEs InvolvedRNC, SGSN

NOTE

Communication between the RNC and the SGSN is disrupted because of changing the IP address of the

SGSN.

Prerequisite





configuration management, refer to Obtaining the RNC Data Configuration Right.l The RNC is online.



Preparation

Negotiate the following data with the peer SGSN: new IP address of the SGSN and network

mask.

Procedure

l When the communication between the RNC and the SGSN is based on ATM, the change

of the IP address of the SGSN affects the data transmission on the user plane. In this case,

you need to adjust the bearing IP paths on the user plane.

1. Modify the IP paths

(1) On the RNC LMT, run the LST IPPATH command to view the IP paths between

the RNC and the old IP address of the SGSN.

(2) Run the RMV IPPATH command to remove the IP paths between the RNC and

the old IP address of the SGSN.

(3) Run the ADD IPPATH command to add an IP path between the RNC and the

new IP address of the SGSN.

2. Modify the IPoA PVC link on which the IP path is carried

RAN




4-15



(1) Run the LST IPOAPVC command to view the IPoA PVC link on which the old

IP path is carried.

(2) Run the RMV IPOAPVC command to delete the IPoA PVC link on which the

old IP path is carried.

(3) Run the ADD IPOAPVC command to add a new IPoA PVC link on which theold IP path is carried.

3. Modify the IP route

(1) Run the LST IPRT command to view the configuration of the IP route of the

previous IP address of the SGSN, and then record the IP address of the forward

route.

(2) Run the RMV IPRT command to remove the route towards the previous IP

address of the SGSN.

(3) Run the ADD IPRT command to add a route towards the new IP address of the

SGSN.

4. Run the PING IP command to check whether the route towards the new destination

IP address is functional.

l When the communication between the RNC and the SGSN is based on IP, the change of

the IP address of the SGSN affects the data transmission on both the user plane and the

control plane. In this case, you need to adjust the bearing SCTP links on the control plane

and the bearing links on the user plane.

1. Modify the SCTP links

(1) Run the LST SCTPLNK command to view the SCTP links between the RNC

and the old IP address of the SGSN.

(2) Run the MOD SCTPLNK command to modify the peer IP addresses of theSCTP links to the new IP address of the SGSN.

2. Modify the IP paths

(1) Run the LST IPPATH command to view the IP paths between the RNC and the

old IP address of the SGSN.

(2) Run the RMV IPPATH command to remove the IP paths between the RNC and

the old IP address of the SGSN.

(3) Run the ADD IPPATH command to add an IP path between the RNC and the

new IP address of the SGSN.

3. Modify the IP route

(1) Run the LST IPRT command to view the configuration of the IP route of the

previous IP address of the SGSN, and then record the IP address of the forward

route.

(2) Run the RMV IPRT command to remove the route towards the previous IP

address of the SGSN. If there are more such routes, repeat this step.

(3) Run the ADD IPRT command to add a route towards the new IP address of the

SGSN.

4. Run the PING IP command to check whether the route towards the new destination

IP address is functional.

----End


RAN




Issue 01 (2009-02-10)



4.7 Reconfiguring Transport Network Timers

This describes how to reconfigure the transport network timers, including SCCP timers, SAALtimers, and AAL2 timers.

4.7.1 Setting SCCP Protocol Timers

This describes how to set SCCP protocol timers.

4.7.2 Setting SAAL Protocol Timers

This describes how to set SAAL protocol timers.

4.7.3 Setting AAL2 Protocol Timers

This describes how to set AAL2 protocol timers to ensure the consistency of the settings at the

two ends of an AAL2 link.

4.7.1 Setting SCCP Protocol Timers

This describes how to set SCCP protocol timers.

NEs InvolvedRNC

NOTE

The modification of the timers has a great impact on signaling processing. Therefore, you are not advised

to modify the settings unless necessary.

Prerequisitel The RNC works properly.








Preparation

To modify the inactive receive SCCP timers or inactive transmit SCCP timers, you need to

prepare the negotiated data, as listed in Table 4-4. Otherwise, you do not need to prepare the

negotiated data.

NOTE

l The duration of the local inactive receive timer must be at least twice as long as that of the peer

inactive transmit timer.

l The duration of the peer inactive receive timer must be at least twice as long as that of the local

inactive transmit timer.

RAN




4-17



Table 4-4 Data negotiated for the SCCP timers

Item Negotiated Data

Inactive Transmit Timer Inactive Receive Timer

SCCP timer of the RNC

SCCP timer of the peer node

Procedure

Step 1 Run the LST SCCPTMR command to view the SCCP timers.

Step 2 Run the SET SCCPTMR command to set the relevant SCCP timers.

Step 3 Run the LST SCCPTMR command to check whether the settings are successful.

----End

4.7.2 Setting SAAL Protocol Timers

This describes how to set SAAL protocol timers.

NEs InvolvedRNC

Prerequisite









Preparation None.

Procedure

Step 1 Run the LST SAALLNK command to view the settings of the SAAL timers.

Step 2 Run the MOD SAALLNK command to set the SAAL timers.

Step 3 Run the LST SAALLNK command to check whether the SAAL timers have been set

successfully.

----End


RAN




Issue 01 (2009-02-10)



4.7.3 Setting AAL2 Protocol Timers

This describes how to set AAL2 protocol timers to ensure the consistency of the settings at the

two ends of an AAL2 link.

NEs InvolvedRNC

NOTE

The modification of the timers has a great impact on signaling processing. Therefore, you are not devised

to modify the settings unless necessary.

Prerequisite









Preparation

None.

Procedure

Step 1 Run the LST AAL2TMR command to view the AAL2 timers.

Step 2 Run the SET AAL2TMR command to set the AAL2 timers.

Step 3 Run the LST RNCBASIC command to check whether the AAL2 timers have been set

successfully.

----End

RAN




4-19






About This Chapter

This describes how to carry out common network reconfiguring tasks in the functioning RAN.

5.1 Reconfiguring Clock Source and Working Mode in the RAN

This describes the procedures of modifying the clock source and clock working mode of an RNC

and a NodeB.

5.2 Reconfiguring Time Information in the RAN

This describes the procedures for modifying the time information of an RNC and a NodeB.

5.3 Reconfiguring a CellThis describes how to reconfigure a cell, including cell parameters and channel parameters.

5.4 Reconfiguring Neighboring Cells

This describes how to reconfigure neighboring cells, including intra-frequency cells, inter-

frequency cells, and neighboring GSM cells.

5.5 Reconfiguring Timeslot Cross Connection

This describes how to reconfigure timeslot cross connection on an RNC and on a NodeB.

RAN

Reconfiguration Guide 5 Reconfiguring the Network



5-1



5.1 Reconfiguring Clock Source and Working Mode in theRAN

This describes the procedures of modifying the clock source and clock working mode of an RNC

and a NodeB.

5.1.1 Modifying the RNC Clock Source and the Clock Working Mode

This describes how to modify the RNC clock source and the working mode of the clock.

5.1.2 Modifying the NodeB Clock Source and the Clock Working Mode

This describes how to modify the NodeB clock source and the working mode of the clock.

5.1.1 Modifying the RNC Clock Source and the Clock Working

Mode

This describes how to modify the RNC clock source and the working mode of the clock.

NEs InvolvedRNC

Prerequisite









Preparation

l The line clock, BITS clock, GPS clock, or external 8 kHz clock is determined as the type

of clock source used by the RNC.

l The working mode MANUAL or AUTO is determined.

Procedure

Step 1 Run the LST CLKSRC command to view the clock source.

Step 2 Add, remove, or change the clock source according to your requirements.

NOTE

If the system clock is extracted from the interface board on which the clock source is not con figured, you

must run the SET CLK command to set the corresponding clock source for the interface board before

adding the system clock source.


RAN




Issue 01 (2009-02-10)



If... Then...

You need to add the system clock

source,

1. Run the ADD CLKSRC command.

2. Go to Step 3.

You need to remove the system clock

source,

1. Run the RMV CLKSRC command.

2. Go to Step 3.

You need to change the system clock

source,

1. Run the RMV CLKSRC command to remove

the original clock source.

2. Run the ADD CLKSRC command to add a new

system clock source that meets your

requirements.

3. Go to Step 3.

Step 3 Run the LST CLKSRC command to check whether the settings of the clock source are correct.

Step 4 Run the LST CLKMODE command to check whether the clock source and the clock working

mode are correct.

If... Then...

The clock source and the clock working

mode are correct,

Finish this task.

The clock source and the clock working

mode are incorrect,

1. Run the SET CLKMODE command.

2. Run the LST CLKMODE command to

ensure that the clock source and the clock

working mode are correct.

3. Finish this task.

----End

5.1.2 Modifying the NodeB Clock Source and the Clock Working

Mode

This describes how to modify the NodeB clock source and the working mode of the clock.

NEs Involved NodeB

NOTE

Each NodeB interface board is configured with only one line clock.

Prerequisite


RAN




5-3



Preparation

l The line clock, IP clock, BITS clock, or GPS clock is determined as the type of clock source

used by the NodeB.

l

The working mode: MANUAL or FREE is determined.

Procedure

Step 1 On the NodeB LMT, run the DSP CLKSTAT command to view the settings of the clock source

and the clock working mode.

Step 2 If you need to change the current clock source to IP, BITS, or GPS, or change the clock working

mode to MANUAL or FREE, run the SET CLKMODE (on NodeB LMT) command to set the

parameters. Otherwise, finish the task.

Step 3 On the NodeB LMT, run the DSP CLKSTAT command to ensure that the settings of the clock

source and the clock working mode are correct.

----End

5.2 Reconfiguring Time Information in the RAN

This describes the procedures for modifying the time information of an RNC and a NodeB.

5.2.1 Modifying the Time Information of an RNC

This describes how to modify the time information of an RNC.

5.2.2 Modifying the Time Information of a NodeB

This describes how to modify the time information of a NodeB, including the time zone of the

NodeB, daylight saving policy, and SNTP synchronization period.

5.2.1 Modifying the Time Information of an RNC

This describes how to modify the time information of an RNC.

NEs InvolvedRNC

Prerequisite









Preparation

l The time zone of the RNC is known.


RAN




Issue 01 (2009-02-10)



l The daylight saving parameters of the RNC that comply with the local law are known.

l The synchronization period on the SNTP client is known.

Procedure

Step 1 Set the time zone and daylight saving information of the RNC.

1. Run the LST TZ command to view the time zone and daylight saving information of the

RNC.

2. Run the SET TZ command to modify the time zone and daylight saving information of the

RNC.

If the Daylight Saving Time (DST) is chosen, you also need to set the parameters for the

DST.

3. Run the LST TZ command to check whether the modified time zone and daylight saving

information of the RNC is correct.

Step 2 Set the parameters of the RNC serving as an SNTP client.

1. Run the LST SNTPCLTPARA to view the parameters of the SNTP client.

2. Run the SET SNTPCLTPARA to modify the parameters of the SNTP client.

3. Run the LST SNTPCLTPARA command to check whether the modifications are correct.

----End

5.2.2 Modifying the Time Information of a NodeB

This describes how to modify the time information of a NodeB, including the time zone of the

NodeB, daylight saving policy, and SNTP synchronization period.

NEs Involved NodeB

Prerequisite


Preparation

l Time zone of the NodeB

l The daylight saving policy of the NodeB location

l SNTP synchronization period

Procedure

Step 1 On the NodeB LMT, run the LST TZ command to view the time zone of the NodeB.

If... Then...

The result shows that the time zone is incorrect, Go to Step 2.

The result shows that the time zone is correct, Go to Step 4.

RAN




5-5



Step 2 On the NodeB LMT, run the SET TZ command to modify the NodeB time zone and daylight

saving time settings.

When modifying the daylight saving policy, you need to specify the time offset and the start and

end time of the daylight saving period.

Step 3 On the NodeB LMT, run the LST TZ command to check whether the modification is correct.

Step 4 On the NodeB LMT, run the LST SNTPCLTPARA command to view the information about

the SNTP client.

If... Then...

The result is inconsistent with the SNTP server information, Go to Step 5.

The result is consistent with the SNTP server information, Finish this task.

Step 5 On the NodeB LMT, run the SET SNTPCLTPARA command to modify the information about

the SNTP client.

Step 6 On the NodeB LMT, run the LST SNTPCLTPARA command to check whether the SNTP

client information is correct.

----End

5.3 Reconfiguring a Cell

This describes how to reconfigure a cell, including cell parameters and channel parameters.

5.3.1 Modifying the Power of a Cell

This describes how to modify the maximum transmit power of a cell or the power of different

channels in the cell.

5.3.2 Modifying Cell Frequencies

This describes how to modify cell frequencies, including UL frequency and DL frequency.

5.3.3 Modifying the Scrambling Code of a Cell

This describes how to modify the DL primary scrambling code of a cell.

5.3.4 Modifying Cell System Message Parameters

This describes how to modify cell system message parameters. The parameters are cell system

information block switch, cell access restriction information, cell selection/reselectioninformation, and cell measurement control information.

5.3.5 Modifying Cell Radio Link Parameters

This describes how to modify cell radio link parameters. The parameters are activation time

offset for radio link synchronization reconfiguration and radio link power.

5.3.6 Modifying Cell Synchronization Parameters

This describes how to modify the cell synchronization parameters.

5.3.7 Modifying the Area Information of a Cell

This describes how to modify the area information of a cell. These areas are location areas,

service areas, and routing areas.

5.3.8 Modifying the UTRAN Registration Area of a Cell


RAN




Issue 01 (2009-02-10)



This describes how to modify the UTRAN registration area (URA) of a cell.

5.3.9 Modifying a PRACH

This describes how to modify a Physical Random Access Channel (PRACH) in the cell.

5.3.10 Removing a PRACHThis describes how to remove a PRACH from a logical cell.

5.3.11 Modifying an SCCPCH

This describes how to modify a Secondary-Common Control Physical Channel (SCCPCH) in a

cell.

5.3.12 Removing an SCCPCH

This describes how to remove an SCCPCH from a logical cell.

5.3.13 Renaming a Cell

This describes how to rename a cell.

5.3.14 Changing the ID of a Cell

This describes how to change the ID of a cell.

5.3.1 Modifying the Power of a Cell

This describes how to modify the maximum transmit power of a cell or the power of different

channels in the cell.

NEs InvolvedRNC, NodeB

NOTE

The operation is recommended when the cell load is low. To modify a cell or channel power when the cell

load is high, you must deactivate or block the cell, which causes service disruption of the cell

You can modify the following power parameters:

l Maximum transmit power of the cell

l PCPICH power

l Max./Min. TX power of the PCPICH

l PSCH power

l SSCH power

l AICH power

l PICH power

l BCH power

l PCH power

l Max. TX power of the FACH

RAN




5-7



NOTE

l Among these parameters, the Physical Common Pilot Channel (PCPICH) power, Max./Min. TX

power of the PCPICH, and Max. TX power of the cell are absolute values. The rest of the parameters

are power offsets from the PCPICH power.

l If the cell is in service, modifying the Max. TX power of the cell or the PCPICH/PSCH /SSCH/BCH power can trigger the CELL RECONFIGURATION process on the Iub interface.

l If the Max. TX power of the cell at the RNC is greater than that at the NodeB, the logical cell cannot

be set up or the cell reconfiguration process fails.

l If the Max. TX power of the cell at the RNC is too small, the cell reconfiguration process fails.

l It is recommended that the Max. TX power of the RNC and NodeB be the same.

If the Secondary-Common Control Physical Channel (SCCPCH) or Physical Random Access

Channel (PRACH) is in service, modifying the Max. TX power of the FACH or the PCH/PICH/

AICH power can trigger the COMMON TRANSPORT CHANNEL RECONFIGURATION

process on the Iub interface.

Prerequisite

l The RNC and the NodeB work properly.








Preparation

None

Procedure

l Modify the maximum transmit power of the cell.

1. On the RNC LMT, run the LST CELL command to view the maximum transmit

power of the logical cell.

2. On the RNC LMT, run the MOD CELL command to modify the maximum transmit

power of the logical cell.

3. On the NodeB LMT, run theLST LOCELL command to view the maximum transmit

power of the local cell that corresponds to the logical cell.

4. On the NodeB LMT, run the MOD LOCELLcommand to change the maximum

transmit power of the local cell that corresponds to the logical cell.

5. On the NodeB LMT, run the LST CELL and LST LOCELL commands to check

whether the modification is successful.

l Modify the transmit power of the PCPICH.

1. On the RNC LMT, run the LST PCPICH command to view the transmit power of

the PCPICH.

2. Run the MOD CELL command to modify the transmit power of the PCPICH.

3. Run the LST SCCPCH command to check whether the modification is successful.


RAN




Issue 01 (2009-02-10)



l Modify the maximum transmit power of the PCPICH.


the PCPICH.

2. Run the MOD CELL command to modify the transmit power of the PCPICH.

3. Run the LST PCPICH command to check whether the modification is successful.

l Modify the minimum transmit power of the PCPICH.


the PCPICH.

2. Run the MOD PCPICHPWR command to modify the transmit power of the PCPICH.

3. Run the LST PCPICH command to check whether the modification is successful.

l Modify the power of the PSCH.

1. On the RNC LMT, run the LST PSCH command to view the power of the PSCH.

2. Run the MOD CELL command to modify the power of the PSCH.

3. Run the LST PSCH command to check whether the modification is successful.

l Modify the power of the SSCH.

1. On the RNC LMT, run the LST SSCH command to view the power of the SSCH.

2. Run the MOD CELL command to modify the power of the SSCH.

3. Run the LST SSCH command to check whether the modification is successful.

l Modify the power offset of the AICH.

1. On the RNC LMT, run the LST CHPWROFFSET command to view the power offset

of the AICH.

2. Run the MOD AICHPWROFFSET command to modify the power offset of theAICH.

3. Run the LST CHPWROFFSET command to check whether the modification is

successful.

l Modify the power offset of the PICH.

1. On the RNC LMT, run the LST CHPWROFFSET command to view the power offset

of the PICH.

2. Run the MOD PICHPWROFFSET command to modify the power offset of the

PICH.

3. Run the LST CHPWROFFSET command to check whether the modification is

successful.

l Modify the transmit power of the BCH.

1. On the RNC LMT, run the LST BCH command to view the power of the BCH.

2. Run the MOD CELL command to modify the power of the BCH.

3. Run the LST BCH command to check whether the modification is successful.

l Modify the power of the PCH.

1. On the RNC LMT, run the LST PCH command to view the power of the PCH.

2. Run the MOD SCCPCH command to modify the power of the PCH.

3. Run the LST PCH command to check whether the modification is successful.

l Modify the maximum transmit power of the FACH.

RAN




5-9



1. On the RNC LMT, run the LST FACH command to view the maximum transmit

power of the FACH.

2. Run the MOD SCCPCH command to modify the maximum transmit power of the

FACH.

3. Run the LST FACH command to check whether the modification is successful.

----End

5.3.2 Modifying Cell Frequencies

This describes how to modify cell frequencies, including UL frequency and DL frequency.


NOTE

The services in the cell are disrupted during the operation.

When the cell frequency is changed, the neighboring relations are deleted. Plan and add the

neighboring cells by referring to 5.4 Reconfiguring Neighboring Cells.

Prerequisite









Preparation

None.

Procedure

Step 1 On the RNC LMT:

1. Run the HO CELL command to forcibly hand over the UEs from the cell to a neighboring

cell.

2. Run the DEA CELL command to deactivate the cell.

3. Run the RMV NRELATION command to remove the bidirectional neighboring relations

of the cell.

NOTE

The RMV NRELATION command can only remove the bidirectional neighboring relations of the

cell in only one RNC. To remove the relationship between the existing cell and the neighboring cells

in other RNC/BSC, use this command on that RNC/BSC.

4. Run the MOD CELLSETUP command to modify cell frequencies.

5. Run the LST CELL command to check whether the modification is correct.


RAN




Issue 01 (2009-02-10)



Step 2 On the NodeB LMT, run the MOD LOCELL command to modify cell frequencies.

Step 3 On the RNC LMT, run the ACT CELL command to activate the cell.

Step 4 On the RNC LMT, run the DSP CELL command to check whether the status of the cell is

normal.

Step 5 Reconfigure the neighboring cell data after the cell frequencies are changed by referring to 5.4

Reconfiguring Neighboring Cells.

----End

5.3.3 Modifying the Scrambling Code of a Cell

This describes how to modify the DL primary scrambling code of a cell.

NEs InvolvedRNC

NOTE

The services in the cell are disrupted during the operation.

Prerequisite









Preparation

None.

Procedure

Step 1 On the RNC LMT, run the HO CELL command to forcibly hand over the UEs in a cell to a

neighboring cell.

Step 2 Run the DEA CELL command to deactivate the cell.

Step 3 Run the LST CELL command to view the basic data of the cell.

Step 4 Run the MOD CELLSETUP command to modify the primary DL scrambling code of the cell.

Step 5 Run the ACT CELL command to activate the cell.

Step 6 Run the LST CELL command to check whether the modification is successful.

----End

RAN




5-11



5.3.4 Modifying Cell System Message Parameters

This describes how to modify cell system message parameters. The parameters are cell system

information block switch, cell access restriction information, cell selection/reselection

information, and cell measurement control information.

NEs InvolvedRNC

NOTE

The system information attributes depend on the cell performance. Do not modify the attributes unless you

fully understand the impact.

Prerequisite


l

The current user has the RNC control right concerning data configuration management.The control right of data configuration management can be queried through LST






Preparation

None.

Procedure

l Modify cell system information block switch.

1. On the RNC LMT, run the LST CELLSIBSWITCH command to view the cell

system information switches.

2. Run the MOD CELLSIBSWITCH command to modify the cell system information

switches.

3. Run the LST CELLSIBSWITCH command to check whether the modification is

correct.

l Modify the cell access restriction information.

1. Run the LST CELLACCESSSTRICT command to view the cell access restriction

information.

2. Run the MOD CELLACCESSSTRICT command to modify the cell access

restriction information.

3. Run the LST CELLACCESSSTRICT command to check whether the modification

is correct.

l Modify the cell selection/reselection information.

1. Run the LST CELLSELRESEL command to view the cell selection/reselection

information.

2. Run the MOD CELLSELRESEL command to modify the cell selection/reselectioninformation.


RAN




Issue 01 (2009-02-10)



3. Run the LST CELLSELRESEL command to check whether the modification is

correct.

l Modify the cell measurement control information.

1. Run the LST CELLMEAS command to view the cell measurement control

information.

2. Run the MOD CELLMEAS command to modify the cell measurement control

information.

3. Run the LST CELLMEAS command to check whether the modification is correct.

----End

5.3.5 Modifying Cell Radio Link Parameters

This describes how to modify cell radio link parameters. The parameters are activation time

offset for radio link synchronization reconfiguration and radio link power.

NEs InvolvedRNC

When the cell is activated, you can view, modify, remove, or add the cell radio link power of

the CS/PS traffic rate. The new settings are sent to the NodeB in the RADIO LINK SETUP

message through the Iub interface. The settings are used to control the power. If there are no

data matching the traffic rate requested by the UE in the database, the system uses the power

data with the closest rate.

Prerequisite


l The current user has the RNC control right concerning data configuration management.The control right of data configuration management can be queried through LST






Preparation

None.

Procedure

Set the cell radio link power.

1. Run the LST CELLRLPWR command to view the settings of the cell radio link power.

2. Set the cell radio link power.

– Run the MOD CELLRLPWR command to modify cell DL transmit power.

– Run the ADD CELLRLPWR command to add cell DL transmit power parameter.

– Run the RMV CELLRLPWR command to remove cell DL transmit power.

3. Run the LST CELLRLPWR command to check whether the modification is correct.

----End

RAN




5-13



5.3.6 Modifying Cell Synchronization Parameters

This describes how to modify the cell synchronization parameters.

NEs InvolvedRNC

NOTE

The services in the cell are disrupted during the operation. Therefore, operate with caution.

CAUTION

Modifying the cell synchronization attributes can trigger the CELL RECONFIGURATION

process on the Iub interface, that is, the NodeB logical OM process.

Cell synchronization parameters include:

l NInsyncInd: Number of successive synchronization indications

l NOutsyncInd: Number of successive out-of-synchronization indications

l TRlFailure: Timer length of radio link failure

Prerequisite








Preparation

None.

Procedure

Step 1 On the RNC LMT, run the LST CELL command to view the cell information.

Step 2 Run the MOD CELL command to modify the cell synchronization parameters.


----End

5.3.7 Modifying the Area Information of a Cell

This describes how to modify the area information of a cell. These areas are location areas,service areas, and routing areas.


RAN




Issue 01 (2009-02-10)



NEs InvolvedRNC

Prerequisite









Preparationl ID of the cell to be modified

l New location area, service area, and routing area of the cell

Procedure

Step 1 Run the LST CELL command to view the basic data of the cell.

Step 2 Run the MOD CELLACINFO command to modify the LAC, RAC, and SAC of the cell.


----End

5.3.8 Modifying the UTRAN Registration Area of a Cell

This describes how to modify the UTRAN registration area (URA) of a cell.

NEs InvolvedRNC

A cell can belong to up to eight URAs. After the cell is activated, you can add the URA

dynamically according to your requirements.

Prerequisite


l The specified URA ID of the cell must be configured as the global information.

You can check the information through the LST URA command. If it is not configured,

add it by referring to 4.3.4 Adding a UTRAN Registration Area.






RAN




5-15





Preparation

None.

Procedure

Step 1 On the RNC LMT, run the LST CELLURA command to view the cell URA information.

Step 2 Configure the cell URA.

If... Then...

You need to remove a cell URA, Run the RMV CELLURA command.

You need to add a cell URA, Run the ADD CELLURA command.

You need to modify the cell URA from

A to B,

1. Run the ADD CELLURA to add the reference

of the cell to URA B.

2. Run the RMV CELLURA to remove the

reference of the cell to URA A.

Step 3 Run the LST CELLURA command to check whether the modification is correct.

----End

5.3.9 Modifying a PRACH

This describes how to modify a Physical Random Access Channel (PRACH) in the cell.

NEs InvolvedRNC

NOTE

The impact on the services varies according to the modified parameters.

NOTE

To make the settings of the PRACH take effect after the modification, you need to use the DEA

PRACH command to deactivate the PRACH before the modification. After the modification, run the ACT

PRACH command to activate the PRACH.

Prerequisite

l The PRACH to be modified exists in the cell.








RAN




Issue 01 (2009-02-10)





Preparation

If the TF of the RACH carried on the PRACH is changed, calculate the CTFC of the PRACH

before carrying out this task.

Procedure

l To modify the preamble signature, RACH subchannel ID or PRACH timeslot format,

perform the following steps:

1. Run the LST PRACH command to view the configuration information of the

specified PRACH.

2. Run the MOD PRACH command to reconfigure the PRACH.

NOTE

If the PRACH is in service, operations in previous steps can trigger the COMMON

TRANSPORT CHANNEL RECONFIGURATION process on the Iub interface.

3. Run the LST PRACH command to check whether the modification is correct.

l To modify the Uu interface update parameters of the PRACH, perform the following steps:

1. Run the LST PRACH command to view the Uu interface update parameters of the

PRACH.

2. Run the MOD PRACHUUPARAS command to modify the Uu interface update

parameters of the PRACH.


l To modify the access service class information of the PRACH, perform the following steps:

1. Run the LST PRACH command to view the access service class information of the

PRACH.

2. Run the MOD PRACHASC command to modify the access service class information

of the PRACH.


l To modify the information on the mapping between the access class and access service

class of the PRACH, perform the following steps:

1. Run the LST PRACH command to view the information on the mapping between the

access class and access service class of the PRACH.2. Run the MOD PRACHACTOASCMAP command to modify the information on the

mapping between the access class and access service class of the PRACH.


l To modify the CTFC information of the PRACH, perform the following steps:

1. If the cell is in service and there is only one PRACH in the cell, run the HO CELL

command to forcibly hand over the UEs from the cell to a neighboring cell.

2. If the cell is in activated state and there is only one PRACH in the cell, run the DEA

CELL command to deactivate the cell.

3. If the PRACH is in active state, run the DEA PRACH command to deactivate it.

4. Run the LST PRACH command to view the CTFC information of the PRACH.

RAN




5-17



5. To remove the CTFC information of the PRACH, run the RMV PRACHTFC

command.

6. To add the CTFC information of the PRACH, run the ADD PRACHTFC command.

7. Run the ACT PRACH command to activate the PRACH.

8. Run the ACT CELL command to activate the cell.

9. Run the LST PRACH command to check whether the operation result is correct.

l To modify the timeslot format of the PRACH, perform the following steps:






4. Run the LST PRACH command to view the timeslot format information of the

PRACH.5. To remove the timeslot format information of the PRACH, run the RMV

PRACHSLOTFORMAT command.

6. To add the timeslot format information of the PRACH, run the ADD

PRACHSLOTFORMAT command.



9. Run the LST PRACH command to check whether the operation result is correct.

l To modify the random back-off lower limit, random back-off upper limit and maximum

number of preamble loops of the RACH, perform the following steps:






4. Run the LST RACH command to view the TX parameters of the RACH.

5. Run the MOD RACH command to modify the TX parameters of the RACH.



8. Run the LST RACH command to check whether the operation result is correct.

l To modify the basic data of the RACH, perform the following steps:






4. Run the LST RACH command to view the RACH information.

5. To remove the basic data of the RACH, run the RMV RACH command. Ensure that

the dynamic TX format set information of the RACH is removed before this operation.

6. To add the basic data of the RACH, run the ADD RACH command.


RAN




Issue 01 (2009-02-10)



7. Run the ADD RACHDYNTFS command to restore the dynamic TX format set

information of the RACH, and then run the ACT PRACH command to activate the

PRACH.



l To modify the dynamic TX format set information of the RACH, perform the following

steps:






4. Run the LST RACH command to view the RACH information.

5. To remove the dynamic TX format set information of the RACH, run the RMV

RACHDYNTFS command.

6. To add the dynamic TX format set information of the RACH, run the ADD

RACHDYNTFS command.




l To modify the AICH information, perform the following steps:



2. If the cell is in activated state and there is only one PRACH in the cell, run the DEACELL command to deactivate the cell.


4. Run the LST AICH command to view the AICH information.

5. To remove the AICH, run the RMV AICH command.

6. To add the AICH, run the ADD AICH command.



9. Run the LST AICH command to check whether the operation result is correct.

----End

5.3.10 Removing a PRACH

This describes how to remove a PRACH from a logical cell.

NEs InvolvedRNC

NOTE

In this operation, you have to consider the following:

l If the cell has two PRACHs before the removal, the services on the PRACH that is now removed are

disrupted.

l If the cell has only one PRACH before the removal, the cell becomes unavailable after the removal.

RAN




5-19



NOTE

Whether to activate the cell before running the RMV PRACH command depends on the number of

PRACHs in the cell. You are advised, however, to deactivate the cell.

l If the cell has only one PRACH, you must deactivate the cell before running the RMV PRACH

command.

l If there are two PRACHs in the cell, you can run the RMV PRACH command to remove a PRACH

with the larger channel ID when the cell is in activated state.

Prerequisite









Preparation

None.

Procedure

Step 1 On the RNC LMT, run the LST PRACH command to view the PRACH of the cell.

Step 2 Perform different steps based on the status of the cell.

If... Then...

The cell is in service, and you want to

remove the PRACH when the cell is in

activated state,

Run the DEA PRACH to deactivate the

PRACH to be removed.

If the cell is in activated state and you want

to remove the PRACH when the cell is indeactivated state,

1. Forcibly hand over the UEs from the cell to

a neighboring cell by running the HOCELL command.

2. Run the DEA CELL command to deactivate

the cell.

Step 3 Run the RMV SCCPCH command to remove the SCCPCH.

Step 4 If the cell has another PRACH and you need the deactivated cell to re-enter the service state,

run the ACT CELL command to activate the cell.

Step 5 Run the LST PRACH command to check whether the operation is successful.

----End


RAN




Issue 01 (2009-02-10)



5.3.11 Modifying an SCCPCH

This describes how to modify a Secondary-Common Control Physical Channel (SCCPCH) in a

cell.

NEs InvolvedRNC

NOTE

The impact varies with the parameters to be modified. Do not modify the SCCPCH unless you fully

understand the consequences.

CAUTION

Recalculate the CTFC of the SCCPCH if any one of the following parameters changes: number

of FACHs, number of PCHs, TFS of the FACH, and TFS of the PCH.

Prerequisite








Preparation

None.

Procedure

l Modify the attributes of the PCH and FACH.

1. Run the LST FACH command or LST PCH command to view the data of the

SCCPCH to be modified.

2. Run the MOD SCCPCH command to reconfigure the SCCPCH.

3. Run the LST FACH command or LST PCH command to check whether the

modification is correct.

l Modify the CTFC of the SCCPCH.

NOTE

If the cell in service has only one SCCPCH, or if it has two SCCPCHs but the one with the smaller

channel ID needs to be modified, then do as follows:

1. Run the HO CELL command to forcibly hand over the UEs from the cell to a neighboring cell.


3. After the modification, run the ACT CELL command to activate the cell.

1. Run the DEA SCCPCH command to deactivate the SCCPCH.

RAN




5-21



2. Run the LST SCCPCH command to view the CTFC of the SCCPCH.

3. Modify the CTFC of the SCCPCH.

If... Then...

You need to remove theCTFC of the SCCPCH,

Run the RMV SCCPCHTFC command.

You need to add the CTFC

of the SCCPCH,

Run the ADD SCCPCHTFC command.

4. Run the LST SCCPCH command to check whether the modification is correct.

5. Run the ACT SCCPCH command to activate the SCCPCH.

l Modify the basic data of the FACH.

NOTE


channel ID needs to be modified, then do as follows:1. Run the HO CELL command to forcibly hand over the UEs from the cell to a neighboring cell.




2. Run the LST FACH command to view the basic data of the FACH.

3. Modify the basic data of the FACH.

– Before removing the basic data of the FACH, ensure that the FACH dynamic

transport format, FACH logical channel, and carried CTCH are removed.

– You can restore the removed basic data of the FACH. The data includes the FACH

dynamic transport format, FACH logical channel, and carried CTCH.

If... Then...

You need to remove

the basic data of the

FACH,

Run the RMV FACH command.

You need to add the

basic data of the

SCCPCH,

Run the ADD FACH command.

4. Run the LST FACH command to check whether the modification is correct.


l Modify the FACH dynamic transport format set.

NOTE







2. Run the LST FACH command to view the FACH dynamic transport format set.

3. Modify the dynamic transport format set of the FACH.


RAN




Issue 01 (2009-02-10)



If... Then...

You need to remove the

FACH dynamic transport

format set,

Run the RMV FACHDYNTFS command.

You need to add the

FACH dynamic transport

format set,

Run the ADD FACHDYNTFS command.

4. Run the LST FACH command to check whether the FACH dynamic transport format

is correctly modified.


l Modify the logical channels mapped to the FACH.

NOTE







2. Run the LST FACH command to view the logical channels mapped to the FACH.

3. Modify the logical channels mapped to the FACH.

– Before removing the logical channels mapped to the FACH, ensure that the CTCH

carried on the FACH is removed.

–

You can restore the removed logical channels mapped to the FACH. For example,you can restore the CTCH carried on the FACH.

If... Then...

You need to delete the logical

channels mapped to the FACH,

Run the RMV FACHLOCH command.

You need to add the logical

channels mapped to the FACH,

Run the ADD FACHLOCH command.

4. Run the LST FACH command to check whether the information about the logical

channels mapped to the FACH is correct.


l Modify the basic data of the PCH.

NOTE







2. Run the LST PCH command to view the data of the PCH.

3. Modify the basic data of the PCH.

RAN




5-23



– Before removing the basic data of the PCH, ensure that the dynamic transport

format set of the PCH is removed.

– You can restore the removed basic data of the PCH, such as the dynamic transport

format set of the PCH.

If... Then...

You need to delete the basic data of the

PCH,

Run the RMV PCH command.

You need to add the basic data of the

PCH,

Run the ADD PCH command.

4. Run the LST PCH command to check whether the modification is correct.


l Modify the PCH dynamic transport format set.

NOTE







2. Run the LST PCH command to view the PCH dynamic transport format set.

3. Modify the dynamic transport format set of the PCH.

If... Then...

You need to remove the PCH dynamic

transport format set,

Run the RMV PCHDYNTFS

command.

You need to add the PCH dynamic

transport format set,

Run the ADD PCHDYNTFS

command.

4. Run the LST PCH command to check whether the PCH dynamic transport format set

is correctly modified.


l Modify the data of the PICH.

NOTE







2. Run the LST PICH command to view the data of the PICH.

3. Modify the PICH data.


RAN




Issue 01 (2009-02-10)



If... Then...

You need to remove the

PICH data,

Run the RMV PICH command.

You need to add the PICHdata,

Run the ADD PICH command.

4. Run the LST PICH command to check whether the modification is correct.


----End

5.3.12 Removing an SCCPCH

This describes how to remove an SCCPCH from a logical cell.

NEs InvolvedRNC

NOTE

In this operation, you have to consider the following:

l If the cell has only one SCCPCH before the removal, call drop or out-of-control failure occurs on

non-dedicated channels and no new UE can be admitted.

l If the cell has two SCCPCHs, the SCCPCH with smaller ID number must carry the only PCH in the

cell. This is ensured when the SCCPCHs are created.

l You are advised to deactivate the cell before removing an SCCPCH.

Prerequisite









Preparation

None.

Procedure

Step 1 Run the LST SCCPCH command to view the SCCPCHs in the cell.

Step 2 Perform different steps based on the status of the cell.

RAN




5-25



If... Then...

The cell is in service, and you want to

remove the SCCPCH when the cell is in

activated state,

Run the DEA SCCPCH to deactivate the

PRACH to be removed.

The cell is in activated state, and you do

not want to remove the SCCPCH when the

cell is in deactivated state,

1. Run the HO CELL command to forcibly

hand over the UEs from the cell to a

neighboring cell.

2. Run the DEA CELL command to deactivate

the cell.

Step 3 Run the LST FACH command to check whether the FACH carries the CTCH.

Step 4 If the FACH carries the CTCH, run the DEA CELLCBS command to deactivate cell CBS, and

then run the RMV CTCH command to remove the CTCH.

Step 5 Run the RMV SCCPCH command to remove the SCCPCH.

Step 6 If there is still another SCCPCH in the cell after one SCCPCH is removed, and you need to make

the cell enter the service state, run the ACT CELL command to activate the cell.

Step 7 Run the LST SCCPCH command to check whether the SCCPCH is removed from the cell.

----End

5.3.13 Renaming a Cell

This describes how to rename a cell.


Prerequisite

l The basic data of the cell is added.

Run the LST CELL command to view the basic data of the cell. If the basic data of the

cell is not configured, run the ADD CELLSETUP to add the basic data of the cell.

l

The RNC and the NodeB work properly.l The current user has the RNC control right concerning data configuration management.







Preparation

None.


RAN




Issue 01 (2009-02-10)



Procedure

Step 1 Run the LST CELL command to view the cell name.

Step 2 Run the MOD CELLNAME command to modify the cell name.

Step 3 Run the LST CELL command to check whether the modification is correct.

----End

5.3.14 Changing the ID of a Cell

This describes how to change the ID of a cell.


NOTE

This operation requires that the cell is in deactivated state, and therefore it affects the current services in

the cell.

Prerequisite


l The cell is configured at the RNC.








Preparation

None.

Procedure

Step 1 Run the DSP CELL command to view the status of the cell.

If... Then...

The cell is in activated state, Go to Step 2.

The cell is not in activated state, Go to Step 4.

Step 2 Run the HO CELL command to forcibly hand over the UEs from the cell to a neighboring cell.

Step 3 Run the DEA CELL command to deactivate the cell.

Step 4 Run the MOD CELLID command to modify the cell ID.

RAN




5-27



Step 5 Run the LST CELL command to check that the modification is correct.

Step 6 To make the cell enter the service state, run the ACT CELL command to reactivate the cell,

and then run the DSP CELL command to check that the status of the cell is normal.

----End

5.4 Reconfiguring Neighboring Cells

This describes how to reconfigure neighboring cells, including intra-frequency cells, inter-

frequency cells, and neighboring GSM cells.

5.4.1 Adding an Intra-Frequency Neighboring Cell

This describes how to add an intra-frequency neighboring cell to a specified cell.

5.4.2 Adding an Inter-Frequency Neighboring Cell

This describes how to add an inter-frequency neighboring cell to a specified cell.

5.4.3 Adding a Neighboring GSM Cell

This describes how to add a GSM cell on the coverage edge of the WCDMA.

5.4.4 Modifying a Neighboring Cell

This describes how to modify the neighboring cell of a specified cell. For example, you can

change the neighboring cell of cell A from cell B to cell C.

5.4.5 Removing a Neighboring Cell

This describes how to remove the neighboring relationship of a cell. The neighboring

relationship are classified into unidirectional neighboring relation and bidirectional neighboring

relation.

5.4.1 Adding an Intra-Frequency Neighboring Cell

This describes how to add an intra-frequency neighboring cell to a specified cell.

NEs InvolvedRNC

CAUTION

The primary scrambling codes of intra-frequency neighboring cells of a cell should be differentfrom each other.

Prerequisite

l The cell to be configured with the neighboring relationship is available.


l If the neighboring cell is at a neighboring RNC, the basic data of that RNC is configured

at the RNC where the cell is located.

You can run the LST NRNC command to view the basic data of the neighboring RNC. If

the basic data does not exist, you can run the ADD NRNC command to add the basic dataof the neighboring RNC at the local RNC.


RAN




Issue 01 (2009-02-10)










Preparation

Table 5-1 lists the data to be prepared for an intra-frequency neighboring cell.

Table 5-1 Data to be prepared for an intra-frequency neighboring cell

Cell (Cell ID/RNC ID) Intra-Frequency Cell (Cell ID/RNC ID)

If the neighboring cell is located at another RNC, also prepare the data as listed in Table 5-2.

Table 5-2 Data prepared for the neighboring cell at another RNC

RNCID

CellID

CellName

PrimaryScrambling Code

MobileCountryCode

MobileNetworkCode

Frequency (UL/DL)

LAC/ RAC/SAC

URA

Procedure

Step 1 Check the intra-frequency neighboring cells planned in Table 5-2.

If... Then...

The cell is located at a neighboring RNC, Go to Step 2.

No cell is located at a neighboring RNC, Go to Step 4.

Step 2 Run the LST NRNCCELL command to check whether all the parameters listed in Table 5-2

are configured at the local RNC.

RAN




5-29



If... Then...

There are cells that are not configured at

the RNC,

1. Run the ADD NRNCCELL command to add

the parameters of a neighboring RNC cell. If

multiple basic parameters of the neighboring

RNC cell are not configured, repeat this step.

2. Go to Step 3.

All cells are configured at the RNC, Go to Step 3.

Step 3 Run the LST NRNCURA command, enter Neighboring RNC ID, and then check whether all

the URAs listed in Table 5-2 are configured at the RNC.

If... Then...

There are URA IDs that are not

configured,

1. Run the ADD NRNCURA command to add

the URA ID at the neighboring RNC. If

multiple URA IDs are not configured, repeat

this step.

2. Go to Step 4.

All URA IDs are configured, Go to Step 4.

Step 4 Run the ADD INTRAFREQNCELL command to add an intra-frequency neighboring cell.

If there are multiple intra-frequency neighboring cells listed in Table 5-1, repeat this step.

Step 5 Run the LST INTRAFREQNCELL command to check whether the data configured for the

neighboring cell is correct.

----End

5.4.2 Adding an Inter-Frequency Neighboring Cell

This describes how to add an inter-frequency neighboring cell to a specified cell.

NEs InvolvedRNC

CAUTION

l Any two inter-frequency neighboring cells of a cell must have different UL frequencies, DL

frequencies, or scrambling codes at the same time.

l The maximum number of pairs formed by a UL frequency and a DL frequency of that inter-

frequency neighboring cell is two.


RAN




Issue 01 (2009-02-10)



Prerequisite



l If the neighboring cell is at a neighboring RNC, the basic data of that RNC is configuredat the RNC where the cell is located.

You can run the LST NRNC command to view the basic data of the neighboring RNC. If

the basic data does not exist, you can run the ADD NRNC command to add the basic data

of the neighboring RNC at the local RNC.







Preparation

Table 5-3 lists the data to be prepared for an inter-frequency neighboring cell.

Table 5-3 Data prepared for an inter-frequency neighboring cell

Cell (Cell ID/RNC ID) Inter-Frequency Cell (Cell ID/RNC ID)

If the inter-frequency neighboring cell belongs to another RNC, also prepare the data as listed

in Table 5-4.

Table 5-4 Data prepared for the neighboring cell at another RNC

RNCID

CellID

CellName

PrimaryScrambling

Code

MobileCountry

Code

MobileNetwork

Code

Frequency(UL/ DL)

LAC/ RAC/ SAC

URA

Procedure

Step 1 Check the inter-frequency cell planned in Table 5-4.

If... Then...

The cell is located at a neighboring RNC, Go to Step 2.

RAN




5-31



If... Then...

No cell is located at a neighboring RNC, Go to Step 4.

Step 2 Run the LST NRNCCELL command to check whether the basic parameters of the neighboring

cell at another RNC listed in Table 5-4 are configured at the local RNC.

If... Then...

There are basic parameters that are not

configured on the neighboring RNC cell,

1. Run the ADD NRNCCELL command to add

the parameters of a neighboring RNC cell. If

multiple basic parameters of the neighboring

RNC cell are not configured, repeat this step.

2. Go to Step 3.

All basic parameters of the neighboring

RNC cell are configured,

Go to Step 3.

Step 3 Run the LST NRNCURA command and enter Neighboring RNC ID to check whether all URAs

listed in Table 5-4 are configured at the local RNC.

If... Then...

There are URA IDs that are not

configured,

1. Run the ADD NRNCURA command to add

the URA ID at the neighboring RNC. If

multiple URA IDs are not configured, repeat

this step.

2. Go to Step 4.

All URA IDs are configured, Go to Step 4.

Step 4 Run the ADD INTERFREQNCELL command to add an inter-frequency neighboring cell.

If there are multiple inter-frequency neighboring cells listed in Table 5-3, repeat this step.

Step 5 Run the LST INTER FREQNCELL command to check whether the data of the inter-frequency

cell is correct.

----End

5.4.3 Adding a Neighboring GSM Cell

This describes how to add a GSM cell on the coverage edge of the WCDMA.

NEs InvolvedRNC


RAN




Issue 01 (2009-02-10)



CAUTION

l Any two neighboring GSM cells of a cell must have different network color codes, BS

color codes, frequencies, or band indicators.l A maximum of 32 neighboring GSM cells can be added.

Prerequisite








The curr ent data configuration mode of the RNC can be queried through the LST


Preparation

Table 5-5 lists the basic data of the GSM cell.

Table 5-5 Basic data of the GSM cell

GSMCellIndex

GSMCellName

MobileCountryCode

MobileNetworkCode

LocationAreaCode

GSMCell IDNumbering

NetworkColorCode

BSColorCode

Frequency No.ofInter-SystemCell

Inter-SystemCellType

Table 5-6 lists the data to be prepared for adding a neighboring GSM cell to a WCDMA cellthat is located at the RNC.

Table 5-6 Data prepared for a neighboring GSM cell

Cell ID GSM Cell Index

Procedure

Step 1 Run the LST GSMCELL command to check whether all the data listed in Table 5-5 isconfigured at the RNC where the cell is located.

RAN




5-33



If... Then...

The basic data of the neighboring GSM

cell is not configured,

1. Run the ADD GSMCELL command to add

the basic data of the neighboring GSM cell.

2. Go to Step 2.

The basic data of the neighboring GSM

cell is configured,

Go to Step 2.

Step 2 Run the ADD GSMNCELL command to add a neighboring GSM cell.

Step 3 Run the LST GSMNCELL command to check whether the data of the neighboring GSM cell

is correct.

----End

5.4.4 Modifying a Neighboring Cell

This describes how to modify the neighboring cell of a specified cell. For example, you can

change the neighboring cell of cell A from cell B to cell C.

Modifying a neighboring cell consists of the following sub-tasks:

1. Adding a neighboring cell based on the type of neighboring cell

l 5.4.1 Adding an Intra-Frequency Neighboring Cell

l 5.4.2 Adding an Inter-Frequency Neighboring Cell

l 5.4.3 Adding a Neighboring GSM Cell

2. 5.4.5 Removing a Neighboring Cell.

5.4.5 Removing a Neighboring Cell

This describes how to remove the neighboring relationship of a cell. The neighboring

relationship are classif ied into unidirectional neighboring relation and bidirectional neighboring

relation.

NEs InvolvedRNC

NOTE

l The services are not affected when the unidirectional neighboring relations are removed.

l The services are disrupted when the bidirectional neighboring relations are removed.

NOTE

Assume that the RNC has cell A and cell B, and the two cells are neighboring cells. To remove the

unidirectional neighboring cell of cell A is to remove the neighboring cell B from cell A, and the neighboring

cell A is not removed from cell B. Removing the bidirectional neighboring cell of cell A is to remove the

neighboring cell B from cell A, and the neighboring cell A is also removed from cell B.

Prerequisite




RAN




Issue 01 (2009-02-10)








Preparation

None.

Procedure

l Remove the unidirectional intra-frequency neighboring relationship of a cell.

1. On the RNC LMT, run the LST INTRAFREQNCELL command to view intra-

frequency neighboring cells.

2. Run the RMV INTRAFREQNCELL command to remove an intra-frequency

neighboring cell.

3. Run the LST INTRAFREQNCELL command to check whether the neighboring cell

is correctly removed.

l Remove the unidirectional inter-frequency neighboring relationship of a cell.

1. On the RNC LMT, run the LST INTERFREQNCELL command to view inter-

frequency neighboring cells of the specified cell.

2. Run the RMV INTERFREQNCELL command to remove an inter-frequency

neighboring cell.

3. Run the LST INTERFREQNCELL command to check whether the neighboring cell

is removed.

l Remove the unidirectional neighboring GSM cells of a cell.

1. On the RNC LMT, run the LST GSMNCELL command to view the neighboring

GSM cells of the specified cell.

2. Run the RMV GSMNCELL command to remove a neighboring GSM cell.

3. Run the LST GSMNCELL command to check whether the neighboring cell is

removed.

l Remove the bidirectional neighboring relationship between the current cell and other cells.

1. If the current cell is in service, run the HO CELL command to forcibly hand over the

UEs from this cell to another cell.2. If the current cell is in activated state, run the DEA CELL command to deactivate the

cell.

3. Run the RMV NRELATION command and specify one or several types of the

neighboring cells in Neighboring Cell Type, and then remove the bidirectional

neighboring relationship between the current cell and other cells within the RNC.

NOTE

l The RMV NRELATION command can remove only the bidirectional neighboring cells

that are controlled by the local RNC.

l To remove the bidirectional neighboring cells that are controlled by another RNC or BSC,

you need to perform the operation on the other RNC or BSC.

4. Run the ACT CELL command to make the cell enter the service state again.

RAN




5-35



5. Run the DSP CELL command to check whether the status of the cell is correct.

----End

5.5 Reconfiguring Timeslot Cross ConnectionThis describes how to reconfigure timeslot cross connection on an RNC and on a NodeB.

5.5.1 Configuring a Timeslot Cross Connection on an RNC

This describes how to configure a timeslot cross connection between narrow-band transmission

devices.

5.5.2 Configuring a Timeslot Cross Connection on a NodeB

This describes how to add a timeslot cross connection on a running NodeB, thus providing a

transfer channel between narrow-band transmission devices.

5.5.1 Configuring a Timeslot Cross Connection on an RNC

This describes how to configure a timeslot cross connection between narrow-band transmission

devices.

NEs InvolvedRNC

Prerequisite

l The E1/T1 links on the AEUa or PEUa board are configured as fractional ATM, fractional

IMA, or PPP links. In addition, these links have idle timeslots.l The RNC works properly.








Preparation

l Source link number and destination link number

l Source timeslot number and destination timeslot number

Procedure

Step 1 On the RNC LMT, run the ADD TSCROSS command to add a timeslot cross connection to the

AEUa or PEUa board. If there are multiple timeslot cross connections, repeat this step.

Step 2 Run the LST TSCROSS command to check whether the configuration is correct.

----End


RAN




Issue 01 (2009-02-10)



5.5.2 Configuring a Timeslot Cross Connection on a NodeB

This describes how to add a timeslot cross connection on a running NodeB, thus providing a

transfer channel between narrow-band transmission devices.

NEs Involved NodeB

Prerequisite

l The E1/T1 link is configured as a fractional ATM or PPP link. The link has idle timeslots.

l The NodeB works properly.

Preparation

l Number of the E1/T1 port connected to the narrow-band transmission equipment

l Bandwidth of the channel used to transfer the data of the narrow-band transmissionequipment

Each timeslot can provide the 64 kbit/s bandwidth.

Procedure

Step 1 On the NodeB LMT, run the ADD TSCROSS command to add a timeslot cross connection to

the NodeB.

Step 2 On the NodeB LMT, run the LST TSCROSS to check whether the configuration is correct.

----End

RAN




5-37






About This Chapter

This describes the reference for RAN reconfiguration.

6.1 Transport Network Timers

This describes the interface protocol timers.

6.2 Cell-Related Concepts

This introduces the cell-related concepts.

6.3 RAN Clock Synchronization Configuration

This describes how to configure RAN clock synchronization. The configuration involves theRNC clock sources, RNC clock strata, switching policy of RNC clock sources, and switching

policy of NodeB clock sources.

RAN

Reconfiguration Guide 6 RAN Reconfiguration Reference



6-1



6.1 Transport Network Timers

This describes the interface protocol timers.

6.1.1 SCCP Timers

SCCP timers refer to the timers related to the SCCP protocol.

6.1.2 SAAL Timers

SAAL timers are used during information transmission on the SAAL links.

6.1.3 AAL2 Timers

AAL2 timers are used by the AAL2 signaling entities for request and indication during the AAL2

link connection.

6.1.1 SCCP Timers

SCCP timers refer to the timers related to the SCCP protocol.

You can modify the default settings of the SCCP timers according to your requirements.

Command: SET SCCPTMR

6.1.2 SAAL Timers

SAAL timers are used during information transmission on the SAAL links.

Command: ADD SAALLNK

6.1.3 AAL2 TimersAAL2 timers are used by the AAL2 signaling entities for request and indication during the AAL2

link connection.

You can modify the default settings of the AAL2 timers according to your requirements.

Command: SET AAL2TMR

6.2 Cell-Related Concepts

This introduces the cell-related concepts.

6.2.1 Definitions of Sector, Carrier, and Cell

A sector is the smallest radio coverage area unit, which is covered by one or more radio carriers.

Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallest

serving unit for UE access.

6.2.2 Definitions of Local Cell and Logical Cell

In the 3GPP, a service-providing cell is referred to as a local cell in implementation sense and

as a logical cell in logical resource management sense.

6.2.3 Logical Cell Model

This describes the logical cell model that is instructive for the configuration of logical cells.

6.2.4 Areas of Logical Cells


RAN




Issue 01 (2009-02-10)



A logical cell must exist in a Location Area (LA), a Service Area (SA), a Routing Area (RA),

and a UTRAN Registration Area (URA).

6.2.5 Physical Resources of Cells

This describes the physical resources of cells from the perspective of sector RF resources and

the cell resource pool.

6.2.6 Cell/Channel Activation and Deactivation

This describes cell activation, cell deactivation, channel activation, and channel deactivation.

6.2.7 Definition of Neighboring Cell

A neighboring cell is associated with a specific cell. There are three types of neighboring cell

for UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, and

neighboring GSM cell.

6.2.1 Definitions of Sector, Carrier, and Cell

A sector is the smallest radio coverage area unit, which is covered by one or more radio carriers.

Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallest

serving unit for UE access.

Sectors are of two types: omnidirectional sector and directional sector. The omnidirectional

sector provides coverage for small traffic. It covers the 360º circle area with the omnidirectional

antenna in the center of the circle. As the traffic grows, the omnidirectional sector is split into

three or six directional sectors. The directional sectors are covered by directional antennas. For

a 3-sector cell, each of the three directional antennas covers a 120º sector area. For a 6-sector

cell, each of the six directional antennas covers a 60º sector area. In fact, the azimuth of the

antenna is greater than the theoretical value, and therefore there is overlap between the sectors.

Number of cells supported by a NodeB = number of sectors x number of carriers in each sector.

Figure 6-1 shows the typical 3 x 2 configuration. The whole circle area is split into three sectors:sector 0, sector 1, and sector 2. Each sector has two carriers, and each carrier forms a cell. There

are six cells in total.

Frequency multiplexing is allowed in a WCDMA system if different downlink primary

scrambling codes are used in neighboring cells of different sectors that use the same frequency.

The different downlink primary scrambling codes lower the interference between cells.

Figure 6-1 shows the relations between sector, frequency, and cell.

RAN




6-3



Figure 6-1 Relations between sector, frequency, and cell

6.2.2 Definitions of Local Cell and Logical Cell

In the 3GPP, a service-providing cell is referred to as a local cell in implementation sense and

as a logical cell in logical resource management sense.

Local Cell

A local cell is a combination of physical resources, such as hardware resources and software

resources, in a cell of a NodeB. A local cell is related to the physical implementation of a device.

NodeBs from different vendors have different ways of providing physical resources for cells.Therefore, the concept of logical cell is proposed by the 3GPP to ensure that the RNC can control

the radio resources in certain cells through the standard Iub interface. These cells are carried on

NodeBs from different vendors.

Logical Cell

A logical cell is a standard logical model that helps the RNC control the radio resources in a

cell. The model is independent of local cell implementation and ensures that the Iub interface is

an open interface. For details about the logical cell model, refer to 6.2.3 Logical Cell Model.

The parameters of a local cell are configured at and managed by the NodeB. The parameters of

a logical cell are configured at and managed by the RNC. Each logical cell has a one-to-onerelationship with each local cell.


RAN




Issue 01 (2009-02-10)



6.2.3 Logical Cell Model

This describes the logical cell model that is instructive for the configuration of logical cells.

Figure 6-2 shows the logical cell configuration model. The number above the square is the

quantity of the entities that serve as lower-level nodes. The number below the square is the

quantity of the entities that serve as upper-level nodes.

Figure 6-2 Logical cell configuration model

NOTE

l P-CPICH: Primary Common Pilot Channel

l PSCH: Primary Synchronization Channel

l SSCH: Secondary Synchronization Channel

l P-CCPCH: Primary Common Control Physical Channel

l PICH: Paging Indicator Channel

l S-CCPCH: Secondary Common Control Physical Channel

l PRACH: Physical Random Access Channel

l AICH: Acquisition Indication Channel

l BCH: Broadcast Channel

l PCH: Paging Channel

l FACH: Forward Access Channel

l RACH: Random Access Channel

6.2.4 Areas of Logical Cells

A logical cell must exist in a Location Area (LA), a Service Area (SA), a Routing Area (RA),

and a UTRAN Registration Area (URA).

NOTE

For details about the areas, refer to Area Identifiers.

l A cell can belong to only one LA.

l A cell can belong to only one RA.

l A cell can belong to only one CS/PS SA.

l A cell can belong to only one CBS SA.

RAN




6-5



l A cell can belong to one to eight URAs.

6.2.5 Physical Resources of Cells

This describes the physical resources of cells from the perspective of sector RF resources and

the cell resource pool.

Cell RF Resources

The NodeB provides the physical RF resources of the cells. Figure 6-3 shows the physical RF

resources mapped onto the NodeB from the sector. Each sector uses one directional antenna.

Each directional antenna provides 2-way receive channels to enhance the receiving sensitivity,

and the two channels can work in mutual diversity mode.

l The RF module of distributed NodeB is RRU or PicoRRU (PRRU).

l The RF module of the macro NodeB is composed of the MAFU and MTRU. The MAFU

and MTRU are always in pairs.


RAN




Issue 01 (2009-02-10)



Figure 6-3 Physical RF resources mapped from sectors onto NodeB

Figure 6-3 shows the mapping between the sectors and the RF module for a 2-carrier NodeB in

2-way receive diversity mode. The relationship may vary according to the NodeB configurations.

Figure 6-4 shows the rules for mapping the BTS3812E sectors and the MAFU/MTRU.

l 1 MAFU + 1 MTRU for 1 sector: The NodeB supports 6 sectors. This sector mode supports

1-carrier or 2-carrier 1T2R configuration.

l 2 MAFUs + 2 MTRUs for 1 sector: The NodeB supports 3 sectors. This sector mode

supports 1-carrier or 2-carrier 1T2R or 2T2R configuration, and 3-carrier or 4-carrier 1T2R

configuration. You may change the external interface connections of the MTRU and MAFUto make it support 1-carrier or 2-carrier 2T4R configuration.

RAN




6-7



l 4 MAFUs + 4 MTRUs for 1 sector: The NodeB supports 1 to 3 sectors. Combined cabinet

is required when more than one sector is involved. This sector mode supports 3-carrier or

4-carrier 2T4R configuration.

Figure 6-4 Mapping rules between the BTS3812E sectors and the MAFUs/MTRUs

Cell Resource PoolThe macro NodeB puts the UL/DL signal processing resources in the resource pool for the cells

to share. When you configure the cell, specify the type of the resource pool. The two types of

resource pool are as follows:

l GEN_POOL: UL/DL baseband resource pool that consists of the HBBI, HULP, and HDLP

boards. This type of resource pool is commonly used. You must specify the uplink baseband

resource group.

l GRP_POOL: UL/DL baseband resource pool that consists of the HBOI board in slot 15.

You need not specify the uplink baseband resource group.

Uplink baseband resource group. Uplink baseband resource group has the following features

and requirements:

l One uplink baseband resource group consists of one or more uplink processing units. One

uplink processing unit corresponds to one HBBI/HBOI/HULP board or one BBU module.

l The cells in one uplink baseband resource group share the uplink resources. Each uplink

baseband resource group processes signals of up to six cells in 2-way and enhanced 2-way

modes. Each uplink baseband resource group processes signals of up to three cells in 4-

way and economic 4-way modes.

l The softer handover can be performed between the cells in the same uplink baseband

resource group. You are advised to add the intra-frequency cells to the same group.

l The number of resource groups should be kept as small as possible. For example, for a 3 x

4 NodeB, you are advised to divide the resource pools into two groups with each groupsupporting six cells.


RAN




Issue 01 (2009-02-10)



6.2.6 Cell/Channel Activation and Deactivation

This describes cell activation, cell deactivation, channel activation, and channel deactivation.

NOTE

l Before activating the HSDPA function of a cell, you need to run the ADD CELLHSDPA command

to add the HSDPA parameters of the cell.

l Before activating the HSUPA function of a cell, you need to run the ADD CELLHSUPA command

to add the HSUPA parameters of the cell.

l As an additional feature of a cell, the HSDPA function needs to be activated by running the ACT

CELLHSDPA command.

l As an additional feature of a cell, the HSUPA function needs to be activated by running the ACT

CELLHSUPA command.

Cell Activation

Before the logical cell is activated, the system checks whether the cell data in the database is

consistent and complete.

If... Then...

The cell data is consistent and

complete,

The cell is successfully activated, and the cell is in active

state. In this case,

l If the data transmission on the Iub interface is normal

and the NodeB works properly, the process to set up

the cell is triggered on the Iub interface, and the cell

on both the RNC and the NodeB will be in service

state.l If the data transmission on the Iub interface is

abnormal or the NodeB does not work properly, the

process to set up the cell is not triggered on the Iub

interface. Though the cell is in active state, it cannot

provide services.

The cell data is inconsistent or

incomplete,

The cell fails to be activated, and the cell is in deactivated

state.

Cell Deactivation

If the logical cell is not activated after configuration, the cell fails to be activated, or the logical

cell is deactivated, the logical cell is in deactivated state.

NOTE

Before deactivating the logical cell, you should perform the forced handover of UEs from the logical cell

and block the logical cell to avoid the impact on subscribers during deactivating the logical cell.

Deactivating a serving cell triggers the cell deletion process on the Iub interface. Then, the cell

is unable to provide services.

Deactivating a channel and deleting a channel are two different operations.

l

Deactivating a cell triggers the cell deletion process on the Iub interface, but still keeps thecell data in the database. You can set up the cell again by activating the cell.

RAN




6-9



l Deleting a cell deletes the cell data from the database permanently. In addition, this

operation triggers the cell deletion process on the Iub interface.

Channel Activation

After the PRACH or SCCPCH is configured at the RNC, the PRACH or SCCPCH channel is

in active state if the channel is successfully activated.

Before the channel is activated, the system checks whether the channel data in the database is

consistent and complete.

If... Then...

The channel data is consistent

and complete,

The channel is successfully activated, and the channel is in

active state. In this case,

l If the cell where the channel is located is in service state,

activating the channel can trigger the setup of common

transport channel on the Iub interface. Thus, the channel

is also in service state.

l If the cell where the channel is located is in deactivated

state, activating the channel does not trigger the setup of

common transport channel on the Iub interface. If the cell

is activated later, the process is triggered to set up the cell

and common transport channel on the Iub interface to

make them enter the service state at the same time.

The channel data is

inconsistent and incomplete,

The channel fails to be activated, and the channel is in

deactivated state.

Channel Deactivation

If the channel is not activated after configuration, the channel fails to be activated, or the channel

is deactivated, the channel is in deactivated state.

NOTE

If there is only one PRACH or SCCPCH in an active cell, or there are two SCCPCHs but the one carrying

the PCH is deactivated, you must deactivate the cell before deactivating the channel.

Deactivating a serving channel triggers the common transport channel deletion process on the

Iub interface. Then, the channel is unable to provide services.

Deactivating a channel and deleting a channel are two different operations.

l Deactivating a channel triggers the channel deletion process on the Iub interface, but still

keeps the channel data in the database. You can set up the channel again by activating the

channel.

l Deleting a channel deletes the channel data from the database permanently. In addition,

this operation triggers the channel deletion process on the Iub interface.

6.2.7 Definition of Neighboring Cell

A neighboring cell is associated with a specific cell. There are three types of neighboring cell

for UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, andneighboring GSM cell.


RAN




Issue 01 (2009-02-10)



l The intra-frequency neighboring cell refers to a cell that has overlapping coverage with the

serving cell and uses the same carrier frequency as the serving cell.

l The inter-frequency neighboring cell refers to a cell that has overlapping coverage with the

serving cell but uses a different carrier frequency from the serving cell.

l The neighboring GSM cell refers to a cell that is adjacent to the serving cell but belongs toa GSM, General Packet Radio Service (GPRS), or Enhanced Data rates for Global

Evolution (EDGE) system.

6.3 RAN Clock Synchronization Configuration

This describes how to configure RAN clock synchronization. The configuration involves the

RNC clock sources, RNC clock strata, switching policy of RNC clock sources, and switching

policy of NodeB clock sources.

6.3.1 RNC Clock SourcesThe RNC has the following clock sources: Building Integrated Timing Supply System (BITS)

clock, Global Positioning System (GPS) clock, line clock, and external 8 kHz clock.

6.3.2 RNC Clock Source Strata

The RNC clock source strata are classified into four strata, that is, strata 1 to 4, in descending

order by priority.

6.3.3 Switching Policy of RNC Clock Sources

The clock sources are classified into current clock sources and non-current clock sources. Based

on the switching policy, the system clock is fixed at the current clock source or switched to

another non-current clock source.

6.3.4 Switching Policy of NodeB Clock SourcesThe NodeB may have multiple clock sources, but it has only one working clock source at a time.

You need to set the clock source working mode to Free or Manual.

6.3.1 RNC Clock Sources

The RNC has the following clock sources: Building Integrated Timing Supply System (BITS)

clock, Global Positioning System (GPS) clock, line clock, and external 8 kHz clock.

BITS Clock

The BITS clock is of three types: 2 MHz, 2 Mbit/s, and 1.5 Mbit/s. The BITS clock has twoinput modes: BITS 1 and BITS 2. The RNC obtains the BITS timing signals through the timing

signal input ports on the GCUa/GCGa board.

NOTE

The 2 MHz and 2 Mbit/s timing signals are E1 timing signals, and the 1.5 Mbit/s timing signals are T1

timing signals.

GPS Clock

The GPS clock provides 1 Pulse Per Second (PPS) timing signals. The RNC obtains the GPS

timing signals from the GPS system. The GCGa board is configured with a GPS card, and the

RNC receives the GPS signals at the ANT port on the GCGa.

RAN




6-11



NOTE

The GCUa board is not configured with a GPS card. Therefore, when the RNC is configured with the GCUa

instead of the GCGa, the GPS clock is unavailable to the RNC.

Line Clock

The line clock is an 8 kHz clock that the Iu interface board in the RSS subrack provides for the

GCUa/GCGa board through the backplane channels. The line clock has two input modes: line

1 and line 2.

External 8 kHz Clock

Through the COM1 port on the GCUa/GCGa board, the RNC obtains 8 kHz standard timing

signals in RS-422 level mode from an external device.

Local OscillatorIf the RNC fails to obtain any external clock, the RNC can obtain its working timing signals

from the local oscillator.

NOTE

The timing signals generated by the local oscillator, however, do not meet the requirements of NodeBs for

clock precision. Therefore, when the RNC uses such timing signals, the NodeBs fail to obtain the timing

signals that meet the precision requirements from the RNC.

6.3.2 RNC Clock Source Strata

The RNC clock source strata are classified into four strata, that is, strata 1 to 4, in descending

order by priority.

During RNC clock source configuration, adhere to the following principles:

l Clock sources and clock source priorities have a one-to-one correspondence.

l The LINE1_8KHZ and LINE2_8KHZ clock sources are locked at the interface board and

sent to the backplane. Each of the 8 KHz clocks can have only one clock source.

In practice, the RNC usually uses line clocks. The system can also use the BITS or GPS clock

in the equipment room if they are available.

6.3.3 Switching Policy of RNC Clock Sources

The clock sources are classified into current clock sources and non-current clock sources. Basedon the switching policy, the system clock is fixed at the current clock source or switched to

another non-current clock source.

Command: SET CLKMODE

l Manual mode

In manual mode, a clock source is specified as the current clock source. The system cannot

use another clock source even if this clock source fails.

l Automatic mode

In automatic mode, you do not need to specify a clock source as the current clock source.

The system automatically selects a clock source with the highest priority. For example, if the current clock source with the priority of PRI3 is faulty, the system selects a clock source


RAN




Issue 01 (2009-02-10)



with the priority of PRI4. If the faulty clock source recovers, the system switches the clock

source to PRI3. If all the clock sources are faulty, the system is switched to the free-run

mode. When the clock sources recover, the system is switched to the AUTO mode.

6.3.4 Switching Policy of NodeB Clock SourcesThe NodeB may have multiple clock sources, but it has only one working clock source at a time.

You need to set the clock source working mode to Free or Manual.

l MANUAL

If the switching policy is set to Manual, the NodeB uses the clock source. If the clock source

is faulty, the NodeB works in free-run mode. When the clock source is recovered, the NodeB

reselects it.

l FREE

If the switching policy is set to Free, the NodeB clock works in free-run mode.

RAN




6-13





7Optional Function Configuration Reference

About This Chapter

This describes how to configure optional function.

7.1 96 HSDPA Users Per Cell

This describes the procedure for enabling and disabling the function.

7.2 96 HSUPA Users Per Cell


7.3 MSCH and MSCH Scheduling


7.4 Enhanced CELL_FACH


7.5 CPC-HS-SCCH Less Operation


7.6 CPC-DTX/DRX


7.7 MOCN


RAN

Reconfiguration Guide 7 Optional Function Configuration Reference



7-1



7.1 96 HSDPA Users Per CellThis describes the procedure for enabling and disabling the function.

Prerequisite

The associated license file is ready.

Context

This feature does not require extra hardware.

Procedure

Step 1 Update the license by performing the following sub-steps:

1. Download the license to the BAM active workspace\FTP\license through FTP.

2. Run the ACT LICENSE command on the M2000 or the RNC LMT to activate the new

license.

Step 2 Activate 96 HSDPA users per cell:

Table 7-1 Activate

Operation Order MML Command Description

1 ADD CELLHSDPA or

MOD CELLHSDPA

Set the HSDPA attributes of

this cell.

2 ACT CELLHSDPA Activate the HSDPA of this

cell.

3 MOD CELLCAC Set the number of HSDPA

users of one cell.

Example:MOD CELLCAC: CellId=1,

MaxHSDSCHUserNum=96;

Step 3 Disable 96 HSDPA users per cell:

Table 7-2 Disable


1 ACT LICENSE Set

96_HSDPA_USERS_PER

_CELL to off.

----End

7.2 96 HSUPA Users Per CellThis describes the procedure for enabling and disabling the function.


RAN




Issue 01 (2009-02-10)



Prerequisite


ContextThis feature does not require extra hardware.

Procedure




license.

Step 2 Activate 96 HSUPA users per cell:

Table 7-3 Activate


1 ADD CELLHSUPA or

MOD CELLHSUPA

Set the HSUPA attributes of

this cell.

2 ACT CELLHSUPA Activate the HSUPA of this

cell.

3 MOD CELLCAC Set the number of HSUPA

users of one cell.Example:MOD CELLCAC: CellId=1,

MaxHSUPAUserNum=96;

Step 3 Disable 96 HSUPA users per cell:

Table 7-4 Disable


1 ACT LICENSE Set

96_HSUPA_USERS_PER _CELL to off.

----End

7.3 MSCH and MSCH Scheduling


Prerequisite


RAN




7-3



Context


ProcedureStep 1 Update the license by performing the following sub-steps:



license.

Step 2 Activate MSCH and MSCH Scheduling:

Table 7-5 Activate

Operation Order MML Command Description1 SET MBMSSWITCH Set MbmsSwitch,

MbmsIubSharingSwitch,

and MschSwitchForMtch-

Multi to ON.

2 SET MSCHPARA Set the MSCH scheduling

parameters.

3 SET MSCH Set the static parameters of

FACH.

4 SET MSCHDYNTFS Set the dynamic parametersof FACH.

5 SET MSCHFACH Set the parameters of FACH.

Step 3 Disable MSCH and MSCH Scheduling:

Table 7-6 Disable


1 ACT LICENSE Set

MSCH_SCHEDULING tooff.

----End

7.4 Enhanced CELL_FACH


Prerequisite



RAN




Issue 01 (2009-02-10)



Context


Procedure




license.

Step 2 Activate Enhanced CELL_FACH:

Table 7-7 Activate


1 ADD CELLHSDPA Set the HSDPA parameters

of this cell.

2 ADD CELLEFACH Set the FACH parameters of

this cell.

3 ACT CELLEFACH Activate the function.

Step 3 Disable MSCH and MSCH Scheduling:

Table 7-8 Disable


1 ACT LICENSE Set

ENHANCED_CELL_FAC

H to off.

----End

7.5 CPC-HS-SCCH Less Operation


Prerequisite


Context


Procedure



RAN




7-5




license.

Step 2 Activate CPC-HS-SCCH Less Operation:

Table 7-9 Activate


1 SET

CORRMALGOSWITCH

Set

CFG_HSPA_HSSCCH_L

ESS_OP_SWITCH to ON.

Step 3 Disable CPC-HS-SCCH Less Operation:

Table 7-10 Disable


1 ACT LICENSE Set CPC_HS_SCCH to off.

----End

7.6 CPC-DTX/DRX


Prerequisite


Context


Procedure



2. Run the ACT LICENSE command on the M2000 or the RNC LMT to activate the newlicense.

Step 2 Activate CPC-DTX/DRX:

Table 7-11 Activate


1 SET

CORRMALGOSWITCH

Set

CFG_HSPA_DTX_DRX_

SWITCH to ON.

Step 3 Disable CPC-DTX/DRX:


RAN




Issue 01 (2009-02-10)



Table 7-12 Disable


1 ACT LICENSE Set CPC_DTX_DRX to off.

----End

7.7 MOCN


Prerequisite


Context


Procedure




license.

Step 2 Activate MOCN:

Table 7-13 Activate


1 SET

OPERATORSHARING-

MODE

Set MOCNSupport to YES.

Step 3 Disable MOCN:

RAN


Date post:	02-Apr-2018
Category:	Documents
Upload:	jan-novak
View:	222 times
Download:	0 times

RAN Reconfiguration Guide(RAN11.0_01)

Documents