OWB301700 BTS3900 WCDMA V200R014 Initial Data Configuration Based On CME ISSUE 1.00

BTS3900 WCDMA V200R014 Initial Data Configuration P-0
Confidential Information of Huawei. No Spreading Without Permission




 Third-party NMS:A third-party network management system (NMS), which manages

devices of multiple vendors in an integrated manner.
 Huawei OSS: An OSS system provided by Huawei, which manages multiple NEs on
the access network and core network. The CME is located at this layer.
 RNC, NodeB, BSC, and BTS: Equipment on the radio access network.

 CME client software

 The CME client software displays the GUI and processes the GUI logic. It is
installed on the M2000 client.
 CME application service
 The CME application service, which refers to the CME server software, is
installed on the M2000 server. It implements the following tasks:
 Communicating with the M2000 application software and obtaining NE
information
 Controlling the service flow and performing data configuration by
communicating with the CME client
 Database
 The CME shares one database system with the M2000. The CME database is
in charge of storing NE configuration data.

 Current data area: Used to store the configuration data on the live network. The data
can only be viewed.
 Planned data area: Used by different users for data planning and data configuration.
Users can create multiple planned data areas based on the data in the current data
area to perform different configuration tasks.
 The CME provides a current data area and multiple planned data areas. Multi-area
management improves data configuration efficiency and enables several users to
configure the same NE at the same time.
 The current data area of the CME obtains the configuration data of NEs from the
existing network through the synchronization function.
 Before configuring data, users copy the data of one or more NEs from the current
data area to the planned data areas created by themselves.
 Users perform data planning and data planning in their own planned data areas.
NOTE:
If multiple users configure the data of one NE at the same time, data conflict occurs.
The CME provides a conflict check function to guarantee the data validity.
 After the data planning and data configuration is complete, users save the
configuration data in the planned data areas as configuration scripts. Then,
users activate the scripts for the scripts to take effect on the existing network.
 The current data area of the CME obtains the updated configuration data of
NEs from the existing network through the synchronization function.


 System output window

 The system output window displays the information such as the system
operation logs and the system alarms. The time displayed is the time of the
client. The log, fault, and security information is provided by the server.
Therefore, the displayed time is the time of the server.
 Status bar
 The menu bar shows the main menu of the system.
 Status bar
 The status bar displays the current status information about the system, such
as the current user and the IP address of the connected server.
 Toolbar
 The toolbar shows the shortcut icons for key operation tasks.

 The CME defines different operation authority contents for different maintenance
tasks. An operation can be performed only by authorized users.
 The CME classifies all operations into NE-irrelevant operations and NE-relevant
operations. The authority corresponding to an NE-irrelevant operation is called a
network management application authority. The authority corresponding to an NE-
relevant operation is called a network device authority.
 On the menu bar of the M2000 main window, choose Security > Security
Management. The Security Management interface is displayed .




 Collect NodeB planning data.

 Collect the NodeB hardware device data. The devices include cabinets,
subracks, boards, and RF modules.
 Collect transport data and radio data of the NodeB.
 Collect radio data of the NodeB based on the installed hardware and
the radio network planning.
 Collect the transport data of the NodeB based on the transmission
networking and the Iub data planning template provided with the CME
software.
 Get the NodeB template ready.
 If a Physical NodeB data similar to the planned data is available on the live
network
 Export the physical NodeB data as a user-defined NodeB template.
 If no data is available on the live network
 Select a default template that is similar to the planned data.
 Import this default template to create physical NodeBs. Then, manually
reconfigure the existing data on the GUI based on the planned data.
 Verify that the NodeB configuration data is intact, consistent, and valid.


 Opening the current data area

 Choose Area Management > Current Area > Open Current Area (CME
Client Mode) or CM Express > Current Area > Open Current Area (M2000
Client Mode). The NEs in the current data area are displayed in the navigation
tree.
 In the navigation tree in the left pane, right-click an NE or the sub-node of an
NE, and then choose the data type to be viewed from the shortcut menu. The
corresponding data of the NE is displayed in the right pane.
 Synchronizing the data in the current data area with the data on the live network
 Open the current data area.
 Choose Area Management > Current Area > Synchronize NE (CME Client
Mode) or CM Express > Current Area > Synchronize NE (M2000 Client
Mode). The dialog box for synchronizing NE configuration data is displayed.
This dialog box displays a list of NEs that are connected to the M2000.
 Select one or more NEs.
 Select a data synchronization mode. This step is applicable only to MBSCs.
 Click OK. A dialog box is displayed for you to confirm the synchronization.
 After you confirm the synchronization, the CME starts to upload NE data. The
