24-NodeB Reparent Tool

RAN Feature Description
Table of Contents
Table of Contents
Chapter 24 NodeB Reparent Tool.............................................................................................. 24-1
24.1 Introduction................................................................................................................... 24-1
24.1.1 Definition............................................................................................................. 24-1
24.1.2 Purposes............................................................................................................ 24-1
24.1.3 Benefits............................................................................................................... 24-1
24.1.4 Terms and Abbreviations....................................................................................24-2
24.2 Availability..................................................................................................................... 24-3
24.2.1 Network Elements Involved................................................................................24-3
24.2.2 Software Releases............................................................................................. 24-3
24.2.3 Miscellaneous..................................................................................................... 24-3
24.3 Impact........................................................................................................................... 24-3
24.3.1 On System Performance....................................................................................24-3
24.3.2 On Other Features.............................................................................................. 24-4
24.4 Technical Description.................................................................................................... 24-4
24.4.2 Preparations for NodeB Relocation....................................................................24-5
24.4.3 Execution of NodeB Relocation..........................................................................24-6
24.4.4 Example of NodeB Relocation............................................................................24-6
24.5 Capabilities................................................................................................................. 24-19
24.6 Implementation........................................................................................................... 24-19
24.6.1 Enabling the NodeB Reparent Tool...................................................................24-19
24.6.2 Reconfiguring the NodeB Reparent Tool..........................................................24-19
24.6.3 Disabling the NodeB Reparent Tool..................................................................24-19
24.7 Maintenance Information.............................................................................................24-19
24.7.1 MML Commands..............................................................................................24-19
24.7.2 Alarms............................................................................................................... 24-19
24.7.3 Counters........................................................................................................... 24-20
24.8 References.................................................................................................................. 24-20
Huawei Technologies Proprietary

i
List of Figures
List of Figures
Figure 24-1 Networking for NodeB relocation.....................................................................24-4
Figure 24-2 Preparations for relocating a single NodeB.....................................................24-5
Figure 24-3 Welcome dialog box........................................................................................24-7
Figure 24-4 Selecting a phase............................................................................................ 24-8
Figure 24-5 Setting parameters of the source RNC............................................................24-9
Figure 24-6 Confirming data modification.........................................................................24-10
Figure 24-7 Modifying the interface data in the second tab...............................................24-11
Figure 24-8 Modifying the interface data in the third tab...................................................24-12
Figure 24-9 Generating a NodeB relocation script............................................................24-13
Figure 24-10 Modifying the MML script.............................................................................24-14
Figure 24-11 Checking data validity..................................................................................24-15
Figure 24-12 Confirming the execution result...................................................................24-16
Figure 24-13 Preparation complete...................................................................................24-17

ii
List of Tables
List of Tables
Table 24-1 NEs required for the NodeB Reparent Tool.......................................................24-3
Table 24-2 RAN products and related versions...................................................................24-3

iii
Chapter 24 NodeB Reparent Tool

24.1 Introduction
24.1.1 Definition
When constructing the 3G network system, operators need to relocate NodeBs in a
Radio Network Controller (RNC) or between RNCs.
A NodeB can be relocated in one of the following ways:
Changing the physical location of the NodeB
Changing the physical links between the NodeB and the RNC
24.1.2 Purposes
NodeBs are relocated for the following purposes:
Optimizing network plans in time during network operation
Balancing the load when RNC capacity is expanded during network operation
Balancing the load of WCDMA RNC Business Subracks (WRBSs) by locating

NodeBs that serve hot spots and non-hot spots to one RNC
24.1.3 Benefits
The benefits of the NodeB Reparent Tool are as follows:
The tool enables easy relocation of NodeBs in an RNC or between RNCs.
The RNCs need not to be reset during NodeB relocation. Neither do the NodeBs.
The tool automatically modifies transmission data, network plan data, and
network optimization data, including related data of neighboring RNCs.
NodeB relocation consists of two phases: preparation phase and execution

