Training Document_RAN15.0 BTS3803E Initial Data Configuration_V1.0_20130929

Course namePage*
Course Code
Pan Feng (employee ID: 00137724) Nie Caiyi (employee ID: 00211383)
2013-09-29
XXX
New
N-*
www.huawei.com
RAN15.0 BTS3803E WCDMA Initial Configuration
Course Name
Course Name
N-*
Copyright © 2013 Huawei Technologies Co., Ltd. All rights reserved.
References
BTS3803E WCDMA Product Documentation
Page*
N-*
Objectives
Upon completion of this course, you will be able to:
Understand the method and process of BTS3803E initial configuration.
Understand the main steps of configuring the BTS3803E using the CME.
Page*
Contents
Overview
Overview
NodeB initial configuration is implemented after installation of the NodeB hardware is complete. It is intended for the compilation of a data configuration file (.xml) based on the hardware configuration, network planning, data negotiation with other network elements, and configuration data.
To ensure that the NodeB initial configuration file necessary to make the NodeB operate properly must meet the following requirements:
The data is complete and accurate, and is consistent with the configuration of physical devices.
The data of the Iub transport layer is consistent with that on the RNC side so that data exchange between the NodeB and the RNC can be completed.
Page*
BTS3803E Initial Configuration Methods
The CME provides two configuration methods: single configuration and batch configuration. Operations and processing mechanisms for the two configuration methods are different.
Creating a Single Base Station
The CME allows you to create a single base station by using the wizard, system template, and general configuration window.
Creating Base Stations in Batches
This part This section describes how to create base stations in batches based on a summary data file on the CME. You can create base stations in batches by using a summary data file, radio data planning file, system template, and tool for customizing summary data files.
Page*
Creating a Single Base Station
The CME allows you to create a single base station by using the wizard, system template, and general configuration window.
Mechanism for Creating a Single Base Station
Start the base station creation wizard on the CME and configure differentiated data among base stations, such as the name, RAT, version, and template of a base station. Then, create a base station based on default data in the correlated base station template.
After data is initially configured, reconfigure the data in the general configuration window, such as device, transport, and radio data. Cell data is not created in the wizard any longer. Instead, the cell data is configured in the carrier resource management window.
The following figure shows the mechanism for creating a single base station.
Mechanism for creating a single base station
Page*
Elements in the Base Station Creation Wizard
You need to select options according to NE types when using the wizard. Related concepts are as follows:
Site: indicates the object you create. The CME allows you to create one site each time.
NE: matches an OM channel (OMCH). Each OMCH corresponds to one NE. You can create multiple NEs during base station creation, which constitute one base station. One NE corresponds to one tab page in the base station creation wizard.
Creating Base Stations in Batches
This part describes how to create base stations in batches based on a summary data file on the CME. You can create base stations in batches by using a summary data file, system template, and tool for customizing summary data files.
You can use the tool for customizing summary data files to customize parameters whose values are different among base stations, such as the IP address of a transmission port and cell ID at the radio layer, and save the data in a summary data file in XLS format. Then, set parameter values and correlated system template name in the file. Configuration data shared by base stations is read from the template and imported into the CME with the data in the summary data file to create base stations in batches. The created base stations contain only device data, transport data, and sector and cell data at the radio layer. You have to configure external cell and neighbor relationship data by using the radio data planning file.
Base station data has two data sources: summary data file and system template. The two files may have the same managed objects (MOs). Therefore, the following mechanism is provided to merge the two data sources before you import the data:
If MOs have been defined in the summary data file, these MOs are applied.
If an MO is not defined in the summary data file, the MO defined in the system template is applied.
Page*
Users plan and enter values of differentiated parameters of an MO defined in the summary data file. Therefore, other parameters under the MO may have no values. The processing mechanism for these parameters is as follows:
If a primary key parameter of the MO can be found in the base station template, the CME reads the value of the parameter from the base station template and fills in the summary data file.
If a primary key parameter of the MO cannot be found in the base station template, the CME reads the default value of the parameter and fills in the summary data file.
If a primary key parameter of the MO in the summary data file still has no value, a message is displayed, indicating that the data is incomplete.
Course Name
Course Name
N-*
CME Client Mode
CME functions can be started in the following modes: CME client mode and M2000 client mode. For details, see the following table.
Page*
CME client mode
This mode applies to the scenario only when the CME functions are used. In this mode, only the CME functions are started, and the M2000 functions are not started, such as fault management, topology management, and performance management. In this mode, the CME functions can be started using either of the following methods: Starting CME Functions on the M2000 Client in Application Mode Starting the CME Client Directly
M2000 client mode
This mode applies to the scenario when both the CME and M2000 functions are used. In this mode, both the CME functions and M2000 functions (such as fault management, topology management, and performance management) are started.
Contents
Overview
Overall Data Configuration Process
Prepare data
Data to be prepared includes the basic data, device data, transport data, and radio data. The transport data needs to be prepared based on actual transport networking scenarios.
Create a workspace
The CME provides one current data area and allows users to create multiple planned data areas. The current data area is used for synchronizing and saving configuration data on the live network, and you can only view data in the current data area. A planned data area is used for configuring data. Therefore, you need to create a planned data area before configuring data.
Configure NodeB data
NodeB data to be configured includes NodeB basic information, device data, transport data, and radio data. Note: This step varies by creation of a single base station and creation of base stations in batches.
Check data
Verify the validity and integrity of base station configuration data before the data is exported.
Export deployment lists and configuration files
Export configuration files. After NodeB initial configuration is complete on the CME, you have to export the NodeB deployment list and configuration files for future NodeB commissioning. You also have to export incremental scripts on the base station controller side and then use the script executor of the CME to load the scripts to base station controllers for the data to take effect.
Course Name
Course Name
N-*
Contents
Overview
Preparing Data
Basic data: refers to the basic information to be prepared.
Device data: includes BRU data, time data, and clock data.
Transport data of the Iub interface on the RNC side: refers to the transport data which needs to be prepared for the Iub interface on the RNC side.
Transport data: includes the transport data in secure networking and non-secure networking scenarios.
Radio data
Creating a Workspace
Page*
Start the CME. Then, perform the following operations to create a planned data area.
On the menu bar, choose Area Management > Planned Area > Create Planned Area (CME client mode) or CME > Planned Area > Create Planned Area (M2000 client mode). A dialog box is displayed for you to create a planned data area, as shown in the following figure.
Type information about the planned data area to be created, and add the base station controllers or base stations you want to configure to the planned data area.
Click OK. The CME starts to create the planned data area. After the planned data area is created successfully, the CME automatically opens it.
Course Name
Course Name
N-*
Configuring NodeB Data — Creating a Single Base Station
Page*
Step
Description
Configure NodeB basic information
To configure basic information about a single NodeB, you have to create the NodeB by using a system or user-defined template. Information in the template is used as the basic information about the new NodeB. You can reconfigure the information as required.
Configure NodeB device data
This section describes how to configure BTS3803E device data. When configuring BTS3803E device data, if you select a default template for BTS3803E creation, the CME automatically configures the cabinet and mandatory boards in the basic cabinet, and you have to manually configure data of other boards and cabinets. If you select a user-defined template for BTS3803E creation, the BTS3803E device data has been configured according to the data in the template, and you can modify the device data as required.
Configure Iub transport data on the base station controller side
This step is used to configure Iub transport data on the base station controller side on the CME.
Configure NodeB transport data
This step is used to configure transport data between NodeBs and RNCs when IP transmission is applied between them on the CME.
Configure radio data
This step is used to configure NodeB radio data on the CME, including sector and cell data.
Configure Iub transport data on the base station controller side
Configuring NodeB Basic Information – Creating a Single Base Station
NodeB basic information includes basic NodeB attributes, location, and NE maintenance mode.
Page*
On the menu bar of the planned data area, choose CME > UMTS Application > Create Base Station (M2000 client mode) or UMTS Application > Create Base Station (CME client mode). A dialog box is displayed for you to create base stations, as shown in the figure at the right-handed side.
Select a product type of the NodeB from the Product type drop-down list.
Specify NE Name, NE Version, NE Template, Radio Template, RNC Name, and RNC ID.
After the configuration is completed, click Next. The CME starts to create a NodeB.
(Optional) Modify NodeB basic information.
Configuring NodeB Device Data - Creating a Single Base Station
The BTS3803E device data that is configured on the CME includes data about the BRU, time, and clock.
Page*
In the left pane of the planned data area, right-click a NodeB and choose Device Panel from the shortcut menu. A window is displayed for you to configure device data.
On the device panel, right-click a configured BRU module and choose Property from the shortcut menu. A dialog box is displayed for you to set attributes of the BRU module. In the displayed dialog box, click related tabs and configure time data as planned.
Configure time data.
Configure clock data.
1. Device Panel
2. BRU Properties
4. Clock Info
3. Time Zone
Configure Iub transport data on the base station controller side - Creating a Single Base Station
In the left pane of the planned data area, click the BSC6900 or BSC6910 serving the NodeB, as shown in the figure at the right-handed side.
Select an MO to be configured in area 1 based on the planned data.
The Object Group tab page displays the configuration object tree where you can select objects to be configured directly.
The Search tab page helps quickly search for configuration objects. You can type an MO on the tab page. The CME displays the searched MO in the lower part.
Double-click the MO. Parameter information about this MO is displayed on the right pane. Configure the MO based on the planned data.
Click to save the configuration.
Page*
Transmission modes over the Iub interface include IP transmission and transmission resource pool.
Configuring NodeB Transport Data – Creating a Single Base Station
On the CME, the NodeB transport data can be configured using parameter search or protocol stacks.
Note: The NodeB can adopt the IP transmission mode in non-secure networking or secure networking. Configure transport data based on the networking scenarios.
Page*
Transport data configuration using parameter search
In the left pane of the planned data area, click a NodeB. The NE configuration object navigation tree is displayed at the lower side.
Select an MO to be configured in area 1 based on the planned data.
Double-click the MO. Parameter information about this MO is displayed on the right pane. Configure the MO based on the planned data.
Transport data configuration using protocol stacks
the left pane of the planned data area, right-click the NodeB to be configured. Choose IP Transport Layer from the drop-down menu. The NodeB IP Transport Layer tab is displayed.
In area 1, click the related button to select an MO.
In area 2, configure parameters of the selected object.
In area 3, select the configured bearer object or link at the lower layer. The selected record is used as the lower-layer bearer of the MO.
Page*
Configuring NodeB Transport Data – Creating a Single Base Station
Configuring NodeB Radio Data - Creating a Single Base Station
In the left pane of the planned data area, right-click the NodeB to which a cell you want to configure belongs and choose Carrier Resource Management from the shortcut menu. The Carrier Resource Management window is displayed.
Right-click area 3 and choose Add Sector from the shortcut menu. The Add Sector dialog box is displayed.
Right-click a sector in area 3 and choose Add Sector Equipment form the shortcut menu. A window is displayed for you to add sector equipment. You can specify related information about the sector equipment such as the sector equipment ID, sector equipment antenna, and antenna TX/RX type.
Right-click area 2 and choose Create UMTS Cell. UMTS Cell Creation dialog box is displayed. Click
in area 1. Connect a cell to sector equipment to add a cell and sector equipment group.
Page*
Area 4: displays RXU boards.
Area 2: cell configuration area.
Area 5: displays legends. You can click on the toolbar to show or hide the legends.
Area 3: sector configuration area.
Area 6: searches for cells, sectors, and sector equipment.
Procedure of Configuring NodeB Data – Creating Base Stations in Batches
Page*
Step
Description
Exporting sample base station data to a summary data file
Before creating base stations, you have to obtain sample base station data. The CME provides the function of exporting sample base station data to a summary data file.
Edit a summary data file
Edit configuration data in a summary data file as planned before creating base stations.
Import a summary data file
This step is used to create NodeBs in batches by importing a summary data file into the CME.
Exporting Sample Base Station Data to a Summary Data File – Creating Base Stations in Batches
Sample base stations are available in the active planned data area. If no sample base stations are available, you are advised to create sample base stations in GUI mode.
Observe the following rules when you select a base station as the sample base station:
The transmission type of the sample base station is the same as that of the base stations to be created.
The link type and quantity of the sample base station are the same as those of the base stations to be created.
Procedure
On the menu bar of the planned data area, choose UMTS Application > Export Data > Export Base Station Summary Data (CME client mode) or CME > UMTS Application > Export Data > Export Base Station Summary Data (M2000 client mode). A dialog box is displayed for you to export a summary data file.
Select the version of the base station controller to which the sample base stations belong, the version of the sample base stations, and related sample base stations, and click Next.
Select an export mode.
After the export succeeds, click Finish.
Page*
If...
Then...
The summary data file for creating base stations is available
Select Summary data file. Select the summary data file and set a save path.
The summary data file for creating base stations is unavailable
Select Custom MOC. Select objects you want to export and specify a save path for the exported file.
Course Name
Course Name
N-*
Editing a Summary Data File – Creating Base Stations in Batches
The summary data file is an Excel file with multiple sheets containing parameter groups, parameters, and values and is used to configure common data negotiated with operators and transport and cell data on all sites.
Page*
Cover
Describes the type of the summary data file, supported NE versions, and related precautions.
1
NA
1
Base Station Transport Data
Provides planned transport data and NodeB basic information that includes the base station name, site type, and template.
1
UMTS Cell
Provides basic information about a cell, such as the cell ID, name, template, and other parameters.
n (n ≥ 1)
n (n ≥ 1)
Other MOs
You can add a sheet by using the tool for customizing summary data files.
n (n ≥ 1)
n (n ≥ 1)
Pattern
This sheet applies to MOCs with multiple instances. If the number of instances and most parameter values under an MO of different base stations are the same, you can define the MO on the Pattern sheet.
n (n ≥ 1)
1
List
Contrary to the Pattern sheet, the List sheet applies to the scenario where multiple instances of an MO are available. For example, on the user plane, the number of links and link types of an MO of all base stations are different. You can define the MO on the List sheet.
n (n ≥ 1)
n (n ≥ 1)
Importing a Summary Data File – Creating Base Stations in Batches
Specifications and Restrictions
The CME can process data about a maximum of 50 base stations at a time.
The CME does not support overwriting the existing base station data on the live network.
Procedure
On the menu bar of the planned data area, choose UMTS Application > Import Data > Import Base Station Summary Data (CME client mode) or CME > UMTS Application > Import Data > Import Base Station Summary Data (M2000 client mode). A dialog box is displayed for you to create base stations using a summary data file.
Click and select the file you want to import.
Click Next and select base stations you want to create.
Click Next. The CME starts the import.
Page*
Verifying Data
Page*
In the lower part of the window, view the verification results, and reconfigure the incorrect data.
You can double-click the message to locate the data that needs to be reconfigured. Reconfigure the data as prompted until all data verification succeeds.
If you need to...
Verify data of a single base station
In the left pane of the planned data area, right-click a base station whose data you want to verify and choose Check Data from the shortcut menu. The CME starts to verify the data validity and integrity of the base station.
Verify data of multiple base stations
On the menu bar of the planned data area, choose Advanced > Check Data (CME client mode) or CME > Advanced > Check Data (M2000 client mode). A verification dialog box is displayed. In the NE navigation tree in the left pane, select base stations whose data you want to verify to the right pane, and click OK. The CME starts the verification. The CME can verify data of a maximum of 50 base stations at a time. You can select Integrity check in the upper left part of the verification dialog box to verify base station integrity together with validity.
Exporting Configuration Files
Export Incremental Scripts of Base Station Controllers
On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (M2000 client mode). A dialog box is displayed for you to export scripts.
Select NEs for exporting scripts in the left part to the right part.
Specify a folder for saving the scripts.
(Optional) You can type description about the scripts in Script project description.
The CME uses the user-defined information in Script project description as the file name prefix for the file saving the exported scripts to easily identify the exported scripts and identify loaded projects in the script.
Select a mode for starting the script executor.
Do not launch script executor: You need to manually start the script executor to activate scripts after they are exported.
Launch script executor only: After scripts are exported, the CME automatically starts the script executor for you to activate the scripts.
Launch script executor and activate exported project: After scripts are exported, the CME automatically starts the script executor and activates the scripts. You need to select an activation mode.
Click Export. The CME starts to export the MML scripts.
Page*
N-*
Appendix: BTS3803E License Control Items
Page*
License control items are configured based on the optimal configuration of a single BTS3803E. Details are as follows:
Name
Shared/BASIC
Remarks
30
A single cell can be configured with a maximum of 15 license control items HS-PDSCH Code and a single base station supports a maximum of two cells.
HSUPA
1
2
2
2
2
2
controller side

Documents

Training Document_RAN15.0 BTS3803E Initial Data Configuration_V1.0_20130929