progress bar and the synchronization information about the NEs are displayed
in the lower part of the dialog box.
 After the synchronization, the dialog box is automatically closed. The CME
main window is displayed.

 Creating a planned data area

 Choose Area Management > Planned Area > Create Planned Area (CME
Client Mode) or CM Express > Planned Area > Create Planned Area
(M2000 Client Mode). A dialog box is displayed for you to create a planned
data area.
 Type a name for the planned data area.
 Select a user group.
 Select an access permission on the planned data area from the Access
Privilege drop-down list.
 Private: Only the creator and administrators can perform operations on
the planned data area.
 Public: The creator, users in the same group with the creator, and
administrators can perform operations on the planned data area.
 (Optional) Select NEs to be added to the planned data area.
 (Optional) Type description of the planned data area.
 Click OK. The CME starts creating the planned data area and then
automatically opens it.

BTS3900 WCDMA V200R014 Initial Data P-17
Configuration

 In the Main View navigation tree in the left pane of the planned data area, select a
UMTS NE.
 Choose CM Express > UMTS Application > Physical NodeB Management >
Create Physical NodeB on the menu bar. The Create Physical NodeB window is
displayed.
 TIP: To create a single physical NodeB, you can also right-click a logical NodeB in the
Main View navigation tree in the left pane of the planned data area and then choose
Create Physical NodeB from the shortcut menu to open the Create Physical NodeB
dialog box.
 Click Add, and then select one or multiple NodeBs.
 Right-click one or multiple records, and then choose Select NodeB Template from
the shortcut menu. The Create Physical NodeB dialog box is displayed. Select the
type, version, and template of the NodeBs respectively from the Series, Version, and
Template drop-down list boxes. Then, click OK.
 Click Next. The CME starts to create physical NodeBs.
 Click Finish to exit the wizard.
 Note: if there is no logical NodeB, need to create a logical NodeB firstly.

 In the Main View navigation tree in the left pane of the planned data area, select an
RNC or MBSC.
 Choose UMTS Application > Physical NodeB Management > Create Physical
NodeB (CME Client Mode) or CM Express > UMTS Application > Physical NodeB
Management > Create Physical NodeB (M2000 Client Mode) on the menu bar. The
Create Physical NodeB window is displayed.
 Click Add and select one or multiple NodeBs.
 Right-click one or more records and choose Select NodeB Template from the
shortcut menu. The Create Physical NodeB dialog box is displayed. Select the type,
version, and template of the NodeB from the Series, Version, and Template drop-
down list boxes, respectively. Then, click OK.
 Click Next. The CME starts the creation.

 In the Main View navigation tree in the left pane of the planned data area, right-click a
physical NodeB and choose Basic Information from the shortcut menu. The basic
information about the physical NodeB is displayed in the right pane.
 The basic information about physical NodeBs is displayed in sheets such as
EquipmentManagement, TransportManagement, RadioManagement,
Time Zone, and Clock Source.
 Based on the planned data, configure basic information about physical NodeBs.

physical NodeB, and choose Device Panel from the shortcut menu. The NodeB
device panel is displayed.
 Click Add Cabinet in the right pane. The Add Cabinet dialog box is displayed. Based
on the planned data, select a cabinet type in the Cabinet Type drop-down list box,
set the cabinet number in the Cabinet No. drop-down list box, enter the description
information in Cabinet Description, and click OK to configure the cabinet.

physical NodeB, and choose Device Panel from the shortcut menu. The device panel
is displayed.
 Configure a CTRLLNK.
 Click Add BBULink in the right pane of the device panel. A dialog box is
displayed for you to add a CTRLLNK.
 Click to configure a CTRLLNK based on onsite physical connection lines.
 Local Cabinet No., Local Subrack No., and Local Slot No.: identify
the cabinet, subrack, and slot for the UMPT board on the leaf node,
respectively.
 Upper Cabinet No., Upper Subrack No., Upper Slot No., and