phase. Operations are performed on the system only in the execution phase so
that it exerts least influence on the system and ensures utmost reliability and
security.
In addition, in case of errors or faults in the preparation phase, the configuration
can be rolled back. Thus, the rollback helps avoid influence on the system and
improve efficiency of the relocation.
A number of NodeBs can be relocated in a single operation.

For NodeB batch relocation between RNCs, the NodeBs must be relocated from
the same source RNC to the same target RNC.
Featuring the wizard, the tool is easy to use because the user only needs to
configure the data on the interface between the NodeB and RNCs.
1
24.1.4 Terms and Abbreviations

I. Terms
Term
Description
Hot spot
A cell that has high traffic and a large quantity of users
Shadow database
A backup database for the original database
Step-by-step execution
An action to relocate NodeBs one by one
Complete execution
An action to relocate NodeBs in a batch
II. Abbreviations
Abbreviation
Full Spelling
AAL2
ATM Adaptation Layer type 2
ATM
Asynchronous Transfer Mode
BAM
Back Administration Module
BSC6800
Huawei RNC Model
FTP
File Transfer Protocol
GGSN
Gateway GPRS Support Node
GUI
Graphic User Interface
HLR
Home Location Register
IMA
Inverse Multiplexing on ATM
IP
Internet Protocol
LMU
Location Measurement Unit
MGW
Media Gateway
MML
Man Machine Language
MSC
Mobile Switching Center
NE
Network Element
RAN
Radio Access Network

2
Abbreviation
Full Spelling
RNC
Radio Network Controller
SGSN
Serving GPRS Support Node
SMLC
Serving Mobile Location Center
UE
User Equipment
UMTS
Universal Mobile Telecommunications System
WCDMA
Wideband Code Division Multiple Access
WRBS
WCDMA RNC Business Subrack
24.2 Availability
24.2.1 Network Elements Involved
Table 1.1 shows the Network Elements (NEs) required for the NodeB Reparent Tool.
Table 1.1 NEs required for the NodeB Reparent Tool
UE
NodeB
RNC
MSC
MGW
SGSN
GGSN
HLR
Server
Note:
: not required
: required
24.2.2 Software Releases

Table 1.1 describes the versions of the RAN products that support the NodeB
Reparent Tool.
Table 1.1 RAN products and related versions
Product
RNC
Version
BSC6800
V100R005 and later releases

3
24.2.3 Miscellaneous
None.
24.3 Impact
24.3.1 On System Performance
The limitations of the NodeB Reparent Tool are as follows:
Currently, bearer types cannot be changed in NodeB relocation by the tool. For
example, an IMA link cannot be changed to a fractional ATM link in NodeB
relocation.
The data after NodeB relocation is consistent with that before the relocation, that
is, no more data is added. To modify such data as neighboring relationship,
execute MML commands or use other tools after relocation.
Any data modification is prohibited during NodeB relocation. Modification on the

data will exert severe impact.
24.3.2 On Other Features

None.
24.4 Technical Description

Figure 1.1 shows the networking for NodeB relocation.

4
BSC
BTS
GSM
cell
Before relocation
RNC 10
CN
NodeB 1
Iur
After relocation
RNC 11
NodeB 2
Cell
Cell
Cell
Figure 1.1 Networking for NodeB relocation

The implementation of the NodeB Reparent Tool depends on the following key
conditions:
Based on relationship between configuration objects, the RNC exports the MML
script of a single NodeB.
The RNC features convenient data backup and restoration.
There is an interactive MML platform based on PYTHON.
24.4.1 Preparations for NodeB Relocation

Figure 1.1 shows the preparation procedure for relocating a single NodeB between
RNCs. Batch NodeB relocation has a similar procedure.

5
NodeB
Reparent Tool
Source RNC
Target RNC
Neighboring
RNC
1. Exports a NodeB-related MML script and creates a shadow database.

