Dynamic Data
Dynamic Data
After data on the live network is loaded to the current data area, you can use the CME
to configure and manage the data.
Open the current data area.
On the menu bar, choose CME > CME.
On the menu bar, choose Area Management > Open Current Area. The
existing NEs in the current data area are displayed in the navigation tree in the
left pane.
In the navigation tree, select an NE or a subnode under an NE.
Manually synchronize live network data to the current data area.
On the menu bar, choose Area Management > Current Area > Synchronize
NEs.
Select one or more NEs.
Select a data synchronization mode.
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.
When the synchronization is complete, the dialog box is automatically closed.
The CME main window is displayed again.
Changing signaling points will interrupt BSC services. Therefore, perform this
operation when the traffic is light, for example, during early morning hours.
Select a base station controller you want to configure from the left pane in the planned data
area. The navigation tree of NE configuration objects is displayed in the lower part of the left
pane.
Double-click the object you want to configure. The parameters of this configuration object are
displayed in the right area. Set the planned values for these parameters.
Click to save the configured data.
Note
The OSP code bits cannot be modified.
If the Originating Signaling Point (OSP) is used by two or more than two M3UA local
entities(You can check this by running the LST M3LE command), the BSC6910 does
not support changing this Originating Signaling Point Code (OPC) in effective mode but
support that in ineffective mode.
Services are interrupted for a short time if the Originating Signaling Point Code (OPC)
is modified. As a result, the KPI is affected.
Equipment Serial Number(ESN) is affected if the OPC whose index number is zero is
modified. As a result, a new license is required.
If the OSP code used by UMTS CN node is changed, run the MOD UCNNODE
command to change the corresponding parameter to keep them consistent.
If the OSP code used by the neighboring RNC is changed, run the MOD UNRNC
command to change the corresponding parameter to keep them consistent.
Note
If you want to modify Adjacent flag whose value is YES (DIRECT_CONNECT), you
need to use LST MTP3LKS or LST M3LKS according to the bearer type to check
whether the corresponding link set exists. If the link set exists, you cannot modify this
parameter.
When the DSP is an adjacent node and you want to modify STP function switch from
ON to OFF, you need to use LST MTP3RT or LST M3RT according to the bearer type
to check whether the route from this DSP to another DSP exists. If this route exists,
you cannot modify this parameter.
If the DSP configuration is used by the destination entity(You can check this by running
the LST M3DE command), you can modify only destination signaling point code
(DPC), Signaling route mask, DSP name, DSP bear type and Net PRI.
The modified DPC cannot be the same as the configured original signaling point code
(OPC) with the same Network Identifier. You can query the configured OPC by running
the LST OPC command.
If the DSP bear type is M3UA or MTP3_M3UA, you cannot modify Adjacent flag.
If the DSP code used by UMTS CN node is changed, run the MOD UCNNODE
command to change the corresponding parameter to keep them consistent.
If the DSP code used by the neighboring RNC is changed, run the MOD UNRNC
command to change the corresponding parameter to keep them consistent.
Add a new N7DPC as show in the CME planned area, in this step:
Set DSP index to an appropriate value.
Set DSP code[Whole Number] to the signaling point code.
Set DSP type to STP(STP).
Set Adjacent flag to YES(DIRECT_CONNECT).
Delete MTP3 or M3UA datas as show in the CME planned area, in this step, including:
MTP3/M3UA Signalling Link Set
MTP3/M3UA Signalling Link
MTP3/M3UA Signalling Route
Add MTP3 or M3UA datas as show in the CME planned area, in this step, including:
M3UA Destination Entity
MTP3/M3UA Signalling Link Set
MTP3/M3UA Signalling Link
MTP3/M3UA Signalling Route
In the navigation tree in the left pane of the planned data area, right-click a BSC and
choose Device Panel from the shortcut menu. The device panel of the BSC is
displayed in the right pane.
The BSC6910 supports only the PARCb subrack and SCUb/SCUc board.
Before adding a subrack, ensure that clock cables have been connected properly and
interconnecting cables have been correctly installed. Otherwise, services allocated to
the added subrack will become abnormal if the subrack cannot obtain clock signals or
subrack loading may fail if interconnecting cables are incorrectly installed.
According to the SCU port connection between MPS and EPS, open the port switch of
SCU board. Different boards and different cables connection, should enable different
ports.
For the SCUb/SCUc board, ports 10G-T8 to T11 are Ethernet ports with the rate 10
Gbit/s. These ports are used for inter-subrack interconnection and support
interconnection of SFP+ high-speed cables and multimode optical cables.
For SCUb Ports 10/100/1000BASE-T0 to T7 can be used as Ethernet ports with the
rates of 10 Mbit/s, 100 Mbit/s, or 1000 Mbit/s, these ports are reserved and cannot be
used to connect the base station controller to other devices.
For SCUc 40GE ports 0 to 7, are used for inter-subrack connection between SCUc
boards. On an SCUc board, Ports 0 to 3 and ports 4 to 7 are used as two port groups
for connecting different subracks, if a group is used, all ports in the group must be all
used.
Add Service Processing Board. Based on the planned data, right-click the required
slot and choose GPU > Add EGPUa/EGPUb/EGPUc/EXPUc/EXPUb/EXPUa from
the shortcut menu. The attribute dialog box is displayed.
The EGPUa boards of the RMP logical type are installed in slots 8 and 9 in the
MPS. No need add for subrack expansion.
EGPUa/EXPUa boards can be installed in slots other than those for the SCUb,
GCUa/GCUb/GCGa/GCGb, and EOMUa/EOMUb/ESAUa/ESAUb boards.
EGPUa/EXPUa boards are preferentially installed in slots 0 to 13.
Add Interface Board. Based on the planned data, right-click the required slot and
choose INT > Add Interface Board Type from the shortcut menu. A dialog box is
displayed for you to configure attributes.
Interface boards must be installed in the rear slots of a subrack to facilitate
cable layout.
The FG2c, GOUc/GOUe, FG2d, GOUd, POUc boards support large
throughput. The boards are preferentially installed in slots 16 to 19 and 22 to
25. If these slots are occupied, the boards can be installed in slots 14 to 15
and 26 to 27.The IuPS interface boards that carry IP transmission are
preferentially installed in slots 16 to 19 and 22 to 25.
The EXOUa board supports large throughput and must be installed in slots 16
to 19 and 22 to 25.
MML Reference:
Run the SET CFGDATAEFFECTIVE command to set the configuration mode
of the new subrack to effective mode.
Run the SET LODCTRL command with Board Start Load Control set to
LFB(Load from OMU and write flash).
Run the FMT DATA command to generate configuration data files for all
subracks.
If the newly added subrack is not powered on, turn on the power switch of the
subrack. If the newly added subrack is powered on, turn off the power switch
of the subrack first, then turn on the power switch again.
Verify Service
On the LMT, choose Device Maintenance to check the board CPU status.
Ten minutes later, all the boards in the subrack are loaded, and the subrack
begins to work properly. Observe the status of each board in the Device
Maintenance window.
On the Browse Alarm tab page on the LMT, check whether alarms related to
board faults are reported.
Run the CMP BRDVER command to check whether the software version of
the board in the newly added subrack is consistent with the host software.
Run the SET LODCTRL command with Board Start Load Control set to
CL(Consult Load).
Prerequisites
Risk evaluation is performed:
GSM:Risk evaluation is performed to evaluate the impact of BTS relocation on
services when removing a board, the impact of BTS relocation on the target
board, and the impact on transmission links.
UMTS:Risk evaluation is performed to evaluate the impact of NodeB relocation
on services when removing a board, the impact of NodeB relocation on the
target board, and the impact on transmission links.
Network planning is performed:
GSM:Network planning is performed to plan the number of BTSs carried on
each subrack and each EGPUa/EGPUb/EXPUa/EXPUb board.
UMTS:Network planning is performed to plan the number of NodeBs carried
on each subrack and each EGPUa/EGPUb board.
Required tools are ready
Including an ESD wrist strap, a Phillips screwdriver, an ESD box or bag,
dustfree cloth, and a fiber cleaner.
Back up the BSC6910 configuration data, performance data, and alarm data through
MML commands BKP DB or using the omu_backup_restore_tool.
Impact of removing the EGPUa/EGPUb board (UCUP) and how to remove the board:
Configuration Objects on the
Removing Impact How to Remove
Board to Be Removed
NodeB Services on the NodeB are interrupted. The NodeB is automatically
reparented to another board.
MTP3 link, SAAL link, M3UA Transmission links of the current control Transmission links are
link, and SCTP link subsystem configured on the board to be automatically configured on
removed are interrupted. another board.
Impact of removing the EGPUa/EGPUb/EXPUa/EXPUb board (GCUP) and how to
Configuration
remove the Objects on the
board:
Removing Impact How to Remove
Board to Be Removed
BTS, cell, operation and Services on the NodeB are interrupted. The NodeB is automatically
maintenance link (OML), and reparented to another board.
radio signaling link (RSL)
SCTP link, M3UA link set, M3UA • The IP transmission link over the A Transmission links are
link, and M3UA route interface is unavailable or the automatically configured on
transmission efficiency decreases. another board.
• Transmission links of the current control
subsystem configured on the board to
be removed are interrupted.
NSE(Network Service Entity) PS services are unavailable. Control subsystem are
automatically configured on
another board.
In the navigation tree in the left pane of the planned data area, right-click a BSC and
choose Device Panel from the shortcut menu. The device panel of the BSC is
displayed in the right pane.
Right-click a board you want to delete and choose Delete from the shortcut menu.
The confirmation dialog box is displayed.
Click OK to delete the board.
Delete Subrack after remove the INT and GPU boards.
MML Reference:
Run the SET CFGDATAINEFFECTIVE command to set the configuration
mode of all subracks to ineffective mode.
Remove the configuration objects of the board.
Run the RMV BRD command to remove the board.
Run the RMV SUBRACK command to remove the subrack.
Run the SET SCUPORT to disable the port on the SCU in the subrack whose
connection is removed.
Prerequisites
Network planning is complete. Network planning is performed to plan the type,
number and backup mode of the A interface boards, the data throughput in the
transmission resource pool of the A interface, and the number of transmission
resource pools on the A interface.
Hardware requirement: The FG2c, FG2e ,FG2d, GOUc, GOUd, GOUe, or
EXOUa has been configured.
The license controlling A interface transmission pool has been activated.
NOTE: Before removing the A interface board, ensure that the line clock carried on
the A interface board in the TCS is removed.
Optional: Only if BM/TC separated mode is used for TDM transmission, then need
delete the TCS subrack after deleting all the TCS data.
In the Transmission navigation tree of the planned data area, click A, The
Properties window is displayed for you to configure.
Reconfigure the parameters of the object in the right pane based on the planned data.
Remove the clock source data and reconfigure the clock mode. In A over IP network,
BSC clock can work in free-run mode-That is use internal clock.
After removing the clock data, A interface board can be removed from slot for new
interface board.
MML Reference:
Run the RMV BRD command to remove the TDM interface boards and the
DPUf board.
Optional: Only if BM/TC separated mode is used for TDM transmission, run the
RMV SUBRACK command to remove TCS data.
NOTE: Before removing the A interface board, ensure that the line clock
carried on the A interface board in the TCS is removed. For details about how
to remove the line clock and the clock source, see the descriptions of the SET
CLK and RMV CLKSRC commands.
In the navigation tree in the left pane of the planned data area, right-click a BSC and
choose Device Panel from the shortcut menu. The device panel of the BSC is
displayed in the right pane.
Add an IP interface board to the MPS or EPS.
MML Reference:
Run the ADD BRD command to add an IP interface board to the MPS or EPS.
In the Transmission navigation tree of the planned data area, click A, and choose
DSP from the Properties menu. The window is displayed for you to configure the
DSP
Reconfigure the parameters of the object in the right pane based on the planned data.
MML Reference: Change the transmission mode of destination point code (DPC) on
the A interface from TDM to IP.
Run the ADD N7DPC command to add a temporary DSP for the A interface
that is used for transmitting M3UA messages.
Run the RMV N7DPC command to remove the DSP of the A interface that is
originally used for transmitting MTP3 messages.
Run the ADD N7DPC command to add a DSP for the A interface that is used
for transmitting M3UA messages.
Run the RMV N7DPC command to remove the temporary DSP.
In the navigation tree in the left pane of the planned data area, right-click a BSC and
choose Device Panel from the shortcut menu. The device panel of the BSC is
displayed in the right pane.
Configure the parameters of the object in the right pane based on the planned data.
Related MO to be modified is ETHPORT.
MML Reference: Set Ethernet port attributes.
Run the LST ETHPORT command to query the default data of the Ethernet
port.
Optional: If the planned data is inconsistent with the default data, Run the
SET ETHPORT command to set Ethernet port attributes.
In the Transmission navigation tree of the planned data area, click A, and choose IP
Transport from the Properties menu. The window is displayed for you to configure
the IP Transport.
Configure the parameters of the object in the right pane based on the planned data.
This section describes how to configure the mapping between the service types and
transmission resources for the adjacent node. You can configure the TRM mapping
table for users with different priorities. It’s optional, only if the default mapping is not
used:
Related MO of optional configuration: TRMMAP,TRMFACTOR and ADJMAP.
TRMMAP used to set the service priority.
TRMFACTOR used to set the service admission control.
ADJMAP used to bind the TRMMAP and TRMFACTOR to the ADJNODE.
MML Reference:
Run the ADD TRMMAP command to add a TRM mapping table. To add more
TRM mapping tables, run this command for each table.
Run the ADD ADJMAP command to configure the TRM mapping table for
users with different priorities.
The network reliability can be verified by checking generated alarms and making
dialing tests after a switchover between the active/standby boards.
Prerequisites
All the subracks of the BSC6910 are running normally.
The alarms generated during the operation have been cleared.
Procedure
Run the SET CFGDATAEFFECTIVE command with Automatic BSC Reset set
to NO to set the configuration mode of all subracks to effective mode.
Run the FMT DATA command to generate a configuration data file.
Run the RST BSC command to reset the BSC and reload the configuration
data.
Run the ACT LICENSE command to activate the license.
Use an MS in a cell under the BTS to perform basic services and check
whether services are going on properly
This section describes how to modify the maximum transmit power of a serving cell or power of different
channels in a cell when the network is optimized.
Max Transmit Power of Cell, this parameter represents the sum of the maximum transmit power of all DL
channels in a cell, is configured during network planning. If this parameter is set to a small value,
downlink capacity and coverage are restricted. However, the maximum value should not exceed the
processing capability of the NodeB.
If the cell is in service, changing the maximum transmit power of the cell has the following impacts:
If the maximum transmit power of the cell is changed to a value within the range specified by the
maximum and minimum transmit powers for cells under a NodeB, the change will take effect
and trigger the CELL RECONFIGURATION procedure over the Iub interface.
If the maximum transmit power of the cell is changed to a value greater than the maximum
transmit power or less than the minimum transmit power for cells under a NodeB, the change
will not take effect nor trigger the CELL RECONFIGURATION procedure over the Iub interface.
When this occurs, the RNC will automatically report ALM-22215 UMTS Cell Max DL Power
Mismatch.
Reconfigure Max Transmit Power of a single cell procedure:
Select a NE you want to configure from the left pane in the planned data area. The navigation
tree of NE configuration objects is displayed in the lower part of the left pane.
Select the objects you want to configure 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 a
configuration object on the tab page, for example the ‘Cell Basic Information’. The
CME displays the searched configuration object in the lower part.
Double-click the object you want to configure. The parameters of this configuration object are
displayed. Set the planned values for these parameters.
Click to save the configured data.
You can modify cell data in batches by exporting data from the live network as a file,
modifying the cell data in the file, and importing the file into the CME.
On the menu bar of the planned data area, choose CME > UMTS Application
> Export Cell Parameter Data. Then, export the parameters you want to
reconfigure as a file.
Select a cell and the version of the RNC to which the cell belongs.
To select all cells under an NE, select NE from the Selected by drop-
down list. Then, select the NE in the NE list area.
To select some cells under an NE, select Cell from the Selected by
drop-down list, and click Add. Three modes for selecting cells are
displayed. You can select one of them based on site requirements.
Click Next. A dialog box is displayed for you to select parameters.
On the menu bar of the planned data area, choose CME > UMTS Application >
Import Cell Parameter Data. A dialog box is displayed for you to select files.
Specify the type of the file to be imported and click Add to select the file.
Click Next.
This section describes how to modify the area information of a cell when some areas
are replanned or a NodeB is cut over. These areas are location areas, service areas,
and routing areas.
Before modifying cell area information, need add new area code under RNC first.
LAC= Location Area Code, Identifying an LA within a Public Land Mobile Network
(PLMN). Mobile Country Code (MCC), Mobile Network Code (MNC) and LAC
compose Location Area Identity (LAI). This parameter is defined by the operator.
RAC= Routing Area Code, Identifying a routing area in a location area for a PLMN.
RAC and LAI compose Routing Area Identity (RAI). If the RNC supports the PS
domain, must configure RAC. This parameter is defined by the operator.
SAC= Service Area Code, MCC, MNC, LAC, and SAC together compose the Service
Area ID (SAI). SAI = MCC || MNC || LAC || SAC. The SAI is used to define an area
composed of cells in the same location area. This area is called service area, which
indicates the location of a UE to the CN. This parameter is defined by the operator.
For Location Area Code, The LAC is a 2-byte hexadecimal code. It ranges from
0000 to FFFE. The codes 0000 and FFFE are reserved.
LAC, SAC, and CfgRacInd must be specified at the same time.
You can modify cell data in batches by exporting data from the live network as a file,
modifying the cell data in the file, and importing the file into the CME.
On the menu bar of the planned data area, choose CME > UMTS Application
> Export Cell Parameter Data. Then, export the parameters you want to
reconfigure as a file.
Select a cell and the version of the RNC to which the cell belongs.
To select all cells under an NE, select NE from the Selected by drop-
down list. Then, select the NE in the NE list area.
To select some cells under an NE, select Cell from the Selected by
drop-down list, and click Add. Three modes for selecting cells are
displayed. You can select one of them based on site requirements.
Click Next. A dialog box is displayed for you to select parameters.
On the menu bar of the planned data area, choose CME > UMTS Application >
Import Cell Parameter Data. A dialog box is displayed for you to select files.
Select the version of the RNC to which the cell belongs.
Specify the type of the file to be imported and click Add to select the file.
Click Next.
When you import cell parameter data, the processing mechanism is as follows:
Whether Whether
Data Exists Data Exists on Results After the File Is Imported into the CME
in the File the CME
The CME overwrites the existing data using the cell
Yes Yes
data in the file.
The CME adds the cell data in the file.
NOTE:
1.If data about the URA, LAC, SAC, RAC, and SPG
referenced by the cell does not exist on the CME, the
Yes No
CME automatically adds the data.
2.You need to manually delete the URA, LAC, SAC,
RAC, and SPG that are no longer referenced by any
cell from the general configuration window.
No Yes The CME does not change any data.
This section describes how to change cell frequencies (including uplink and downlink
frequencies) when the cell frequencies are replanned for capacity expansion.
On the menu bar of the planned data area, choose CME > UMTS Application >
Modify Cell Frequencies in Batches, and reconfigure cell frequencies and
scrambling codes.
After the cell frequency is changed, the neighbouring relationships in the cell are
deleted. Replan and add the neighboring cells after changing cell frequency.
This section describes how to reconfigure the TRX power in a cell when the cell
coverage needs to be adjusted according to network optimization.
Reconfiguring the TRX power in a cell may affect ongoing calls in the cell. Therefore,
perform this operation with caution.
Reference MML commands :
Run the LST GTRXDEV command to record the TRX power before the
reconfiguration.
Run the SET GTRXDEV command to reconfigure the TRX power in a cell.
You can modify TRX information in batches by exporting data from the live network as
a file, modifying the TRX information in the file, and importing the file into the CME.
On the menu bar of the planned data area, choose CME > GSM Application >
Export TRX Parameter Data. Then, export the parameters you want to
reconfigure as a file.
You can modify frequency information in batches by exporting data from the live
network as a file, modifying the frequency information in the file, and importing the file
into the CME.
On the menu bar of the planned data area, choose GSM Application >
Export Cell Frequency Data. Then, export the parameters you want to
reconfigure as a file.
Check for any conflicts between configuration data and data on the live network.
Before activating configuration data, you can compare configuration data in the
planned data area with the live network data in the current data area to locate data
conflicts. Then, you can reconfigure the data in the planned data area based on the
check result to ensure successful data activation.
On the menu bar of the planned data area, choose Area Management >
Check Conflicts to start the conflict check.
On the menu bar of the planned data area, choose Area Management > Planned
Area > Export Incremental Scripts. 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.
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, and upload the scripts
saved on the local PC to the U2020 server in the future.
Launch script executor only: The CME automatically uploads the exported
scripts to the U2020 server, and starts the script executor, you can check or
edit scripts in the script executor window before activating scripts.
Before performing this operation, ensure that you have the network
device permission Modify Physical NE Data though CME.
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.
In the Script Executor window, click the More tab, click the plan area the user
created.
In the project list in the right pane, right-click a project and choose View Project.
Double-click a project in the project list in the right pane. A project tab page is
displayed, showing information about all the tasks in the current project.
Right-click a task and choose Edit Script from the shortcut menu. The system
switches to the script editing mode. When the script is in editing mode, the CME
automatically suspends the corresponding task.
Right-click the script and choose Update Script from the shortcut menu. The client
uploads the modified script to the server.
In the project list in the right pane, right-click a project you want to preactivate.
Fallback
On the menu bar of the CME main window, choose Advanced > System >
Script Executor (CME client mode) . The script executor window is displayed.
In the Script Executor window, click the More tab.
Right-click the project whose data you want to roll back and choose Activate
Fallback Project.