Upper Port No.: identify the cabinet, subrack, and slot for the UCIU
board on the root node, and the port number of the M port,
respectively.
 Click OK to save the data and exit.
 NOTE: The NodeB allows two BBU3900 subracks to be cascaded. BBU cascading
enables the BBU3900 subrack to transmit operation and maintenance (O&M)
information, service information containing signaling and user data, clock
synchronization information, and baseband data.

• In the cabinet navigation tree in the left pane, select the BBU3900 subrack. Then,
right-click the related slot on the device panel in the right pane based on the type of
the boards to be configured, and choose Add board from the shortcut menu. A dialog
box is displayed for you to set board attributes. Set board parameters based on the
planned data, and click OK to add boards to the BBU3900 subrack.

 Add an RRU chain/ring.
 NOTE:
 You can configure an RRU chain/ring only after configuring the WBBP board.
 Information about the RRU chain tail needs to be configured only when the
RRU chain is in ring topology.

 Configure RFUs or RRUs.

 NOTE:
 You can configure RRUs only after an RRU chain/ring is configured.
 You can configure RFUs only after an RRU chain/ring and an RFU subrack is
configured.
 When configuring the RRU or RFU, you need to configure the numbers of RX
and TX channels for the RRU or RFU.

 (Optional) In the cabinet navigation tree in the left pane, select the cabinet where you
need to configure a monitoring board. Then, right-click the related slot on the device
panel in the right pane, and choose Add monitoring board from the shortcut menu.
A dialog box is displayed for you to set monitoring properties.
 Based on the planned data, set information about the monitoring board, such as
Manager Cabinet No., Manager Subrack No., Manager Port No., and Address.
 Click OK. The configured monitoring boards are displayed in the slot.

 (Optional) Configure a PMU board.
 In the cabinet navigation tree in the left pane, select the cabinet where you need to
configure a PMU board. Then, right-click slot 0 of subrack 7 on the device panel in the
right pane, and choose Add PMU from the shortcut menu. A dialog box is displayed
for you to set PMU board properties.
 Based on the planned data, set the information such as Power System Type,
Manager Cabinet No., Manager Subrack No., Manager Port No., and Address.
 Click OK. The configured PMU board is displayed in the slot.
 (Optional) In the cabinet navigation tree in the left pane, select the cabinet where you
need to configure the PSU board. Then, right-click any of slots 1 to 2, 1 to 6, 1 to 4, or
1 to 3 of subrack 7, and choose Add PSU from the shortcut menu to configure the
PSU board.
 (Optional) Configure batteries.

physical NodeB, and choose ATM Transport Layer from the shortcut menu.
 Click ATMPort and configure the NodeB physical link data based on the onsite plan.
 Based on the onsite plan, configure transport data.
 (Optional, required only when NodeBs are in cascading mode) Click NetWork, and
click the TreeLink PVC tab to configure a treelink PVC.
Object Description
In ATM transmission mode, You must configure at least one type of
Physical link the physical links, such as IMA group, IMA links, UNI links and
fractional ATM links.
Transmission The bandwidth of physical links is allocated to the transmission
resource resource group to carry the data on the control plane, user plane, and
group OM channel.
In ATM transmission mode, the control plane data consists of the data
of SAAL links, and the data of the NCP, CCP, and ALCAP carried by
Control plane
the SAAL links.
data
Before deleting an SAAL link, you must delete the NCP, CCP, or
ALCAP carried by the SAAL link.
In ATM transmission mode, the user plane data is about the AAL2
User plane
path. An AAL2 path is a channel carrying the user plane data between
data
the RNC and the NodeB.
In ATM transmission mode, the OM channel is used to carry the
OM channel
maintenance information between the RNC and the NodeB.
Networking In ATM transmission mode, the networking link consists of the
link Timeslot cross connection and treelink PVC.

physical NodeB, and choose IP Transport Layer from the shortcut menu.
 Click Basic Configuration, click IPPort, and configure NodeB physical link data
based on the onsite plan.
 Click Basic Configuration, and configure NodeB transport data.