4. Generates
interface data from
the MML scripts.
5. Generates new
MML scripts based
on the modified
data.
6. Executes the related MML script.
9. Displays execution
results.
Goes back to step 4,
if any error occurs.
10. Deletes the shadow database, if the data is correct.
Figure 1.1 Preparations for relocating a single NodeB

In the Graphic User Interface (GUI) of the NodeB Reparent Tool, one or more NodeBs
and the relocation type shall be selected. For inter-RNC relocation, because the cell
attributes change in the relocation, the data of the target RNC and neighboring RNC
is also required.
The preparation procedure for relocating a single NodeB is as follows:
1)
Based on the input data and relationship between the NodeB and the source
RNC, the tool exports a related MML script and automatically modifies the
involved cell neighboring relationship. Meanwhile, the tool creates a shadow
database of the current database on the source RNC for rollback and data
check.

6
2)
Based on the input data and relationship between the NodeB and the target
RNC, the tool exports a related MML script and automatically modifies the
involved cell neighboring relationship. Meanwhile, the tool creates a shadow
database of the current database on the target RNC for rollback and data check.
3)
Based on the input data and relationship between the NodeB and neighboring
RNCs, the tool exports a related MML script, and automatically modifies the
involved cell neighboring relationship for each neighboring RNC. Meanwhile, the
tool creates a shadow database of the current database on each neighboring
RNC for rollback and data check.
4)
The tool reads the MML scripts, generates interface data for the NodeB, and
displays the data subject to modification.
5)
Based on the modified interface data, the tool generates new MML scripts.
6)
The tool executes the related new MML script on the shadow database of the
source RNC, and checks the validity of the data.
7)
target RNC, and checks the validity of the data.
8)
neighboring RNC, and checks the validity of the data.
9)
The execution result is confirmed. In case of data error, the tool goes back to
step 4 for data re-modification.
10) If the data is correct, the tool saves the data for execution of the NodeB
relocation and deletes the shadow databases. For inter-RNC relocation, the
source RNC, target RNC, and neighboring RNCs are involved in deleting the
shadow databases, as shown in steps 10 through 12 in Figure 1.1 respectively.
24.4.2 Execution of NodeB Relocation

The tool executes the MML scripts in the set sequence on each RNC to validate the
modified data.
The execution is of the following two types:
Step-by-step execution
The tool relocates the NodeBs one by one. Other NodeBs can be relocated after
a NodeB is relocated.
Complete execution
The tool relocates the NodeBs in a batch.
24.4.3 Example of NodeB Relocation

This section describes using the tool to relocate NodeB 1 from RNC 10 to RNC 11 as
an example. 24.4.1 IFigure 1.1 shows the networking for NodeB relocation.

7
I. Preparing for the NodeB Relocation

To prepare for the NodeB relocation, perform the following steps:
1)
Double-click NodeBReparent.exe in the installation directory of the NodeB

Reparent Tool.
The welcome dialog box is displayed, as shown in Figure 1.1.
Figure 1.1 Welcome dialog box

2)
Click Next.
The Select reparent phase dialog box is displayed, as shown in Figure 2.1.

8
Figure 2.1 Selecting a phase

3)
Click Preparation phase, and then click Next.

The Source RNC and NodeB list dialog box is displayed, as shown in Figure
3.1.

9
Figure 3.1 Setting parameters of the source RNC

4)
Set parameters of the source RNC as follows:
Enter the external virtual IP address of the BAM server in the source RNC.
Enter the password of the operator.
Enter the password of the FTP account.
Enter the name of the NodeB to be relocated.

The name is case sensitive. For batch relocation, mark a comma between
two NodeB names.
Click a relocation type in the Reparent Type drop-down list. The meanings
of the options in the drop-down list are as follows:
-
INTERNAL RNC: to relocate the NodeB to another board of the same

