Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
V100R004C10
Issue 03
Date 2017-04-26
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
NE Version
Product Type Product Name Product Version
eSCN230 V100R004C10
eNB530DBS3900eNodeB V100R004C10
eOMC910 V100R004C10
EV750 V200R002C00
EP650 V200R002C00
EG860 V200R003C00
Intended Audience
This document is intended for:
System engineers
Organization
1 Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
2 Reconfiguration Overview
This section describes the definition of the reconfiguration guide and corresponding
configuration tool.
3 Prerequisites
This section describes the prerequisites before configuration adjustment. You must have
logged in to the configuration page on the eOMC910 operation and maintenance client.
4 Modifying the PLMN
This section describes the application scenario, change impact and change implementation of
modifying the PLMN. After the PLMN is changed, you need to synchronization
reconfiguration the eCN, the eNodeB and the UE.
5 Modifying the Name of an DBS3900
This section describes the application scenario, change impact and change implementation of
modifying the name of an DBS3900.
6 Modifying a Clock Source
This section describes the application scenario, change impact and change implementation of
modifying a clock source.
7 Modifying Time Information
This section describes the application scenario, change impact and change implementation of
modifying time source information.
8 Adjusting Cells
This chapter describes how to adjust cells and cell parameters.
9 Adjusting Neighboring Cells
This chapter describes how to adjust neighboring cells. Neighboring cells include intra-
frequency cells and inter-frequency cells.
10 Modifying VSWR Alarm Threshold of an eRRU
This section describes the application scenario, change impact and change implementation of
modifying VSWR alarm threshold of an eRRU.
11 Adjusting the Transmission Network
This section describes how to adjust the transmission network, including changejing the IP
address, SCTPLNK information, and IPPATH information.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl
+Alt+A means the three keys should be pressed
concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
8 Adjusting Cells............................................................................................................................ 16
8.1 Adding a Cell................................................................................................................................................................18
8.1.1 Application Scenario................................................................................................................................................. 18
8.1.2 Change Impact........................................................................................................................................................... 18
8.1.3 Change Implementation.............................................................................................................................................18
8.2 Removing a Cell........................................................................................................................................................... 20
8.2.1 Application Scenario................................................................................................................................................. 20
8.2.2 Change Impact........................................................................................................................................................... 21
8.2.3 Change Implementation.............................................................................................................................................21
8.3 Modifying a Cell ID..................................................................................................................................................... 21
1 Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
03 (2017-04-26)
This is the second commercial release of the V100R004C10 version.
Compared with issue 02 (2017-02-20) of V100R004C10, this issue include the following
changed issue.
Section Description
02 (2017-02-20)
This is the second commercial release of the V100R004C10 version.
Compared with issue 01 (2016-04-15) of V100R004C10, this issue include the following
changed issue.
Section Description
01(2016-04-15)
This is the first commercial release of the V100R004C10 version.
2 Reconfiguration Overview
This section describes the definition of the reconfiguration guide and corresponding
configuration tool.
Definition
Reconfiguration is to add, modify, or delete data after a DBS3900 system is running.
Tool
eOMC910 can be used to reconfigure a DBS3900.
NOTE
l This document describes how to use eOMC910 to reconfigure a DBS3900 system. For details about
how to use eOMC910, refer to eOMC910 Operation & Maintenance User Guide.
l In this document, eOMC910 operation maintenance terminal is called eOMC910 simplify.
3 Prerequisites
This section describes the prerequisites before configuration adjustment. You must have
logged in to the configuration page on the eOMC910 operation and maintenance client.
Prerequisites
l The eOMC910 is communicating properly with the DBS3900.
l You have the configuration right.
Procedure
Step 1 Run the operation and maintenance client. Enter User Name, Password, and Server. Click
OK.
Step 2 Choose Maintenance > NE Config In Batch from the main menu. The NE Config In Batch
page is displayed.
Step 3 Select the NE in the navigation tree on the left pane and further select desired NEs. Figure
3-1 shows the NE Config In Batch page.
----End
Follow-up Procedure
You can adjust configurations using the following methods:
l Input the MML command in batches in MML command input area.
l Input an MML command each time in Manual MML command input area.
This section describes the application scenario, change impact and change implementation of
modifying the PLMN. After the PLMN is changed, you need to synchronization
reconfiguration the eCN, the eNodeB and the UE.
Context
Impacts on NEs after the PLMN is changed:
l After the PLMN is changed in the eCN, UEs without PLMN change cannot access the
eCN.
l The DBS3900 without PLMN change must restart to make the change take effect.
During the restart, the DBS3900 cannot provide services normally.
l The UE must restart to make the PLMN change take effect. During the restart, the UE
cannot provide services normally.
Prerequisites
Collect the following information:
Context
In the following example, the MCC of the PLMN remains 460, the MNC is changed from 01
to 20. Run the following MML commands:
Procedure
l Change configurations on the eCN side (Run MML commands on the MML Command
Line-eCNS210 tab page to change configurations on eCNS210).
NOTE
If the PLMN is modified when an eCNS210 is used, the license of the eCNS210 may become
invalid. Apply for a new license based on the ESN after the PLMN is modified.
The license validity of the eSCN230 is not affected if the PLMN is modified when an eSCN230 is
used.
This section describes the application scenario, change impact and change implementation of
modifying the name of an DBS3900.
Prerequisites
The new name of the eNB530DBS3900eNodeB has been planned.
Context
A base station name can contain only the following characters: uppercase letters (A-Z),
lowercase letters (a-z), digits (0-9), space, special characters such as ' ( ) + - ., and characters
that conform to the ASCII standard.
Procedure
Step 1 Run the MOD ENODEB command, and enter the planned base station name in eNodeB
name.
After you run the MOD ENODEB command, the system informs you to manually reset the
base station. If you change only eNodeB name, you do not need to reset the base station.
----End
This section describes the application scenario, change impact and change implementation of
modifying a clock source.
Prerequisites
The desired length of the modified antenna has been planned.
Context
Only one GPS clock link is on a LMPT or UMPTb2.
Procedure
Step 1 Run the MOD GPS MML command to set Cable Length to the length of the modified
antenna.
----End
This section describes the application scenario, change impact and change implementation of
modifying time source information.
Prerequisites
Before adding or modifying NTP client information, obtain the network information of the
NTP server, such as the NTP mode, IP address of the NTP server, and ports of the NTP
server.
Procedure
Step 1 Run the SET TIMESRC MML command to set Time Source to GPS(GPS) or NTP(NTP).
Step 2 When setting the clock source from GPS to NTP, run the ADD NTPC MML command to
add the NTP client and set NTP client parameters based on the actual information of the NTP
server.
Step 3 Run the MML command SET MASTERNTPS to set the active NTP server.
Set parameters as follows:
l Set IP type to IPV4(IPv4).
l Set the value of IPv4 Address to be the same as that of IPv4 Address of NTP Server in
the ADD NTPC command.
----End
8 Adjusting Cells
Prerequisites
The information of the new cell is planned. For details, see Table 8-1.
If RF resources are insufficient and more eRRUs must be added to the new cells, configure
the eRRUs to be added before adding cells. For details about the eRRU parameter
configuration, see descriptions in DBS3900 Product Documentation.
Procedure
Step 1 Run the ADD SECTOR MML command to add a sector.
Step 2 Run the ADD CELL MML command to set parameter in Table 8-1 to add a cell.
Parameter Description
Parameter Description
Cell transmission and reception mode Indicates the transmission and reception
mode of the cell. Set parameters to 1T1R,
2T2R, 4T4R, or 8T8R based on the network
plan.
Step 3 Run the ADD CELLOP MML command to set parameters in Table 8-2 to add cell operator
information.
Step 4 Run the ACT CELL MML command to set Local cell ID to the Local cell ID of the new cell
to activate the cell.
----End
Prerequisites
Before removing a cell, remove all parameters related to the cell, such as intra-frequency
neighboring relationships. For details about how to remove intra-frequency neighboring
relationships, refer to 9.3 Removing an Intra-frequency Neighboring Cell and 9.4
Removing an Inter-frequency Neighboring Cell.
NOTE
When running the RMV CELL MML command, delete data related to the cell one by one based on the
messages displayed by the system.
Procedure
Step 1 Run the RMV CELL MML command to set Local cell ID to the Local cell ID of the desired
cell to remove the cell.
----End
Context
Modifying a cell ID will interrupt services.
If a cell serves as a neighboring cell for another intra-eNodeB cell, the cell ID cannot be
modified.
Procedure
Step 1 Run the DSP CELL MML command to query the Local cell ID of the cell.
Step 2 Run the LST EUTRANINTRAFREQNCELL and LST EUTRANINTERFREQNCELL
MML commands to check whether the cell serves as a neighboring cell for other cells.
If... Then...
The cell serves as a neighboring cell for Remove the neighboring relationship and go
other cells. to Step 3.
NOTE
For details about how to remove a neighboring
relationship, see 9.3 Removing an Intra-
frequency Neighboring Cell and 9.4 Removing
an Inter-frequency Neighboring Cell.
Step 3 Run the MOD CELL MML command to set Local cell ID to the desired Local cell ID and
set Cell ID to the modified value.
----End
Prerequisites
The new cell name has been planned.
Procedure
Step 1 Run the DSP CELL MML command to query the Local cell ID of the cell.
Step 2 Run the MOD CELL MML command to set Local cell ID to the desired Local cell ID and
set Cell Name to the modified value.
----End
Context
The maximum transmit power of a cell depends on the Reference signal power and PB in the
configuration information of the PDSCH.
Reference signal power refers to the cell reference signal power for each physical antenna. It
has the following impact on eNodeBs:
Increasing the value of Reference signal power brings higher channel estimation
accuracy, a lower demodulation threshold, and higher receiver sensitivity. However, it
causes stronger interference to neighboring cells.
l Impact on network capacity
Increasing the value of Reference signal power brings better coverage. However, a large
value limits the power used for data transmission and hence decreases system capacity.
PB refers to the scaling factor indexes of the EPRE on the PDSCH. Increasing the value of
PB brings better channel estimation performance, and better PDSCH demodulation
performance. Meanwhile, it also leads to lower transmit power of the PDSCH and therefore
increases the data rate of cell edge users (CEUs).
Procedure
Step 1 Run the DSP CELL MML command to query the current Maximum transmit
power(0.1dBm) and Local cell ID of the cell.
Step 2 Run the MOD PDSCHCFG MML command based on the site situations to set Reference
signal power and PB, to increase/decrease the maximum transmit power of the cell. Table
8-3 lists the related configuration parameters.
Parameter Description
Reference signal power GUI value range: –600 to 500; actual value
range: –60 to 50; step: 0.1; unit: 0.1 dBm
PB Value range: 0 to 3
Recommended value: 0 for single antenna
and 1 for dual antennas
----End
Context
Modifying cell EARFCNs will interrupt services.
The EARFCNs of neighboring cells must be modified when the local serving cell serves as an
inter/intra-frequency neighboring cell for others cells. You can run LST
EUTRANINTRAFREQNCELL and LST EUTRANINTERFREQNCELL MML commands
to query whether the local serving cell serves as an inter/intra-frequency neighboring cell for
others cells.
Prerequisites
The new cell EARFCNs have been planned.
Procedure
l When the local serving cell does not serve as an inter/intra-frequency neighboring cell
for others cells,
a. Run the MOD CELL MML command to set the cell EARFCNs to new Uplink
earfcn and Downlink earfcn.
l When the local serving cell serves as an inter/intra-frequency neighboring cell for others
cells,
a. Remove neighboring relationships.
Run the RMV EUTRANINTRAFREQNCELL or RMV
EUTRANINTERFREQNCELL MML command to remove all neighboring
relationship.
b. Modify cell EARFCNs.
Run the MOD CELL MML command to set the cell EARFCNs of the local serving
cell and neighboring cell to new Uplink earfcn and Downlink earfcn.
c. Add neighboring relationships.
Run the ADD EUTRANINTRAFREQNCELL or ADD
EUTRANINTERFREQNCELL MML command to recover the inter/intra-
frequency neighboring relationships. For details, see 9.1 Adding an Intra-
frequency Neighboring Cell and 9.2 Adding an Inter-frequency Neighboring
Cell.
Prerequisites
The new UL and DL CP lengths have been planned.
Context
Modifying the CP length of a cell will interrupt services.
The UL and DL cyclic prefixes of cells on the same baseband board are consistent.
Uplink cyclic prefix length, Downlink cyclic prefix length, and Special subframe patterns
are related. For details, refer to LST CELL.
Procedure
Step 1 Run the LST CELL MML command to query the Uplink cyclic prefix length, Downlink
cyclic prefix length, and Special subframe patterns of the desired cell. Determine whether
to modify Special subframe patterns based on Uplink cyclic prefix length and Downlink
cyclic prefix length.
Step 2 In the TDD scenario, run the MOD CELL MML command to set the Local cell ID of the
desired cell, update Uplink cyclic prefix length and Downlink cyclic prefix length, and
update Special subframe patterns or keep it unchanged.
Step 3 In the TDD scenario, run the MOD CELL MML command to set the Local cell ID of the
desired cell, and update Uplink cyclic prefix length and Downlink cyclic prefix length.
----End
Application scenario: The previous cell offset is inappropriate and needs to be re-planned.
Prerequisites
The new Cell specific offset has been planned.
Context
Cell specific offset affects the probability of triggering handovers from the serving cell to its
intra-frequency neighboring cells. A smaller value of this parameter leads to a higher
probability.
Procedure
Step 1 Run the MOD CELL MML command to set the Local cell ID of the desired cell, and update
Cell specific offset.
----End
Prerequisites
The new cell radius has been planned.
Context
Modifying the cell radius will interrupt services.
Cell radius(m) is related to Preamble, High speed flag, and Root sequence index.
Cell radius(m), Preamble, High speed flag, and Root sequence index are related. For details, refer to
the parameter description in MOD CELL.
Procedure
Step 1 Run the LST CELL MML command to query the Cell radius(m), Preamble, High speed
flag, and Root sequence index of the cell. Determine whether to modify Preamble, High
speed flag, and Root sequence index based on parameter relationships.
Step 2 Run the MOD CELL MML command to activate the modified Cell radius(m).
----End
Application scenario: The current bandwidth is less than 20 MHz and cannot meet service
requirements due to the increasing number of users.
Prerequisites
The new uplink (UL) and downlink (DL) bandwidths of a cell have been planned.
NOTE
Before planning the new UL and DL bandwidths, you can run the LST CELL MML command to query
the current Uplink earfcn and Downlink earfcn of the cell.
Procedure
Step 1 Run the MOD CELL MML command to modify Uplink bandwidth and Downlink
bandwidth.
----End
Application scenario: The requirement for the uplink and downlink transmission rates varies
in different scenarios.
Prerequisites
The new value of Subframe assignment has been planned.
NOTE
Context
Modifying the subframe assignment of the cell will interrupt services.
l When Preamble is set to 0, Subframe assignment can be set to only SA0, SA1 or SA2.
l When Preamble is set to 1, Subframe assignment can be set to only SA0 or SA1.
l When Preamble is set to 2, Subframe assignment can be set to only SA0 or SA1.
l When Preamble is set to 3, Subframe assignment can be set to only SA0.
l When Preamble is set to 4, Subframe assignment can be set to only SA0 or SA1.
Procedure
Step 1 Run the MOD CELL MML command to modify the Subframe assignment of the cell.
----End
Prerequisites
The new value of Special subframe patterns has been planned.
NOTE
Context
Modifying the special subframe patterns of the cell will interrupt services.
The relationships between Special subframe patterns and Preamble/Uplink cyclic prefix
length/Downlink cyclic prefix length are as follows:
l When Preamble is set to 4, Special subframe patterns can be set to only SSP4, SSP5,
or SSP7.
l When Uplink cyclic prefix length and Downlink cyclic prefix length are set to
NORMAL_CP, Special subframe patterns can be set to only SSP5 or SSP7.
l When Uplink cyclic prefix length and Downlink cyclic prefix length are set to
EXTENDED_CP, Special subframe patterns can be set to only SSP5.
l When Uplink cyclic prefix length is set to EXTENDED_CP and Downlink cyclic
prefix length is set to NORMAL_CP, Special subframe patterns can be set to only
SSP5 or SSP7.
l When Uplink cyclic prefix length is set to NORMAL_CP and Downlink cyclic prefix
length is set to EXTENDED_CP, Special subframe patterns can be set to only SSP5.
Procedure
Step 1 Run the MOD CELL MML command to modify the Special subframe patterns of the cell.
----End
This chapter describes how to adjust neighboring cells. Neighboring cells include intra-
frequency cells and inter-frequency cells.
Application scenario: The previous neighboring cell parameters are inappropriate and need to
be re-planned.
Prerequisites
l An intra-frequency cell has existed.
l The uplink (UL) and downlink (DL) EARFCNs of the local cell and intra-frequency cell
are the same.
NOTE
You can run the LST CELL MML command to query whether a neighboring cell exists and its UL and
DL EARFCNs.
Context
A maximum of 256 neighboring relationships with intra-frequency E-UTRAN cells can be
configured for a cell.
Procedure
Step 1 Run the ADD EUTRANEXTERNALCELL MML command to add external cells. If the
intra-frequency neighboring cells are under the same NodeB, you do not need to configure
them as external cells.
NOTE
----End
Prerequisites
l An inter-frequency cell has existed.
l The uplink (UL) and downlink (DL) EARFCNs of the local cell and inter-frequency cell
are the same.
You can run the LST CELL MML command to query whether a neighboring cell exists and its UL and
DL EARFCNs.
Context
A maximum of 256 neighboring relationships with inter-frequency E-UTRAN cells can be
configured for a cell.
Procedure
Step 1 Run the ADD EUTRANEXTERNALCELL MML command to add external cells. If the inter-
frequency neighboring cells are under the same NodeB, you do not need to configure them as
external cells.
Parameter Description
NOTE
----End
Application scenario: The previous neighboring cell parameters are inappropriate and need to
be re-planned.
Procedure
Step 1 Run the LST EUTRANINTRAFREQNCELL MML command to query the intra-frequency
neighboring relationships and record the Local cell ID, Mobile country code, Mobile
network code, eNodeB ID, and Cell ID of the desired neighboring relationship.
Step 2 Run the RMV EUTRANINTRAFREQNCELL MML command and input the parameter value
queried in Step 1 to remove the desired neighboring relationship.
----End
Application scenario: The previous neighboring cell parameters are inappropriate and need to
be re-planned.
Procedure
Step 1 Run the LST EUTRANINTERFREQNCELL MML command to query the inter-frequency
neighboring relationships and record the Local cell ID, Mobile country code, Mobile
network code, eNodeB ID, and Cell ID of the desired neighboring relationship.
Step 2 Run the RMV EUTRANINTERFREQNCELL MML command and input the parameter value
queried in Step 1 to remove the desired neighboring relationship.
----End
This section describes the application scenario, change impact and change implementation of
modifying VSWR alarm threshold of an eRRU.
Procedure
Step 1 Query the VSWR alarm threshold of the eRRU.
Input the Cabinet No., Subrack No., and Slot No. of the desired eRRU, and run the LST
RRU command to query RRU Topo Position, RRU Chain No., RRU Position, RRU type,
and RRU Work Standard.
Step 2 Change the VSWR alarm threshold of the eRRU.
Run the MOD RRU command, and change RRU Topo Position, RRU Chain No., RRU
Position, RRU type, and RRU Work Standard to values queried in Step 1. Table 10-1 lists
the related parameters.
Table 10-1 Parameter settings for changing the VSWR alarm threshold of an eRRU
Parameter Configuration Description
VSWR alarm post-processing threshold(0.1) Indicates the new VSWR alarm post-
processing threshold(0.1).
----End
This section describes how to adjust the transmission network, including changejing the IP
address, SCTPLNK information, and IPPATH information.
Procedure
Step 1 Query SCTP link information.
Run the LST SCTPLNK command to query First Local IP Address, First Peer IP Address,
and Peer SCTP Port No..
Step 2 Change the SCTP link information.
Run the MOD SCTPLNK command, and change First Peer IP Address and Peer SCTP
Port No. to the values queried in Step 1. Table 11-1 lists the related parameters.
----End
Application scenario: The previous IP address is inappropriate. The IP address on the service
plane of the core network is changed.
Procedure
Step 1 Query the IP PATH link information.
Run the LST IPPATH command to query Peer IP.
Step 2 Change the IP PATH link information.
Run the MOD IPPATH command, and change Peer IP to the value queried in Step 1. Table
11-2 lists the related parameters.
Table 11-2 Parameter settings for changing the IP PATH link parameters
Parameter Configuration Description
----End
Application Scenario
This section describes the scenario where the service IP address needs to be changed.
Application scenario: The previous service IP address is improperly planned. The service IP
address of the base station is changed and needs to be re-planned.
Change Impact
Services are interrupted after the service IP address of a base station is changed.
Change Implementation
This section describes how to change a service IP address.
Prerequisites
You have planned new IP addresses on the user plane and signaling plane.
Procedure
Step 1 Add a service IP address.
Run the ADD DEVIP command, and set related parameters based on the IP address on the
user plane, IP address on the signaling plane, and subnet mask. Table 11-3 describes the
related parameters.
Run the RMV DEVIP command, and set related parameters to delete the original IP addresses
on the user plane and signaling plane. Table 11-3 lists the parameters.
----End
Application Scenario
This section describes the scenario where a remote maintenance IP address needs to be
changed.
Change Impact
After a remote maintenance IP address is changed, the eNB530DBS3900eNodeB is
disconnected from the eOMC910, and all remote maintenance operations are unavailable. It is
recommended that you run MML commands in batches to change the IP address.
Change Implementation
This section describes how to change the remote maintenance IP address.
Prerequisites
l You have planned the new remote maintenance IP address.
l You have run the LST OMCH command to query Master/Slave Flag and Local IP (that
is, the original remote maintenance IP address) of the remote OM channel.
Context
The remote maintenance IP address is used to communicate with the eOMC910.
Procedure
Step 1 Add a remote maintenance IP address.
Run the ADD DEVIP command, and set related parameters based on the new remote
maintenance IP address and subnet mask. Table 11-5 describes the related parameters.
Run the MOD OMCH command, and select the desired remote OM channel based on
Master/Slave Flag. Change Local IP and Local Mask to the new remote maintenance IP
address and subnet mask.
Run the RMV DEVIP command and set related parameters. Table 11-6 lists the parameters.
----End