Object Description
In IP transmission mode, you must configure at least one type of the physical links,
Physical link such as MLPPP group, PPP link, Ethernet trunk group, and device IP address of the
port.
Transmission The bandwidth of physical links is allocated to the transmission resource group to carry
resource group the data on the control plane, user plane, and OM channel.
In IP transmission mode, the CME provides IP routes for the control plane, user plane,
IP route
and OM channel of the NodeB in layer-3 networking mode.
In IP transmission mode, the control plane data consists of the data of SCTP links, and
Control plane the data of the NCP and CCP carried by the SCTP links.
data Before deleting an SCTP link, you must delete the NCP or CCP carried by the SCTP
link.
In IP transmission mode, the user plane data is about the IP path. An IP path is a
User plane data
channel carrying the user plane data between the RNC and the NodeB.
In IP transmission mode, the OM channel is used to carry the maintenance information
OM channel
between the RNC and the NodeB.
In IP transmission mode, other objects include the transmission resource group whose
Other objects destination IP network segment is bound, Ethernet OAM data, BFD session, IP clock
link, networking link, differentiated service priorities, and next hop VLAN mapping.

physical NodeB, and choose Radio Layer from the shortcut menu.
 Click UL/DL BB Resource Group in the lower part of the window. A window is
displayed for you to configure baseband resource groups. Based on the onsite plan,
configure the baseband resource group data.
 Based on the onsite plan, configure the site, sector, and cell data.

 Table Configuring the data
Object Description
Baseband resources are categorized as uplink and downlink baseband

Uplink and resources. You can specify an uplink baseband resource group ID to configure
downlink uplink baseband resources for a cell and specify a downlink baseband resource
baseband group ID to configure the downlink baseband resources for a cell.
resource Before deleting the baseband resources in a baseband resource group, you
group need to delete the cells that are using this baseband resource group.
The BTS3900A or BTS3900 supports the configuration of local sectors, remote

Site, sector, sectors, and distributed sectors. The DBS3900 supports the configuration of
and cell remote sectors and distributed sectors. Cells can be configured on local sectors,
remote sectors, or distributed sectors.
Reconfiguring the values of the Mac parameters of the local cells that support
the HSDPA service means to reconfigure the Mac-hs scheduling parameters of
Mac
the local cells. The Mac parameters consist of the Mac-hs scheduling
parameters
parameters, Mac-hs resource proportion restriction parameters, and Mac-e
parameters.
Other Other objects of the radio layer consist of the remote coverage resource groups,
objects TX antenna pairs, power sharing groups, and CMB FACH duplication function.



 Collect NodeB planning data.

 Collect the NodeB hardware device data. The devices include cabinets, subracks,
boards, and RF modules.
 Collect transport data and radio data of the NodeB.
 Collect the transport data of the NodeB based on the transmission networking.
 Collect radio data of the NodeB based on the installed hardware and the radio
network planning.
 Obtain the Iub template by using the following method:
 Obtain the BSC version Iub Data Import Template file from M2000 client
installation path\client\client\Data\BSC
version\Model\local\language\Template. You are not allowed to edit the file
in the folder. You must save the file to another local folder for editing.
 Export the Iub interface data (including physical NodeB data) from the live
network to use the data as an Iub data planning file.
 Custom NodeB Device Data and Radio Data by using the following method:
 If a Physical NodeB data similar to the planned data is available on the live
network
 If no data is available on the live network
 Select a default template that is similar to the planned data.
 Import this default template to create physical NodeBs. Then, manually
reconfigure the existing data on the GUI based on the planned data.
 Verify that the NodeB configuration data is intact, consistent, and valid.

 Cover Sheet
 The Cover sheet contains the controller version, release date, descriptions,
and precautions. You are advised to read the information in this sheet before
customizing parameters or editing this file.
 NodeBSummary Sheet
 A row in the NodeBSummary sheet corresponds to some data in a NodeB sheet.
 NodeB Sheets
 Each NodeB sheet records all data of one NodeB.
Area No. Content Description
1 Configuratio •The area above PHYSICAL NODEB displays Iub configuration objects
n objects on the RNC, while the area from PHYSICAL NODEB down displays Iub
configuration objects on the NodeB. Object PHYSICAL NODEB is
available only on the CME.
•You are not allowed to change the names of configuration objects in the
NodeB sheet.
2 Parameters This area lists the parameters to be configured for all objects. The NodeB
sheet contains the network planning parameters and parameters
negotiated with the peer end. Some optional parameters are not included.
Parameters marked with * and their branch parameters are mandatory.
You are not allowed to change the names of parameters in the NodeB
sheet.
The name of the NodeB sheet is the same as the value of NodeB ID in
this sheet.
3 Parameter This area provides the meaning, value range, and source of a parameter.
comments

 Description of a NodeBSummary sheet