RNC
NEIGHBOURING RNC: to relocate the NodeB to another RNC
In this example, click INTERNAL RNC.

5)
Click Next.

10
The data processing starts. When the MML script for the NodeB relocation is
obtained, the data modification dialog box with the first tab is displayed, as
shown in Figure 5.1.
Figure 5.1 Confirming data modification

6)
Click I want to modify the script of transport layer to modify the interface
data, or click I don't want to modify the script of transport layer not to modify
the interface data. Then click the second tab.
The dialog box with the second tab is displayed, as shown in Figure 6.1.

11
Figure 6.1 Modifying the interface data in the second tab

7)
Modify data in the second tab, and then click the third tab.
The modified data must be consistent with the original data. It is recommended
to keep the original values if there is no invalid data or special need.
The dialog box with the third tab is displayed, as shown in Figure 7.1.

12
Figure 7.1 Modifying the interface data in the third tab

8)
Modify the data in the third tab, and then click Next.
The modified data must be consistent with the original data. It is recommended
to keep the original values if there is no invalid data or special need.
The script generating dialog box is displayed, as shown in Figure 8.1.

13
Figure 8.1 Generating a NodeB relocation script

When the script is generated, the tool processes as follows:
If you select I want to modify the script of transport layer in step 6, the
Please modify script window is displayed, as shown in Figure 8.2. Then,
perform either of the following steps:
Modify the data as required and click OK.
If you do not want to modify the script, click Cancel.
The data validity check dialog box is displayed, as shown in Figure 8.3.
If you select I dont want to modify the script of transport layer in step 6, the
data validity check dialog box is displayed, as shown in Figure 8.3.

14
Figure 8.2 Modifying the MML script

15
Figure 8.3 Checking data validity

When the check is complete, the confirmation dialog box is displayed, listing the
detected errors, as shown in Figure 8.4.

16
Figure 8.4 Confirming the execution result

9)
Confirm the result of MML execution, and then click Next.
If you select No, I will modify the interface data of this NodeB and
reparent again and then click Next, you go back to step 7.
If you select Yes, I confirm the result of MML execution and finish its
work and then click Next, the finish dialog box is displayed, as shown in
Figure 9.1.

17
Figure 9.1 Preparation complete

10) Click Finish.
Caution:
For relocating NodeBs for several times, execute NodeB relocation each time the
preparation is complete. Then prepare the next relocation.
II. Executing the NodeB Relocation

To execute the NodeB relocation, perform the following steps:
1)
Double-click NodeBReparent.exe in the installation directory of the NodeB

Reparent Tool.
The welcome dialog box is displayed, as shown in IFigure 1.1.

18
2)
Click Next.
The Select reparent phase dialog box is displayed, as shown in IFigure 2.1.
3)
Select an execution phase, and then click Next.

The execution result is then displayed.
If you select Execution phase (step by step) and then click Next, then
each time scripts are executed, a dialog box is displayed to confirm starting
the next relocation.
If you select Execution phase (complete) and then click Next, the tool
relocates all the selected NodeBs in a batch.
Note:
You can execute EXP CFGMML to export the scripts before and after the relocation is
executed. Compare the two scripts to find the difference between them.
III. Notes
Note the following when relocating NodeBs:
The source RNC, target RNC, and neighboring RNC must be configured with
neighboring relationship between each other.
If the NodeB to be relocated is configured with a Serving Mobile Location Center