Area Content Description

No.
1 Configuration In this area, you can customize the objects that parameters belong
objects to which to. This helps you check data.
the parameters
belong
2 Parameters •In this area, you can customize the names of parameters to be
configured (column headers) based on the planned data. Parameter
names can be the same as those in the NodeB sheet. Alternatively,
you can customize parameter names as required.
•If a parameter belongs to multiple configuration objects, this
parameter must be defined in different columns.
3 Positions of In this area, you can identify where a parameter value in the
parameter NodeBSummary sheet is located in the NodeB sheet. This
values location correlates a user-defined parameter in the
NodeBSummary sheet to the corresponding parameter in the
NodeB sheet.
4 Parameter This area provides the meaning, value range, and source of a
comments parameter.

 The principles for customizing parameters in Based on the User-Defined NodeB

Sheets mode are as follows:
 Based on the scenario and planned data, customize the configuration
objects of the Iub interface on the RNC and physical NodeB and the
number of configuration objects.
 Enable the system to create a NodeB sheet and set the values for all
parameters based on the planned data.
 Select a customized NodeB sheet and copy the NodeB sheet to
create NodeB sheets for other NodeBs in the same configuration
scenario.
 Manually reconfigure data in the NodeB sheets of other NodeBs
based on the planned data.
 The principles for customizing parameters in User-Defined NodeB Sheets and the
NodeBSummary mode are as follows:(For detailed information, refer to the manual)
 Create and edit the NodeB sheets.
 Obtain the data difference between multiple NodeBs based on the
planned data.
 Determine the configuration objects and parameters related to the
data difference and the positions of the parameter values in the
NodeB sheets, and then customize the NodeBSummary sheet.
 After the editing is complete, update data in the NodeB sheets based
on data in the NodeBSummary sheet.

 When ATM transport is applied to the Iub interface, the sequence of adding Iub
interface data should be consistent with the protocol structure, that is, from the lowest
layer to the highest layer and from the control plane to the user plane.
 The transport network layer of the Iub interface consists of the transport network layer
user plane (area A), the transport network layer control plane (area B), and the
transport network layer user plane (area C).
 Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the
three areas can be carried on common physical links.
 Links in areas A and B are carried on SAAL links. Based on the type of carried
information, the upper layer of area A is classified into the NCP and CCPs. Only
ALCAP links are carried in area B.
 In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer
is the ATM PVC. Under the control of ALCAP, AAL2 connections can be dynamically
set up or released for the transmission of upper-layer services. Therefore, each AAL2
path must have its corresponding controlling ALCAP.
 SAAL:Signaling ATM Adaptation Layer
 AAL2:ATM Adaptation Layer 2
 UNI:User Network Interface
 ALCAP:Access Link Control Application Protocol
 NBAP:NodeB Application Part
 NCP:NodeB Control Port
 CCP:Communication Control Port

 IMA(Inversed Multiplexing over ATM) means to inversely multiplex the ATM cell flow
over a high-speed link onto several low-speed links at the TX end for transmission,
and then converge the cell flows from several low-speed transmission links into a
high-speed cell flow at the RX end.
 IMA group is a logical concept, which allows multiple E1 links to be logically grouped.
These E1 links are named IMA links. To add an IMA link, ensure that the IMA group
containing this IMA link exists.
 The IMA link can be added only when the target IMA group is successfully
created.
 An E1/T1 link can be used by only one application at the same time. For
example, the link cannot be set to an IMA link and UNI link at the same time. If
an E1/T1 link is used as an IMA link, it cannot be used as a UNI link. If an
E1/T1 link is used as a UNI link, it cannot be used as an IMA link.
 The IMA links in an IMA group must be of the same type, that is, the links must
be E1 links or T1 links.
 If a loopback error (local loopback or physical loopback) occurs on an IMA link,
the IMA link is automatically deleted from its IMA group.


 Device IP addresses can only be configured on the interface board. Each interface
board can be configured with a maximum of 16 device IP addresses.
 The local IP address and the peer IP address must be on the same subnet.
 The parameters TX traffic record index and RX traffic record index must be
set to the same value.

 Click Generate Template. The customized NodeB sheet is generated with ATM
mode.
 (Optional) If you need to increase the number of the objects of the Iub interface on the
RNC or physical NodeB side, you can select a configuration object in the A column
and click Expand Row to add a row. The system displays a dialog box indicating
whether to overwrite the existed file, and click OK.
 NOTE:
 If you need to add multiple rows, click Expand Row multiple times.
 This function is not supported by the exported Iub data planning file.
 This function is supported by Iub data planning files of the following versions obtained
from M2000 client installation path\client\client\Data\BSC
version\Model\local\language\Template.

 Set values of the parameters for each object in the NodeB sheet based on the
planned data. When setting the parameters under the PHYSICAL NODEB object, be
aware that:
 Is Exist is set to YES and identifies that you need to configure the Iub
interface data about the physical NodeB.
 NodeB Name identifies the name of a physical NodeB to be configured. The
value of this parameter is the same as that of NodeB Name under the
NODEB object on the RNC side.
 Parent NE Name identifies the name for the parent node of the physical
NodeB to be configured.
 NodeB Configuration identifies the basic attributes of the physical NodeB
to be configured. You are recommended to leave this parameter blank.
 (Optional. Required when you need to add NodeB sheets for other NodeBs) Select a
customized NodeB sheet and click Copy Sheet above. A new NodeB sheet is
generated, data in which is the same as that in the selected NodeB sheet.
 Save the file and exit.

 According to the configuration sequence, select the configuration objects of the

transport layer under the IP Transport node, and then configure the data.
 Data of the physical layer and the data link layer
 Ethernet Port IP Address: Configure the IP addresses of FE/GE ports.
 Trunk IP: Configure the IP addresses of FE/GE trunk link groups. One trunk
link group can be configured with a maximum of six IP addresses.
 IP Logic Port: Configure an IP logical port.
 MLPPP Group:
 Each MP group can be bound to a maximum of eight MLPPP links.
 Timeslot 0 of an MLPPP link cannot be configured.
 On the POU board, all the MLPPP links in an MP group must be
configured with timeslots of the same number.
 PPP Link: The PPP links and MLPPP links on the same interface board must
be numbered uniquely.
 Device IP: Configure the device IP addresses of the interface board as the
local IP addresses of the IP path and SCTP link in the case of layer 3
networking. If a device IP address is used for the cell broadcast service (CBS),
it cannot be used for the SCTP link and IP path.

 There are two types of networking on the Iub interface, namely, layer 2 networking
and layer 3 networking. Compared with layer 3 networking, layer 2 networking is
simpler. That is because the port IP addresses of the BSC and NodeB are located on
the same network segment and no route is required.
 IP 1 and IP 2 are port IP addresses.

 IP 1 and IP 2 are device IP addresses on the IP interface board. IP 3 and IP 4 are port
IP addresses on the IP interface board. IP 5 and IP 6 are gateway IP addresses on
the BSC side. IP 7 is the gateway IP address on the NodeB side. IP 8 is the IP
address of the NodeB.
 On the Iub interface where layer 3 networking is applied, you should configure the
route.
 The Iub IP addresses at the BSC consist of IP addresses of Ethernet ports, local IP
addresses of PPP links, local IP addresses of MLPPP groups, and device IP
addresses.


 Click Generate Template. The customized NodeB sheet is generated with IP mode.
 (Optional) If you need to increase the number of the objects of the Iub interface on the
RNC or physical NodeB side, you can select a configuration object in the A column
and click Expand Row to add a row. The system displays a dialog box indicating
whether to overwrite the existed file, and click OK.
 NOTE:
 If you need to add multiple rows, click Expand Row multiple times.
 This function is not supported by the exported Iub data planning file.
 This function is supported by Iub data planning files of the following versions obtained
from M2000 client installation path\client\client\Data\BSC
version\Model\local\language\Template.

 Set values of the parameters for each object in the NodeB sheet based on the
planned data. When setting the parameters under the PHYSICAL NODEB object, be
aware that:
 Is Exist is set to YES and identifies that you need to configure the Iub
interface data about the physical NodeB.
 NodeB Name identifies the name of a physical NodeB to be configured. The
value of this parameter is the same as that of NodeB Name under the
NODEB object on the RNC side.
 Parent NE Name identifies the name for the parent node of the physical