(SMLC) or Location Measurement Unit (LMU) neighboring cell, data loss will
occur when the NodeB is relocated. Then you need to manually configure the
related data, such as the SMLC neighboring cell and LMU neighboring cell.
For a neighboring cell, the maximum number of neighboring RNCs, including the
local RNC, is six. The number of neighboring RNCs might exceed three when all
the neighboring cells are relocated from the source RNC to the target RNC. In
this case, the tool generates an error report during the relocation. Then, you
need to manually configure neighboring relationship to clear the error.
When you confirm the execution result, errors might be reported as data being
invalid or data being used. Such error reports are common, because RNCs
share some resources, such as physical links, neighboring RNC cells, and traffic
record indexes. When exporting scripts, the RNC also exports the scripts of the
shared resources. Thus, you only need to confirm the exporting.
During the NodeB relocation, the tool communicates with multiple RNCs. Thus,
the connection between the tool and RNCs must be ensured. In case of
connection failure, perform the following steps:
-
If the connection fails in relocation preparation, it does not have any impact
on the system. Restart the relocation.
19
If the connection fails in relocation execution, reconnect the tool and RNCs.
Then click Cancel to exit the tool, and restart the tool to execute the scripts.
Check every error reported in script execution.
The execution result in the preparation phase is supposed to be consistent with

that in the execution phase. In case of inconsistency, contact the technical
support engineers of the RNC.
24.5 Capabilities
None.
24.6 Implementation
NodeB relocation is implemented through the NodeB Reparent Tool, which is
released independently. The tool is responsible for modification of related RNC
configuration in the NodeB relocation.
24.6.1 Enabling the NodeB Reparent Tool

I. Hardware Installation
The tool has no special requirement on the hardware.
II. Software Installation

No software installation is required for the tool.
24.6.2 Reconfiguring the NodeB Reparent Tool

None.
24.6.3 Disabling the NodeB Reparent Tool

None.
24.7 Maintenance Information

24.7.1 MML Commands
EXP CFGMML: executed to export MML scripts.
24.7.2 Alarms
None.

20
24.7.3 Counters
None.
24.8 References
None.

21

24-NodeB Reparent Tool

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

24-NodeB Reparent Tool

Uploaded by

Copyright:

Available Formats

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Chapter 24 NodeB Reparent Tool

Chapter 24 NodeB Reparent Tool

Changing the physical location of the NodeB

Optimizing network plans in time during network operation

Balancing the load of WCDMA RNC Business Subracks (WRBSs) by locating

The tool enables easy relocation of NodeBs in an RNC or between RNCs.

NodeB relocation consists of two phases: preparation phase and execution

A number of NodeBs can be relocated in a single operation.

RAN Feature Description

Chapter 24 NodeB Reparent Tool

24.1.4 Terms and Abbreviations

A cell that has high traffic and a large quantity of users

A backup database for the original database

An action to relocate NodeBs one by one

An action to relocate NodeBs in a batch

ATM Adaptation Layer type 2

Asynchronous Transfer Mode

Back Administration Module

Huawei RNC Model

File Transfer Protocol

Gateway GPRS Support Node

Graphic User Interface

Home Location Register

Inverse Multiplexing on ATM

Location Measurement Unit

Man Machine Language

Mobile Switching Center

Radio Access Network

Huawei Technologies Proprietary

RAN Feature Description

Chapter 24 NodeB Reparent Tool

Radio Network Controller

Serving GPRS Support Node

Serving Mobile Location Center

Universal Mobile Telecommunications System

Wideband Code Division Multiple Access

WCDMA RNC Business Subrack

24.2.2 Software Releases

V100R005 and later releases

Huawei Technologies Proprietary

RAN Feature Description

Chapter 24 NodeB Reparent Tool

Any data modification is prohibited during NodeB relocation. Modification on the

24.3.2 On Other Features

24.4 Technical Description

Huawei Technologies Proprietary

RAN Feature Description

Chapter 24 NodeB Reparent Tool

Figure 1.1 Networking for NodeB relocation

The RNC features convenient data backup and restoration.

There is an interactive MML platform based on PYTHON.

24.4.1 Preparations for NodeB Relocation

Huawei Technologies Proprietary

RAN Feature Description

Chapter 24 NodeB Reparent Tool

1. Exports a NodeB-related MML script and creates a shadow database.

Figure 1.1 Preparations for relocating a single NodeB