NodeB to be configured.
 NodeB Configuration identifies the basic attributes of the physical NodeB
to be configured. You are recommended to leave this parameter blank.
 (Optional. Required when you need to add NodeB sheets for other NodeBs) Select a
customized NodeB sheet and click Copy Sheet above. A new NodeB sheet is
generated, data in which is the same as that in the selected NodeB sheet.

 Open the obtained Iub data planning file.

 Obtain the data shared by multiple NodeBs based on the planned data to customize the NodeB sheet
and edit it.
 Obtain the differentiated data between multiple NodeB based on the planned data to customize the
NodeBSummary sheet.
 Click the NodeBSummary tab.
 Add, delete, or modify the columns based on the planned data, transmission scenarios,
and parameters to be configured.
• The sequence of the first five columns, NO., Is Import CME, Reference
NodeB, NodeB name, and NodeB ID, cannot be changed.
• The values in the NO., NodeB name, and NodeB ID columns cannot be
empty.
• Is Import CME: Defines whether to import the data of the NodeB
corresponding to this row to the CME.
• Reference NodeB: The value of this column is the name of the reference
NodeB.
• If the value of this column is set, other data of the NodeB
corresponding to this row is the same as the data in the NodeB
sheet corresponding to the reference NodeB. Other data means the
data not in the NodeBSummary sheet.
• If the value of this column corresponding to a row is not set, other
data of the NodeB corresponding to this row is the same as the
data in the first NodeB sheet. Other data refers to data that is not
customized in the NodeBSummary sheet.
 Define the column headers based on the parameters to be configured. Unless
otherwise specified, a column header indicates the meaning of the column. For
example, you can define NodeB name by using the parameter name recorded in the
NodeB sheet, or change the column header to a header with special meanings for
easy understanding.
 Edit the position of a parameter value by defining where a parameter value in a cell of
the sheet is located in the NodeB sheet.

 (Optional. Required when you need to extract data from existing NodeB sheets) Click
Update Summary from NodeB Sheets to extract the data from each NodeB sheet
for the columns defined in the NodeBSummary sheet.
 Set or modify values for the parameters in the NodeBSummary sheet based on the
planned data.
 Click Generate NodeB Sheets from Summary. The values in the NodeBSummary
sheet are updated to corresponding positions in each NodeB sheet.
 (Optional) Add comment columns.


 Opening the current data area

 Choose Area Management > Current Area > Open Current Area (CME
Client Mode) or CM Express > Current Area > Open Current Area (M2000
Client Mode). The NEs in the current data area are displayed in the navigation
tree.
 In the navigation tree in the left pane, right-click an NE or the sub-node of an
NE, and then choose the data type to be viewed from the shortcut menu. The
corresponding data of the NE is displayed in the right pane.
 Synchronizing the data in the current data area with the data on the live network
 Open the current data area.
 Choose Area Management > Current Area > Synchronize NE (CME Client
Mode) or CM Express > Current Area > Synchronize NE (M2000 Client
Mode). The dialog box for synchronizing NE configuration data is displayed.
This dialog box displays a list of NEs that are connected to the M2000.
 Select one or more NEs.
 Select a data synchronization mode. This step is applicable only to MBSCs.
 Click OK. A dialog box is displayed for you to confirm the synchronization.
 After you confirm the synchronization, the CME starts to upload NE data. The
progress bar and the synchronization information about the NEs are displayed
in the lower part of the dialog box.
 After the synchronization, the dialog box is automatically closed. The CME
main window is displayed.

 Creating a planned data area

 Choose Area Management > Planned Area > Create Planned Area (CME
Client Mode) or CM Express > Planned Area > Create Planned Area
(M2000 Client Mode). A dialog box is displayed for you to create a planned
data area.
 Type a name for the planned data area.
 Select a user group.
 Select an access permission on the planned data area from the Access
Privilege drop-down list.
 Private: Only the creator and administrators can perform operations on
the planned data area.
 Public: The creator, users in the same group with the creator, and
administrators can perform operations on the planned data area.
 (Optional) Select NEs to be added to the planned data area.
 (Optional) Type description of the planned data area.
 Click OK. The CME starts creating the planned data area and then
automatically opens it.

 In the Main View navigation tree in the left pane of the planned data area, select an
,
RNC or MBSC, and choose CM Express > UMTS Application > Import Data >
Import Iub Interface Data (Including Physical NodeB) (M2000 Client Mode), or
UMTS Application > Import Data > Import Iub Interface Data (Including Physical
NodeB) (CME Client Mode) from the menu bar. The window for selecting an Iub data
planning template is displayed.
 Click , select the Iub data planning template to be imported, and select a
required import mode.
 (Optional) If you need to import a shared object data planning template, select Import
Shared Objects, and select a shared object data planning template to be imported.

 Click Next. The window for selecting a physical NodeB template is displayed. Right-
click one or multiple records, and then choose Select NodeB Template from the
shortcut menu. The template selection dialog box is displayed. Select the type,
version, and template of the NodeB respectively from the Series, Version, and
Template drop-down lists. Then, click OK.
 Click Next. The CME starts the import.
 When the CME displays a message indicating that the import is successful, click
Finish.
 NOTE:
 After the physical NodeBs are created successfully, the NodeB icon in the Main View
navigation tree changes from to .
 You can create a batch of physical NodeBs in this mode. A maximum of 50 physical
NodeBs can be created at a time.

physical NodeB and choose Basic Information from the shortcut menu. The basic
information about the physical NodeB is displayed in the right pane.
 The basic information about physical NodeBs is displayed in sheets such as
Equipment Management, Transport Management, Radio Management, Time
Zone, and Clock Source.
 Based on the planned data, configure basic information about physical NodeBs.

 After creating a physical NodeB by importing an Iub data planning file, you need to
reconfigure the device and radio data about the physical NodeB on the CME client
based on the planned data.
 Reconfigure the device data about the physical NodeB.
 Reconfigure the radio data about the physical NodeB.

 Sector classification:
 Remote sector
 RF modules of remote sectors are connected to the baseband unit through
optical fibers.
 RF modules of remote sectors can be located far from the baseband unit.
 Remote sectors are mainly applied at distributed base stations.
 Local sector
 Local sectors are relative to remote sectors.
 Value ranges of cabinet number, subrack number, and slot number for local
sectors are different from those for remote sectors.
 RF modules of local sectors must be located near the baseband unit.
 Distributed sector
 A distributed sector is covered by multiple RF modules, with each RF module
covering an area.
 The RF unit of the distributed sector supports single transmitter, single
receiver, and double receiver.
 A cell can be covered by multiple RF modules, with each RF module covering
an area.
 Distributed sectors are mainly applied for indoor coverage.


 On the menu bar of the current data area or a planned data area, choose Advanced
> Check Consistency (CME Client Mode) or CM Express > Check Consistency
(M2000 Client Mode).
 Start the check task.
 View check results.

 In the Main View navigation tree in the left pane of the planned data area, select a
UMTS or GU NE.
 Choose CM Express > UMTS Application > Physical NodeB Management >
Export Configuration File on the menu bar. The Export NodeB Configuration File
window is displayed.
 Click Add, and select one or multiple NodeBs.
 Click Next and specify the save path for the NodeB XML configuration scripts.
 Click Next. The CME starts the export.
 Click Finish.



OWB301700 BTS3900 WCDMA V200R014 Initial Data Configuration Based On CME ISSUE 1.00

Uploaded by

Document Information

Original Description:

Original Title

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

OWB301700 BTS3900 WCDMA V200R014 Initial Data Configuration Based On CME ISSUE 1.00

Uploaded by

Copyright:

Available Formats

BTS3900 WCDMA V200R014 Initial Data Configuration P-0

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Third-party NMS:A third-party network management system (NMS), which manages

Confidential Information of Huawei. No Spreading Without Permission

 CME client software

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 System output window

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Collect NodeB planning data.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Opening the current data area

Confidential Information of Huawei. No Spreading Without Permission

 Creating a planned data area

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Configure RFUs or RRUs.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Table Configuring the data

Baseband resources are categorized as uplink and downlink baseband

The BTS3900A or BTS3900 supports the configuration of local sectors, remote

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Collect NodeB planning data.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Description of a NodeBSummary sheet

Area Content Description

Confidential Information of Huawei. No Spreading Without Permission

 The principles for customizing parameters in Based on the User-Defined NodeB

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 According to the configuration sequence, select the configuration objects of the

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission