Monitoring Management (SRAN18.1 - Draft A)
Monitoring Management (SRAN18.1 - Draft A)
Monitoring Management (SRAN18.1 - Draft A)
Issue Draft A
Date 2021-12-30
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: https://www.huawei.com
Email: [email protected]
Contents
1 Change History.........................................................................................................................1
1.1 SRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 1
3 Overview....................................................................................................................................5
4 Monitoring Management...................................................................................................... 6
4.1 Principles.................................................................................................................................................................................... 6
4.1.1 Monitoring Managers.........................................................................................................................................................6
4.1.1.1 Introduction to Monitoring Managers...................................................................................................................... 6
4.1.1.2 BBU Monitoring Ports..................................................................................................................................................... 8
4.1.1.2.1 BBU3900/BBU3910/BBU5900 Monitoring Ports................................................................................................ 8
4.1.1.2.2 BBU3910A Monitoring Port....................................................................................................................................... 9
4.1.1.2.3 BBU5900A Monitoring Ports..................................................................................................................................... 9
4.1.1.3 CCU Monitoring Ports...................................................................................................................................................11
4.1.1.4 RRU Monitoring Ports...................................................................................................................................................11
4.1.2 Monitoring Devices........................................................................................................................................................... 11
4.1.2.1 Introduction to Monitoring Devices.........................................................................................................................11
4.1.2.2 Mapping Between Physical Boards and Logical Names of Monitoring Devices...................................... 12
4.1.3 Monitoring Networking for a Single-mode/Dual-mode Base Station............................................................ 19
4.1.3.1 BTS3900/BTS5900 Monitoring Networking.......................................................................................................... 19
4.1.3.2 BTS3900L/BTS5900L Monitoring Networking...................................................................................................... 21
4.1.3.3 BTS3900A/BTS5900A Monitoring Networking.....................................................................................................22
4.1.3.4 DBS3900/DBS5900 Monitoring Networking.........................................................................................................29
4.1.3.5 BTS3900AL Monitoring Networking........................................................................................................................ 37
4.1.3.6 BTS3900C Monitoring Networking.......................................................................................................................... 40
4.1.3.7 BTS3012 (Ver.D_Z) Monitoring Networking......................................................................................................... 40
4.1.3.8 BTS3012AE (Ver.D_Z) Monitoring Networking.................................................................................................... 40
4.1.4 Monitoring Networking for a Triple-mode or Quadruple-mode Base Station............................................ 42
4.1.5 Networking for Customized Alarms............................................................................................................................43
4.2 Network Analysis.................................................................................................................................................................. 48
4.2.1 Benefits................................................................................................................................................................................. 49
4.2.2 Impacts.................................................................................................................................................................................. 49
4.3 Requirements......................................................................................................................................................................... 49
4.3.1 Licenses................................................................................................................................................................................. 49
4.3.2 Software................................................................................................................................................................................49
4.3.3 Hardware.............................................................................................................................................................................. 49
4.3.4 Others.................................................................................................................................................................................... 49
4.4 Operation and Maintenance (eGBTS/NodeB/eNodeB/gNodeB).......................................................................... 49
4.4.1 When to Use....................................................................................................................................................................... 49
4.4.2 Planning................................................................................................................................................................................ 50
4.4.3 Data Configuration........................................................................................................................................................... 53
4.4.3.1 Data Preparation............................................................................................................................................................ 53
4.4.3.1.1 MO Setting Notes....................................................................................................................................................... 53
4.4.3.1.2 Reference for Configuring the Monitoring Function...................................................................................... 69
1. Example of Configurations in a BTS3900 (-48 V DC).................................................................................................70
2. Example of Configurations in a BTS3900 (AC)............................................................................................................. 71
3. Example of Configurations in a BTS3900L (-48 V DC).............................................................................................. 72
4. Example of Configurations in a BTS3900L (AC)........................................................................................................... 73
5. Example of Configurations in a BTS3900A (AC).......................................................................................................... 74
6. Example of Configurations in a BTS3900A (-48 V DC).............................................................................................. 82
7. Example of Configurations in a DBS3900 (AC)............................................................................................................ 84
8. Example of Configurations in a DBS3900 (-48 V DC)............................................................................................. 104
9. Example of Configurations in a BTS3900AL (AC)......................................................................................................113
10. Example of Configurations in a BTS3012 (Ver.D_Z)............................................................................................... 124
11. Example of Configurations in a BTS3012AE (Ver.D_Z).......................................................................................... 126
12. Example of Configurations in a BTS5900 (–48 V DC)........................................................................................... 131
13. Example of Configurations in a BTS5900L (–48 V DC)......................................................................................... 131
14. Example of Configurations in a BTS5900A (AC)..................................................................................................... 131
15. Example of Configurations in a BTS5900A (DC)..................................................................................................... 131
16. Example of Configurations in a DBS5900.................................................................................................................. 131
4.4.3.2 Using MML Commands............................................................................................................................................. 133
4.4.3.3 Using the MAE-Deployment.................................................................................................................................... 135
4.4.4 Activation Verification................................................................................................................................................... 135
4.4.5 Network Monitoring...................................................................................................................................................... 138
4.4.6 Reconfiguration............................................................................................................................................................... 138
4.5 Operation and Maintenance (GBTS)........................................................................................................................... 138
4.5.1 When to Use..................................................................................................................................................................... 138
4.5.2 Precautions........................................................................................................................................................................ 139
4.5.3 Data Configuration......................................................................................................................................................... 139
4.5.3.1 Data Preparation..........................................................................................................................................................139
4.5.3.1.1 MO Setting Notes.................................................................................................................................................... 139
4.5.3.1.2 Reference for Configuring the Monitoring Function....................................................................................156
5 Parameters............................................................................................................................181
6 Counters................................................................................................................................ 183
7 Glossary................................................................................................................................. 184
8 Reference Documents........................................................................................................ 185
1 Change History
Technical Changes
Change Description Parameter Change
Editorial Changes
None
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for
certain reasons. For example, the industry chain (terminals/CN) may not be
sufficiently compatible. However, these features can still be used for testing
purposes or commercial network trials. Anyone who desires to use the trial
features shall contact Huawei and enter into a memorandum of understanding
(MoU) with Huawei prior to an official application of such trial features. Trial
features are not for sale in the current version but customers may try them for
free.
Customers acknowledge and undertake that trial features may have a certain
degree of risk due to absence of commercial testing. Before using them, customers
shall fully understand not only the expected benefits of such trial features but also
the possible impact they may exert on the network. In addition, customers
acknowledge and undertake that since trial features are free, Huawei is not liable
for any trial feature malfunctions or any losses incurred by using the trial features.
Huawei does not promise that problems with trial features will be resolved in the
current version. Huawei reserves the rights to convert trial features into
commercial features in later R/C versions. If trial features are converted into
commercial features in a later version, customers shall pay a licensing fee to
obtain the relevant licenses prior to using the said commercial features. If a
customer fails to purchase such a license, the trial feature(s) will be invalidated
automatically when the product is upgraded.
3 Overview
● Monitors the power supply, fans and environment in the cabinet, and
automatically reports an alarm once an exception is detected.
● Collects alarm signals from outside the cabinet to implement user-defined
alarm monitoring, such as monitoring the environment, diesel generator, and
access control system (ACS) of the equipment room.
For details about the monitoring principles of the site monitor unit (SMU), see
XXXX Site Monitor Unit User Manual of energy products.
4 Monitoring Management
4.1 Principles
When a base station has many devices to be monitored in the cabinets, and
the BBU monitoring ports cannot meet the monitoring requirements, the CCU
of each cabinet monitors devices housed in the cabinet.
– The power cabinet TP48600A-H17B1 (TP48600A for short) and battery
cabinets IBBS700D, IBBS700T, IBBS300D, and IBBS300T use CCUs to
implement monitoring management. The CCUs are cascaded and one
CCU reports alarms to the BBU.
– APM30H (Ver.E) and TMC11H (Ver.E) cabinets can be monitored and
managed by the CCUs which can centrally manage all cabinets in a base
station but do not support cascading.
● Remote radio unit (RRU)
For some DBS3900 and DBS5900 base stations, when RRUs are installed far
away from the BBU and the alarms of devices near the RRUs need to be
collected, RRUs can directly manage these alarms. RRUs report alarms to the
BBU through common public radio interface (CPRI) optical fibers and the BBU
then forwards the alarms to the alarm console. This scenario is called RRU
remote monitoring.
A BBU3910C does not have any monitoring ports and does not support RS485
or dry contacts. External equipment can be monitored only through RRU
monitoring ports.
For details about BBU configurations, see Base Station Cabinets and Subracks
(Including the BBU Subrack) Configuration. For details about RRU configurations,
see RF Unit and Topology Management. For details about CCU configurations, see
the following sections about operation and maintenance.
The following table describes the relationships between the monitoring managers
and hardware devices.
- - BBU BBU
- - RRU RRU
LampSite base stations do not support monitoring by RRUs, but they are the same
as macro base stations in supporting other monitoring managers.
● When a BBU is configured with one UPEU, the BBU provides eight Boolean
signal inputs and two RS485 signal inputs.
● When a BBU is configured with two UPEUs or with one UPEU and one UEIU,
the BBU provides 16 Boolean signal inputs and four RS485 signal inputs. On
the UPEUs or on the UPEU and UEIU, the two MON0 ports are interconnected
through RS485 bus 0, and the two MON1 ports are interconnected through
RS485 bus 1.
Figure 4-2 shows the monitoring ports on the UPEU and UEIU.
Table 4-1 describes the monitoring ports on the UPEU and UEIU.
NOTE
The following types of RRUs cannot be remotely connected to and monitored by the CCUs:
● Internal functions of the following RRUs do not support this type of monitoring:
RRU3908, RRU3008, RRU3004(DRRU), RRU3804, RRU3806, RRU3801E, RRU3805,
RRU3801C, RRU3808, RRU3201, RRU3220, RRU3203, RRU3222, RRU3260, RRU3221, and
RRU3606
● RRUs without monitoring ports, such as Book RRUs, do not support this type of
monitoring.
For details about monitoring devices, see 3900 & 5900 Series Base Station
Component Description. For details about cable connections between monitoring
devices and monitoring managers, see Cable Connections > Monitoring Signal
Cable Connections in 3900 & 5900 Series Base Station Cables.
Mapping Table
NOTE
1:The PMU 12A is supported from SRAN12.1 onwards, and it is supported only by the
BTS3900 (Ver.D) cabinet.
2:The PMU 12A is supported from SRAN12.1 onwards, and it is supported only by the
BTS3900L (Ver.D) DC cabinet.
CMUE TCU
CMUEA TCU
CCUB2/CCUC TCU
NOTE
1: When lithium batteries are installed in an IBBS200D, the PMU 15A is required.
2:The PMU and TCU in an APM30H share the CCUB/CCUC whose E-Label can be queried
through the TCU.
3:When the IBBS200D cabinet is configured with lithium batteries and the required PMU
15A, data configuration for the PMU 15A needs to be performed.
4:When the battery cabinet BBC5200D-L is used with the power cabinet APM30H, the PMU
15A is required.
HEUB TCU
HAU TCU
TCU
PMU PMU
CMUF TCU
HAU TCU
NOTE
1: When lithium batteries are installed in an IBBS200D, the PMU 15A is required.
PMU PMU
FAU FMU
HAU TCU
CMUF/CMUEA TCU
HAU TCU
CMUF TCU
FAU FMU
HAU TCU
CCU01D-03 TCU
TCU
NOTE
The monitoring boards need to be configured only when a TP48600A cabinet is used.
DBS5900 IMB05 - -
CMUH TCU
NOTE
For details about how to connect the monitoring signal cables of the boards to relevant
ports, see sections "Cable Connections" > "Monitoring Signal Cable Connections" in 3900 &
5900 Series Base Station Cables.
A BTS3900 (Ver.E_B~D) or BTS5900 (Ver.A) cabinet used for a BTS5900 applies the
same monitoring principles as those used for a BTS3900.
The monitored boards are cascaded in sequence. If an upper-level board is not
configured, the monitoring signal cable is directly connected to the lower-level
board. The bottom-level board does not need to be connected if it is not
configured. For example:
● If the GATM is not configured, the FMU and PMU are directly connected to
the BBU's MON ports.
● If cabinet 1 and cabinet 2 are not configured, pay attention to components in
cabinet 0 only.
NOTE
Cabinet 0 is the first cabinet of this type configured at a site. The same rule also applies to
numbering cabinets of other types.
The monitoring principles of the BTS3900 cabinet (–48 V DC) are similar to those
of the BTS3900 cabinet (AC). In these cabinets, the PMU is not configured and can
be ignored in Figure 4-7.
NOTICE
In the following figure, FMU0 indicates the FMU in the lower-level subrack and
FMU1 indicates the FMU in the upper-level subrack in the BTS3900L cabinet.
Cascade them following the shown sequence.
The monitoring principles of the BTS3900L (–48 V DC) are similar to those of the
BTS3900L (AC). In the BTS3900L (–48 V DC) cabinet, the PMU in Figure 4-8 is not
configured and can be ignored. The BTS3900L (Ver.C), BTS3900L (Ver.D), and
BTS3900L (Ver.D_B) cabinets use the same monitoring principles.
BTS3900A (Ver.C)/(Ver.D)
Figures "Monitoring principles of the BTS3900A (AC)" and "Monitoring principles
of the BTS3900A (–48 V DC)" show the monitoring principles of these cabinets.
The central monitoring unit type E (CMUE)/central monitoring unit type EA
(CMUEA), PMU, GATM, and EMU communicate with the BBU's MON ports
through an RS485 serial bus. The GATM is GBTS-specific and is not used for the
eGBTS/NodeB/eNodeB/gNodeB. The following uses BTS3900A (Ver.C) cabinets as
an example.
The monitored boards are cascaded in sequence. If an upper-level board is not
configured, the monitoring signal cable is directly connected to the lower-level
board. The bottom-level board does not need to be connected if it is not
configured. For example:
● If the TMC cabinet is not configured, ignore the connections related to the
TMC cabinet. The CMUE in cabinet RFC0 is directly connected to the CMUE in
cabinet RFC1.
● If the battery backup cabinet (BBC) is not configured, ignore the connections
to the CMUE in the BBC.
The monitoring principles of the BTS3900A (Ver.D), BTS3900A (Ver.D_B),
BTS3900A (Ver.D_A1), and BTS3900A (Ver.D_A2) cabinets are the same as those of
the BTS3900A (Ver.C) cabinet, except that no HERT power monitoring interface
unit (HPMI) is configured. The HPMI does not monitor signals but transfers signals
for the PMU. It is not shown in the figures. Figures "Monitoring principles of the
BTS3900A (AC)" and "Monitoring principles of the BTS3900A (–48 V DC)" use the
BTS3900A (Ver.C) cabinet as the example to illustrate the monitoring principles.
For the BTS3900A (Ver.D), BTS3900A (Ver.D_B), BTS3900A (Ver.D_A1), and
BTS3900A (Ver.D_A2), the CMUE is replaced with the CMUEA.
A BTS5900A applies the same monitoring principles as a BTS3900A.
NOTICE
Two BBCs are cascaded in sequence and cannot be connected to the same PMU.
For example, if BBC0 is connected to the PMU's COM_485 port, BBC1 is connected
to the CMUE's COM_OUT port in BBC0 and cannot be connected to the other
RS485 ports on the PMU.
NOTE
BBCs are IBBS200D, IBBS200T, IBBS700D, IBBS700T, IBBS300D, and IBBS300T cabinets. (IBBS
is short for integrated backup battery system.) The monitoring board in an IBBS700D
cabinet is CMUEA and the monitoring board in an IBBS700T cabinet is CMUF. The
monitoring board in an IBBS300D or IBBS300T cabinet is CCU01D-03.
BTS3900A (Ver.E)
Figures "Monitoring principles of the BTS3900A (Ver.E) AC cabinet" and
"Monitoring principles of the BTS3900A (Ver.E) (–48 V)" show the monitoring
principles of the BTS3900A (Ver.E) cabinet.
NOTE
● BBCs are IBBS200D, IBBS200T, IBBS300D, and IBBS300T cabinets. The monitoring board
in an IBBS300D or IBBS300T cabinet is CCU01D-03.
● The TCU and PMU in an APM30H cabinet share the CCUB, whose E-Label can be
queried through the TCU. Port U_COM0 on the CCUB in the cabinet where the BBU is
installed is connected to port MON0 of the BBU, port U_COM1 is connected to port
MON1 of the BBU, lower-level electromechanical components are connected to BBU
communication ports MON0-0, MON0-1, MON1-0, and MON1-1 to which the CCUB is
mapped, respectively. The BBC is connected to COM_485 port of the CCUB.
● If the eBat battery management function is used for the Ver.E cabinet with RRUs
remotely installed, the CCU monitoring is implemented by connecting the CCU to
remote RRUs, which cannot be the following RRUs: RRU3908, RRU3008, RRU3004
(DRRU), RRU3804, RRU3806, RRU3801E, RRU3805, RRU3801C, RRU3808, RRU3201,
RRU3220, RRU3203, RRU3222, RRU3260, RRU3221, and RRU3606. The intelligent
battery monitoring function has been disused and is no longer supported. Therefore, the
board does not need to be configured as CCU.
NOTE
The TCU hardware board in a TMC cabinet is the CCUB. Port U_COM0 on the CCUB in the
cabinet where the BBU is installed is connected to port MON0 of the BBU, port U_COM1 is
connected to port MON1 of the BBU, lower-level electromechanical components are
connected to BBU communication ports MON0-0, MON0-1, MON1-0, and MON1-1 to
which the CCUB is mapped, respectively.
BTS5900A (Ver.A)
Figure 4-13 and Figure 4-15 show the monitoring principles of the BTS5900A
(Ver.A) cabinet.
NOTE
NOTE
● BBCs are BBC5600D and BBC5600D-V cabinets. The monitoring board in a BBC5600D or
BBC5600D-V cabinet is CMUH.
● Only the PMU11C is installed in the APM5950H cabinet. You can query the electronic
label of the cabinet through the PMU. The COM_IN port on the PMU11C in the cabinet
where the BBU is installed is connected to the MON1 port on the BBU.
● The monitored boards are cascaded in sequence. If an upper-level board is not
configured, the monitoring signal cable is directly connected to the lower-level board.
The bottom-level board does not need to be connected if it is not configured. For
example, if the TMC cabinet is not configured, ignore the connections related to the
TMC cabinet. The CMUH in cabinet RFC0 is directly connected to the CMUH in cabinet
RFC1. If the BBC is not configured, ignore the connections to the CMUH in the BBC.
NOTE
The TCU hardware board in an APM5930(DC) cabinet is the CCUC. Port U_COM0 on the
CCUC in the cabinet where the BBU is installed is connected to port MON0 of the BBU, port
U_COM1 is connected to port MON1 of the BBU, lower-level electromechanical components
are connected to BBU communication ports MON0-0, MON0-1, MON1-0, and MON1-1 to
which the CCUC is mapped.
NOTE
The monitored boards are cascaded in sequence. If an upper-level board is not configured,
the monitoring signal cable is directly connected to the lower-level board. The bottom-level
board does not need to be connected if it is not configured. For example, if the TMC
cabinet is not configured, ignore the connections related to the TMC cabinet. The CMUH in
cabinet RFC0 is directly connected to the CMUH in cabinet RFC1. If the BBC is not
configured, ignore the connections to the CMUH in the BBC.
● APM30H (Ver.E)
● TMC11H (Ver.E)
● IBBS200D (Ver.E)/IBBS200T (Ver.E)
● MRE1000
110 V AC/220 V AC Indoor centralized rack (ICR): The BBU For details, see (4) in Figure
and PMU are installed in the upper and 4-19.
lower racks respectively in the indoor
mini box (IMB03/IMB05).
+24 V DC ICR: The BBU is installed in the IMB03/ For details, see (5) in Figure
IMB05 cabinet. 4-19.
110 V AC/220 V AC BBU3910A+outdoor power module For details, see (6) in Figure
50M (OPM50M) 4-19.
NOTE
● The DBS3900 is not configured with the GATM or the RFC cabinet, so the cable
connections to the GATM or to the RFC cabinet can be ignored. The BBU in the APM30H
cabinet is directly connected to the CMUE in the TMC11H cabinet.
● The MRE1000 cabinet does not support the eBat battery management function.
● When the BBU3910A functions as the monitoring manager, it can monitor a maximum
of three cascaded OPM50M/PMU modules. If only one or two OPM50M/PMU modules
are configured at a site, you only need to connect the cables for the configured
OPM50M/PMU modules.
The DBS5900 has multiple application scenarios. The monitoring principles vary
with hardware configurations, as described in Table 4-15.
110 V AC/220 V AC ICR: The BBU and PMU are installed in The monitoring principles are
the upper and lower racks respectively the same as those of a
in the IMB05 cabinet. DBS3900. For details, see (4) in
Figure 4-19.
NOTE
If the DBS5900 is not configured with the GATM and RFC, ignore the cable connections for
the GATM and RFC.
For the APM/TMC series cabinets used in the DBS3900 in RRU remote monitoring
mode, the monitoring principles of the Ver.D/Ver.D_B/Ver.D_A1/Ver.D_A2 cabinets
are the same as those of the Ver.C cabinets, except that the CMUE is replaced with
the CMUEA. Figure 4-17 shows the monitoring principles of the Ver.C cabinets.
Figure 4-20 shows the monitoring principles of APM/TMC (Ver.E) cabinets of the
DBS3900 when RRU remote monitoring is used.
Figure 4-20 shows the monitoring principles of APM5930 series cabinets of the
DBS5900 when RRU remote monitoring is used.
Figure 4-18 Monitoring principles of the DBS3900 configured with the TP48600A
NOTE
In SRAN10.1 and SRAN11.1, the software of the base station does not support
MEB configuration. The MEB provides physical links only and does not require
configuration. The RS485 and dry contact functions are configured on the RRU
connecting to the MEB using a power cable. In this case, the MEB does not
support the alarm, log, inventory, and upgrade functions.
In SRAN12.1 and later versions, the MEB must be configured on a newly deployed
base station in order to support the alarm, log, inventory, and upgrade functions.
You are advised to configure the dry contact alarms on the MEB. The MEB can be
configured for only one RAT. When an MEB is configured, the dry contacts
configured on the manager RRU do not take effect.
During a base station upgrade from SRAN10.1 or SRAN11.1 to SRAN12.1, MEB
configuration does not require modification.
NOTE
● The OPM200 is preferentially monitored by the remotely installed RRU that is powered
by the OPM200. When the BBU5900A is used for monitoring, the monitoring cable for
the OPM200 is connected to the MON0/MON1 monitoring port on the UEIUd in the
BBU5900A.
● The RS485 bus 0 is required for the RRU that does not support the power cable
connection shown in the preceding figure.
The GDU cannot be cascaded and must be directly connected to the BBU. The
GDU in the cabinet can be connected to the BBU for management through the
RS485 communication link.
In SRAN17.0 and later versions, the GDU can be configured but not on the GBTS.
NOTE
Unlike that in an IBBS700D/IBBS700T cabinet, the CCU and CMUF/CMUEA are integrated
into a CCU01D-03 in an IBBS300D/IBBS300T cabinet. However, the CCU and TCU must be
both configured, and only the CCU reports inventory information. Ignore the cable
connections between the CCU and the CMUF/CMUEA. In addition, connect the HAU to the
D_COM0 port on the CCU01D-03.
Figure 4-28 shows the monitoring principles of the BTS3012AE (Ver.D_Z) cabinets
configured with IBBS2.1/IBBS2.2 cabinets.
BTS3900A/ APM30H (Ver.C) Door status sensor, which is connected to the GATE
DBS3900(1) port on an HPMI
(2)
APM30H (Ver.D)/APM30H Door status sensor, which is connected to the GATE
(Ver.D_B)/APM30H port on a PMU
(Ver.D_A1)/APM30H
(Ver.D_A2)
BTS3900/ BTS3900/BTS3900L -
BTS3900L
BTS3900AL(5 BTS3900AL (AC)/ ● Door status sensor, which is connected to the GATE
) BTS3900AL (DC) port on a CCU
● Return air temperature sensor for HEX inner
circulation, which is connected to the TEM0 port on
a CMUF
● Intake air temperature sensor for the RF
compartment, which is connected to the TEM0 port
on an FAU
● Supply air temperature sensor for HEX inner
circulation, which is connected to the TEMP1 port
on a CMUF
BTS3900C BTS3900C -
BTS3012AE BTS3012AE (Ver.D_Z) AC ● Door status sensor, which is connected to the GATE
(Ver.D_Z) port on a PMU
● Temperature sensor for the battery, which is
connected to the BAT_TEMP port on a PMU
IMB05 -
NOTE
(1): The door status sensor is installed only in the RFC5906 complying with UK standards.
BTS5900A APM30H (Ver.E) Door status sensor, which is connected to the GATE
port on a CCUB/CCUC
RFC5906 (Ver.A) (7) ● Door status sensor, which is connected to the GATE
port on a CMUH
NOTE
1. The DBS3900 configured with the OMB or IMB does not have preinstalled sensors. The
BBU3910A configured with the IBBS20D cabinet has a preinstalled door status sensor
and does not have one when the BBU3910A is not configured with the IBBS20D cabinet.
2. The DBS3900 may also be configured with the TP48600A cabinet. For details about the
sensor configuration in this cabinet, see TP48600A-H17B1 User Manual.
3. In the BTS3900A (Ver.C), the sensors are connected to the CMUE. In the BTS3900A
(Ver.D), the sensors are connected to the CMUEA. In the BTS3900A (Ver.E), the sensors
are connected to the CMUH.
4. In the TMC11H (Ver.C), the sensors are connected to the CMUE. In the TMC11H (Ver.D),
the sensors are connected to the CMUEA. In the TMC11H (Ver.E), the sensors are
connected to the CCUB/CCUC.
5. The BTS3900AL site may also be configured with the TP48600A, IBBS700D, IBBS700T,
IBBS300D, and IBBS300T. For details about the sensor configurations of these cabinets,
see the TP48600A-H17B1 User Manual and 3900 & 5900 Series Base Station Cabinet
Description.
6. Most small cell products use dry contact inputs and customized alarms for monitoring.
7. The door status sensor is installed only in the RFC5906 complying with UK standards.
4.2.1 Benefits
None
4.2.2 Impacts
None
4.3 Requirements
4.3.1 Licenses
There are no license requirements for basic functions.
4.3.2 Software
Prerequisite Functions
None
4.3.3 Hardware
Software configuration varies with hardware configuration and monitoring cable
connections among boards. Before you configure software, collect information
about the following devices based on the actual hardware configuration or
hardware configuration plan:
● Monitoring managers: BBU, CCU, and RRU. Plan the manager of each board
according to 4.1 Principles.
● Monitoring device: see Mapping Table. The boards that are not listed in the
tables are configured by default. If the GATM board is installed in a GBTS, the
board must be configured in any scenario listed in the corresponding table.
The logical name of GATM is GATM.
4.3.4 Others
None
4.4.2 Planning
RF Planning
None
Network Planning
None
Hardware Planning
Configuration Planning for Monitoring Devices
The EMU/EMUB is required for configuring customized alarms on base stations.
Table 4-20 and Table 4-21 describe the hardware planning of equipment related
to customized alarms. The logical names in tables are the names of devices
displayed on the configuration tool interface.
NOTE
1. When 1 to 16 customized Boolean inputs are required, the UPEU and UEIU boards can
be configured in the BBU to meet the requirements. You are not advised to configure
customized alarms for the Boolean alarm ports on the FMU, PMU, CMUE, CMUF,
CMUEA, CMUH, and CCU. If you need to use these ports, contact Huawei technical
support engineers.
2. The EMU and EMUB support 32 Boolean inputs and 4 analog inputs. For details about
the monitoring ports on them, see EMU User Guide and EMUB User Guide. You are
advised to preferentially use the EMUB.
3. Some RRUs support 2 or 4 Boolean inputs. Some RRUs can connect to an MEB and the
MEB supports 6 Boolean inputs. For details, see section "RRU Ports" in the related RRU
hardware description.
4. The EMU and EMUB cannot be installed on a BTS3900C (Ver.C).
5. If a BBU3910A configured in a DBS3900 uses AC power supplies and an OPM50M is
connected to the EXT_ALM port, the EXT_ALM_A port on the OPM50M can provide 4
Boolean inputs for the BBU3910A when no battery cabinet can provide backup power.
● Base station's Boolean alarm inputs must be dry contact alarm inputs.
● It is recommended that optical coupling isolation or relay isolation Boolean
inputs be used. When either of the inputs is used, open circuit indicates alarm
reporting, and short circuit indicates no alarm.
● It is not recommended that the voltage signals be used as the BBU Boolean
inputs. If voltage signal alarms are used, ensure that alarm devices and alarm
input devices (BBU, EMU, or EMUB) are properly grounded. When the BBU
input alarms are of the voltage type, 0 V to 0.7 V indicate low voltage, and 3
V to 5 V indicate high voltage. When the EMU/EMUB input alarms are of the
voltage type, 0 V to 0.7 V indicate low voltage, and 5 V to 12 V indicate high
voltage.
Cabinet No. FMU.CN (LTE eNodeB, This parameter specifies the number of the cabinet
5G gNodeB) housing the FMU.
If the number of the RFC housing the FMU is 1, set this
parameter to 1.
Subrack No. FMU.SRN (LTE eNodeB, This parameter specifies the number of the subrack
5G gNodeB) housing the FMU. Set this parameter to 11 or 12.
Slot No. FMU.SN (LTE eNodeB, This parameter specifies the number of the slot
5G gNodeB) housing the FMU. Set this parameter to the default
value 0.
Manager FMU.MCN (LTE The manager of the board is generally a BBU or CCU
Cabinet No. eNodeB, 5G gNodeB) that directly communicates with the board. Set this
parameter to the cabinet number of the BBU or CCU.
Manager FMU.MSRN (LTE The manager of the board is generally a BBU or CCU.
Subrack No. eNodeB, 5G gNodeB) Set this parameter to the subrack number of the BBU
or CCU.
Manager FMU.MPN (LTE eNodeB, This parameter specifies the number of the monitoring
Port No. 5G gNodeB) port on the manager to which the board is connected.
If the FMU is connected to the BBU:
● UPEU/UEIU (MON1): 1
● UPEU/UEIU (MON0): 0
If the FMU is connected to the CCU, it must be
connected to port D_COM1. Set this parameter to 1.
Smart FMU.STC (LTE eNodeB, This parameter specifies whether to enable smart
Temperature 5G gNodeB) temperature control.
Control When this parameter is set to ENABLE, the cabinet
adjusts the fan speed according to the carrier
temperature. In this mode, the fan noise is low.
When this parameter is set to DISABLE, the cabinet
adjusts the fan speed according to the temperature of
the air intake vent. In this mode, the fan noise is high.
ENABLE(Enable) is recommended.
Cabinet No. TCU.CN (LTE eNodeB, 5G This parameter specifies the number of the cabinet
gNodeB) housing the TCU.
If the number of the APM30H housing the TCU is 0,
set this parameter to 0.
Subrack No. TCU.SRN (LTE eNodeB, This parameter specifies the number of the subrack
5G gNodeB) housing the TCU. Set this parameter to 8 or 14.
Slot No. TCU.SN (LTE eNodeB, 5G This parameter specifies the number of the slot
gNodeB) housing the TCU. Value range: 0 to 3
If the TCU is installed in the BTS3900AL AC,
BTS3900AL DC, IBBS700D, or IBBS700T cabinet, set
this parameter as follows:
● Set the slot number of the CMUF to 0.
● Set the slot number of HAU0 to 1.
● Set the slot number of HAU1 to 2.
If the TCU is installed in the TP48600A cabinet, set
this parameter as follows:
● Set the slot number of the CMUF for cabinet
temperature control to 0.
● Set the slot number of the CMUF for battery
cabinet temperature control to 1.
● Set the slot number of HAU0 to 2.
● Set the slot number of HAU1 to 3.
If the TCU is installed in other cabinets, set this
parameter to 0.
Manager TCU.MCN (LTE eNodeB, The manager is generally a BBU, CCU, or RRU. Set this
Cabinet No. 5G gNodeB) parameter to the cabinet number of the BBU, CCU, or
RRU.
Manager TCU.MSRN (LTE eNodeB, The manager is generally a BBU, CCU, or RRU. Set this
Subrack No. 5G gNodeB) parameter to the subrack number of the BBU, CCU, or
RRU.
Manager TCU.MPN (LTE eNodeB, This parameter specifies the number of the
Port No. 5G gNodeB) monitoring port on the manager to which the board is
connected.
If the TCU is connected to the BBU:
● UPEU/UEIU (MON1): 1
● UPEU/UEIU (MON0): 0
If the TCU is connected to the CCU:
● The CMUF must be connected to port D_COM0. In
this case, set this parameter to 0.
● The FAU0 or FAU1 must be connected to port
D_COM3. In this case, set this parameter to 3.
If the TCU is connected to the RRU, set this
parameter to 0.
If the TCU is connected to the BBU3910A, set this
parameter to 0.
Temperature TCU.TLTHD (LTE eNodeB, This parameter specifies the lower temperature limit
Alarm Lower 5G gNodeB) for the cabinet. If the temperature is below the lower
Threshold limit, the base station reports ALM-25652 Cabinet
Temperature Unacceptable.
It is recommended that this parameter be set to -33
for the TCU in the OMB and -20 for the TCU in other
cabinets.
Temperature TCU.TUTHD (LTE This parameter specifies the upper temperature limit
Alarm eNodeB, 5G gNodeB) for the cabinet. If the temperature exceeds the upper
Upper limit, the base station reports ALM-25652 Cabinet
Threshold Temperature Unacceptable.
● Set this parameter to 50 for the TCU in the BBC.
● Set this parameter to 68 for the TCU in other
cabinets.
Cabinet No. CCU.CN (LTE eNodeB, 5G This parameter specifies the number of the cabinet
gNodeB) housing the CCU.
If the number of the BTS3900AL cabinet housing the
CCU is 0, set this parameter to 0.
Subrack No. CCU.SRN (LTE eNodeB, This parameter specifies the number of the subrack
5G gNodeB) housing the CCU. Set this parameter to the default
value 15.
Slot No. CCU.SN (LTE eNodeB, 5G This parameter specifies the number of the slot
gNodeB) housing the CCU. Set this parameter to the default
value 0.
Manager CCU.MCN (LTE eNodeB, The manager of the board is generally a BBU or RRU.
Cabinet No. 5G gNodeB) Set this parameter to the cabinet number of the BBU
or RRU.
Manager CCU.MSRN (LTE eNodeB, The manager of the board is generally a BBU or RRU.
Subrack No. 5G gNodeB) Set this parameter to the subrack number of the BBU
or RRU.
Manager CCU.MPN (LTE eNodeB, This parameter specifies the number of the serial
Port No. 5G gNodeB) port on the manager to which the board is
connected.
The CCU must be connected to port MON0 on the
BBU. In this case, this parameter must be set to 0.
The CCU must be connected to port EXT_ALM on the
RRU. In this case, this parameter must be set to 0.
DirectConne CCU.DCF (LTE eNodeB, This parameter specifies whether the CCU is directly
ctFlag 5G gNodeB) connected to its manager.
If the CCU is directly connected to its manager, set
this parameter to YES. If the CCU is connected to its
manager over a cascaded CCU, set this parameter to
NO.
Cascade No. CCU.CCN (LTE eNodeB, This parameter specifies the position of the CCU on a
5G gNodeB) CCU chain. Set this parameter to 1 for the leftmost
CCU on the chain (the CCU whose port FE_L is not
connected). Set this parameter to an integer in
ascending order for the other CCUs on the chain.
Connected CCU.CS (LTE eNodeB, 5G This parameter specifies the working standard of the
RAT gNodeB) BBU that is directly connected to the CCU. Set this
parameter based on the actual situation.
The parameter is valid only when DCF is set to Yes.
Step 1 Prepare EMU/MEB configuration data. Before data preparation, check whether the
EMU/MEB needs to be configured by referring to Table 4-25. If the EMU/MEB is
required, prepare configuration data by referring to the following table. Otherwise,
skip this step.
Step 2 Prepare configuration data of the alarm signal input and output ports based on
the input and output requirements of customized alarms.
----End
Slot No. ALMPORT.SN (LTE Set this parameter to the actual slot
eNodeB, 5G gNodeB) number.
Cabinet No. OUTPORT.CN (LTE eNodeB, Set this parameter to the actual cabinet number.
5G gNodeB)
Subrack No. OUTPORT.SRN (LTE Set this parameter to the actual subrack number.
eNodeB, 5G gNodeB)
Slot No. OUTPORT.SN (LTE eNodeB, Set this parameter to the actual slot number.
5G gNodeB)
Port No. OUTPORT.PN (LTE eNodeB, Value range: 0 to 5 for the EMU/EMUB;
5G gNodeB) 0 for the BBU3910A
NOTE
If devices to be monitored connect to an MEB, the manager of the boards is the RRU which
also connects to the MEB.
Cabinet No. MEB.CN (LTE eNodeB, 5G This parameter specifies the number of the
gNodeB) cabinet housing the MEB.
Subrack No. MEB.SRN (LTE eNodeB, This parameter specifies the number of the
5G gNodeB) subrack housing the MEB.
Slot No. MEB.SN (LTE eNodeB, 5G This parameter specifies the number of the slot
gNodeB) housing the MEB.
Manager Cabinet MEB.MCN (LTE eNodeB, The manager is the RRU which connects to the
No. 5G gNodeB) board using a power cable. Set this parameter
to the cabinet number of the manager.
Manager Subrack MEB.MSRN (LTE eNodeB, The manager is the RRU which connects to the
No. 5G gNodeB) board using a power cable. Set this parameter
to the subrack number of the manager.
● The GDU does not need to be configured when the software version of the
base station does not support GDU configuration. In this case, the OSS cannot
manage the GDU, that is, the OSS cannot report alarms, logs, and inventory
data of the GDU, and does not support the remote upgrade for the GDU
+SLPA.
● The GDU must be configured when the base station software version supports
the GDU configuration. If the GDU is not configured, it cannot be managed
by the OSS.
The following table describes the parameter settings for the GDU.
Port No. GDU.PN The GDU has two GNSS input ports. If
this parameter is set to AUTO(Auto),
the GDU automatically selects a port
number. If it is set to 0 or 1, the GDU
forcibly switches to the corresponding
port.
The value AUTO is recommended.
NOTE
1. This section describes the configurations in the Ver.C cabinets for the BTS3900 and
BTS3900L. The configurations in the Ver.D/Ver.D_B/Ver.D_A series cabinets and BTS3012
(Ver.D_Z) cabinets are the same as those in the Ver.C cabinets, except that the FMUE is
replaced with the FMUEA.
2. This section also describes the configurations in the Ver.C cabinets for the BTS3900A and
DBS3900. The configurations in the Ver.D/Ver.D_B/Ver.D_A1/Ver.D_A2 cabinets are the
same as those in the Ver.C cabinets, except that the CMUE is replaced with the CMUEA
and no HPMI is configured.
3. This section describes the configurations of a single-, dual-, or triple-mode base station
with only one BBU. If two BBUs are configured for a triple-mode base station, the
second BBU does not perform the monitoring function and the monitoring configuration
is the same as that when one BBU is configured.
4. This section describes the maximum configuration. If a cabinet is not configured at a
site, the monitoring signal cable is directly connected to the lower-level cabinet. If a
device is not configured at a site, the monitoring signal cable is directly connected to
the lower-level device.
0 51 0 GAT 0 0 1 22 For
M GBTS
only
0 11 0 FMU 0 0 0 14 FMU
E
0 40 0 EMU 0 0 1 2 The
EMU
is
optio
nal.
NOTE
When a BTS3900 (AC) is stacked with an IMS06, the PMU is installed in the IMS06, which
makes no difference to connections of monitoring signal cables.
When two BTS3900L cabinets are deployed, each BTS3900L cabinet is stacked with an
IMS06.
0 40 0 EMU 0 0 1 2 The
EM
U is
opti
ona
l.
NOTE
The cabinet number and cabinet type of the IMS06 must be set to the same values as those
of the BTS3900.
0 50 0 GAT 0 0 0 22 For
M GBTS
only
0 51 0 GAT 0 0 1 22 For
M GBTS
only
0 11 0 FMU 0 0 0 14 -
0 12 0 FMU 0 0 0 15 -
0 7 0 PMU 0 0 1 3 -
0 50 0 GAT 0 0 0 22 For
M GBTS
only
0 51 0 GAT 0 0 1 22 For
M GBTS
only
0 11 0 FMU 0 0 0 14 -
0 12 0 FMU 0 0 0 15 -
NOTICE
The HPMI board is configured in the APM30H (Ver.C), but is not configured in the
APM30H (Ver.D). Therefore, the monitoring signal cable connections between the
PMU and the HPMI do not need to be considered for the APM30H (Ver.D) cabinet.
Figure 4-35 and Figure 4-36 show the monitoring signal cable connections in a
BTS3900A (AC) (1 APM30H+1 RFC+2 IBBS200D/IBBS200T cabinets+1 TMC11H).
NOTE
The preceding figure uses the Ver.C cabinet as an example. The monitoring unit of a Ver.C
cabinet is CMUE. The monitoring unit of a Ver.D cabinet is CMUEA.
NOTE
The preceding figure uses the Ver.E cabinet as an example. The TCU and PMU in an
APM30H cabinet are connected to the same CCUB/CCUC. PMIU is the power signal transfer
board and does not need to be configured.
Figure 4-37 and Figure 4-38 show the monitoring signal cable connections in a
BTS3900A (AC) (2 APM30H cabinets+2 RFCs+2 IBBS200D/IBBS200T cabinets).
Figure 4-37 Monitoring signal cable connections in a BTS3900A (Ver.C) (2 APM30H cabinets+2 RFCs
+ 2 IBBS200D/IBBS200T cabinets)
NOTE
The preceding figure uses the Ver.C cabinet as an example. The monitoring unit of a Ver.C
cabinet is CMUE. The monitoring unit of a Ver.D cabinet is CMUEA.
NOTE
The preceding figure uses the Ver.E cabinet as an example. The TCU and PMU in an
APM30H cabinet are connected to the same CCUB/CCUC. PMIU is the power signal transfer
board and does not need to be configured.
Figure 4-39 shows the monitoring signal cable connections in a BTS3900A (AC) (2
APM30H cabinets+2 RFCs+4 IBBS200D/IBBS200T cabinets+1 TMC11H).
NOTE
The preceding figure uses the Ver.C cabinet as an example. The monitoring unit of a Ver.C
cabinet is CMUE. The monitoring unit of a Ver.D cabinet is CMUEA.
NOTE
The preceding figure uses the Ver.E cabinet as an example. The TCU and PMU in an
APM30H cabinet are connected to the same CCUB/CCUC. PMIU is the power signal transfer
board and does not need to be configured.
NOTE
The preceding figure uses the Ver.E cabinet as an example. The TCU and PMU in an
APM30H cabinet are connected to the same CCUB/CCUC.
PMIU is the power signal transfer board and does not need to be configured with
monitoring data.
NOTE
The preceding figure uses the Ver.C cabinet as an example. The monitoring unit of a Ver.C
cabinet is CMUE. The monitoring unit of a Ver.D cabinet is CMUEA.
0 51 0 GAT 0 0 1 22 For
M GBTS
only
0 40 0 EMU 0 0 1 2 -
NOTICE
The HPMI board is configured in the APM30H (Ver.C), but is not configured in the
APM30H (Ver.D). Therefore, the monitoring signal cable connections between the
PMU and the HPMI do not need to be considered for the APM30H (Ver.D).
Figure 4-44 and Figure 4-45 show the monitoring signal cable connections in a
DBS3900 (AC) (2 APM30H cabinets+2 IBBS200D/IBBS200T cabinets+1 TMC11H).
NOTE
The preceding figure uses the Ver.C cabinet as an example. The TCU of a Ver.C cabinet is
CMUE. The TCU of a Ver.D cabinet is CMUEA.
NOTE
The preceding figure uses the Ver.E cabinet as an example. The TCU and PMU in an
APM30H cabinet are connected to the same CCUB/CCUC. PMIU is the power signal transfer
board and does not need to be configured.
Figure 4-46 and Figure 4-47 show the monitoring signal cable connections in a
DBS3900 (AC) (2 APM30H cabinets+4 IBBS200D/IBBS200T cabinets+1 TMC11H).
Figure 4-46 Monitoring signal cable connections in a DBS3900 (2 APM30H cabinets+4 IBBS200D/
IBBS200T cabinets+1 TMC11H)
NOTE
The preceding figure uses the Ver.C cabinet as an example. The TCU of a Ver.C cabinet is
CMUE. The TCU of a Ver.D cabinet is CMUEA.
NOTE
The preceding figure uses the Ver.E cabinet as an example. The TCU and PMU in an
APM30H cabinet are connected to the same CCUB/CCUC. PMIU is the power signal transfer
board and does not need to be configured.
Figure 4-48 and Figure 4-49 show the monitoring signal cable connections in a
DBS3900 in the RRU remote monitoring scenario.
Figure 4-48 Monitoring signal cable connections in a DBS3900 in the RRU remote
monitoring scenario
Figure 4-49 Monitoring signal cable connections in a DBS3900 (Ver.E) in the RRU
remote monitoring scenario
Figure 4-50 shows the monitoring signal cable connections in a DBS3900 (AC) (1
OMB (Ver.C)+2 IBBS20D cabinets).
0 8 0 TCU 0 0 1 7 HEUB
0 8 0 TCU 0 0 1 7 -
Figure 4-53 shows the monitoring signal cable connections in a DBS3900 (with
AC power input) deployed in BBU+RRU+IMB mode. The BBU is installed in an IMB
cabinet and the RRU is installed outdoors.
Figure 4-53 Monitoring signal cable connections in a 110 V/220 V base station
deployed in BBU+RRU+IMB mode
NOTE
● For details about monitoring board configurations, see Operation and Maintenance
(eGBTS/NodeB/eNodeB/gNodeB) > Data Configuration > Data Preparation >
Deployment of Basic Power Supply Management Functions in Power Supply
Management.
● The subrack No. and slot No. for all OPM50M modules must be set to 7 and 0,
respectively, regardless of the number of OPM50M modules configured.
● If only one OPM50M is configured, the data in the row marked [1][2] does not need to
be configured. If two OPM50M modules are configured, the data in the row marked [2]
does not need to be configured.
● If no backup power is available, you do not need to configure the parameters in the row
describing the corresponding cabinet.
NOTE
Blade lithium batteries do not need to be separately configured for the IBBS20L. The
backup power type is lithium power.
NOTE
● For details about monitoring board configurations, see Operation and Maintenance
(eGBTS/NodeB/eNodeB/gNodeB) > Data Configuration > Data Preparation >
Deployment of Basic Power Supply Management Functions in Power Supply
Management.
● The subrack No. and slot No. for all OPM50M modules must be set to 7 and 0,
respectively, regardless of the number of OPM50M modules configured.
Figure 4-56 shows the monitoring signal cable connections for the DBS3900 (1
BBU3910A+1 OPM15M).
NOTE
Blade lithium batteries do not need to be separately configured for the IBBS20L-E. The
backup power type is lithium power.
Figure 4-58 shows the monitoring signal cable connections in a DBS3900 (1 RRU
+1 OPM50M+2 IBBS20L modules).
NOTE
If an RRU can receive RS485 signals and dry contact alarm signals from a DC power cable,
you do not need to connect the RRU to an OPM50M (Ver.B) through a monitoring signal
cable. An MEB06D/MEB06D Ver.B connects to power devices and monitored devices and
carries external RS485 signals and dry contact alarm signals on a power circuit.
Figure 4-59 shows the monitoring signal cable connections in a DBS3900 (1 RRU
+1 OPM50M+2 IBBS20D cabinets).
NOTE
If an RRU can receive RS485 signals and dry contact alarm signals from a DC power cable,
you do not need to connect the RRU to an OPM50M (Ver.B) through a monitoring signal
cable. An MEB06D/MEB06D Ver.B connects to power devices and monitored devices and
carries external RS485 signals and dry contact alarm signals on a power circuit.
NOTE
The lithium batteries are cascaded through the "COM_IN" and "COM_OUT" ports. The
"COM_IN" port on the first-level lithium batteries is connected to the "CAN" port on the
PMID.
0 8 0 TCU 0 0 1 7 -
0 4 0 EMU 0 0 1 2 The
0 EMU is
optional
.
NOTE
● Lithium batteries in the BBC5600D lithium battery cabinet are cascaded through
COM_IN and COM_OUT. The COM_IN port on the first-level lithium battery is connected
to the CAN port on the PMU11C.
● When the battery cabinet is a BBC5600D-V lead-acid battery cabinet, the lithium battery
cascading cable in the preceding monitoring cables is not used.
0 4 0 EMU 0 0 1 2 EMU
0 (optiona
l)
0 17 1 BDU - - - - BDU
1
(opti
onal)
[1]
0 17 2 BDU - - - - BDU
2
(opti
onal)
[1]
8 17 1 BDU - - - - BDU
1
(opti
onal)
[1]
8 17 2 BDU - - - - BDU
2
(opti
onal)
[1]
NOTE
[1] When configuring the BDU, you can specify the type of a device. If this parameter is set
to DEFAULT, the system does not check the BDU, HSU, and SDU types. If this parameter is
set to BDU, HSU, or BDU, the system checks whether the type of the BDU, HSU or SDU in
use is consistent with the configuration.
A BBU3910C does not have any monitoring ports. If a DBS3900 supplied with –48
V power uses a BBU3910C, the power system is connected to an RRU monitoring
port to implement monitoring. The RRU is connected to the BBU3910C using a
CPRI optical fiber. In this way, the power system is monitored by the base station.
Figure 4-68 and Figure 4-69 show the monitoring signal cable connections.
NOTE
● For details about how to connect an alarm cable to an RRU3959, see section "Installing
an RRU Alarm Cable" in "Installing RRU Cables" of RRU3959&RRU3959w Installation
Guide.
● For details about how to connect an alarm cable to an MEB, see section "Installing an
MEB Alarm Cable" in MEB06D User Guide.
● For details about how to connect a monitoring signal cable to an ICC100-N5, see the
description of ports 1 and 5 in section "Monitoring Board" of ICC100-N5 Solar Controller
User Manual.
ICC100-N5. The Com_N1 and Com_N2 ports are ports 1 and 5 shown in Figure
4-70.
Table 4-56 Monitoring board configurations in a DBS3900 (–48 V DC) that has
the BBU installed in a PMU cabinet
Cabi Cabi CN SRN SN Pow MC MS MP AD DC DC
net net er N RN N DR Volt Volt
Typ Sup age age
e ply Alar Alar
Syst m m
em Low Upp
Typ er er
e Thr Thr
esh esh
old old
0 17 1 BDU - - - - -
0 18 1 BDU - - - - -
0 18 2 BDU - - - - -
NOTE
● When configuring the BDU, you can specify the type of a device. If this parameter is set
to DEFAULT, the system does not check the BDU, HSU, and SDU types. If this parameter
is set to BDU, HSU, or SDU, the system checks whether the type of the BDU, HSU or
SDU in use is consistent with the configuration.
● When power cables are used for monitoring, the manager of the virtual PMU on the
SDU is the RRU connected to the SDU.
The following table describes the monitoring board configurations in this scenario.
Ca IFS 0 11 0 FMU 0 0 0 14 -
bin 59
et 06
0
BTS 0 8 0 TCU 0 15 0 7 - CM
390 UF
0AL
BTS 0 11 0 FM 0 15 1 14 - FAU
390 U
0AL
BTS 0 7 0 PM 0 15 2 3 - -
390 U
0AL
BTS 0 8 1 TCU 0 15 3 28 - HA
390 U0,
0AL opti
onal
BTS 0 8 2 TCU 0 15 3 29 - HA
390 U1,
0AL opti
onal
BTS 0 40 0 EM 0 15 3 2 - Opti
390 U onal
0AL
BTS 1 8 0 TCU 1 15 0 7 - CM
390 UF
0AL
BTS 1 11 0 FM 1 15 1 14 - FAU
390 U
0AL
BTS 1 8 1 TCU 1 15 3 28 - HA
390 U0,
0AL opti
onal
BTS 1 8 2 TCU 1 15 3 29 - HA
390 U1,
0AL opti
onal
BTS 0 8 0 TCU 0 15 0 7 - CM
390 UF
0AL
BTS 0 11 0 FM 0 15 1 14 - FAU
390 U
0AL
BTS 0 7 0 PM 0 15 2 3 - -
390 U
0AL
BTS 0 8 1 TCU 0 15 3 28 - HA
390 U0,
0AL opti
onal
BTS 0 8 2 TCU 0 15 3 29 - HA
390 U1,
0AL opti
onal
BTS 0 40 0 EM 0 15 3 2 - Opti
390 U onal
0AL
BTS 1 8 0 TCU 1 15 0 7 - CM
390 UF
0AL
BTS 1 11 0 FM 1 15 1 14 - FAU
390 U
0AL
BTS 1 8 1 TCU 1 15 3 28 - HA
390 U0,
0AL opti
onal
BTS 1 8 2 TCU 1 15 3 29 - HA
390 U1,
0AL opti
onal
BBC 9 8 0 TCU 9 15 0 7 - CM
UF
BBC 9 8 1 TCU 9 15 3 28 - HA
U0,
opti
onal
BBC 9 8 2 TCU 9 15 3 29 - HA
U1,
opti
onal
The following table describes the monitoring board configurations in this scenario.
BTS 0 8 0 TCU 0 15 0 7 - CM
390 UF
0AL
BTS 0 11 0 FM 0 15 1 14 - FAU
390 U
0AL
BTS 0 7 0 PM 0 15 2 3 - -
390 U
0AL
BTS 0 8 1 TCU 0 15 3 28 - HA
390 U0,
0AL opti
onal
BTS 0 8 2 TCU 0 15 3 29 - HA
390 U1,
0AL opti
onal
BTS 0 40 0 EM 0 15 3 2 - Opti
390 U onal
0AL
BTS 1 8 0 TCU 1 15 0 7 - CM
390 UF
0AL
BTS 1 11 0 FM 1 15 1 14 - FAU
390 U
0AL
BTS 1 8 1 TCU 1 15 3 28 - HA
390 U0,
0AL opti
onal
BTS 1 8 2 TCU 1 15 3 29 - HA
390 U1,
0AL opti
onal
BBC 9 8 0 TCU 9 15 0 7 - -
BBC 9 8 1 TCU 9 15 0 28 - HA
U0,
opti
onal
BBC 10 8 0 TCU 10 15 0 7 - -
BBC 10 8 1 TCU 10 15 0 28 - HA
U0,
opti
onal
The following table describes the monitoring board configurations in this scenario.
BTS BTS 0 11 0 FM 0 0 0 14 - FM
301 301 U UEA
2 2
(Ver. (Ver.
D_Z D_Z
) DC ) DC
0
BTS 0 40 0 EM 0 0 1 2 - Opti
301 U onal
2
(Ver.
D_Z
) DC
BTS BTS 1 11 0 FM 0 0 0 15 - FM
301 301 U UEA
2 2
(Ver. (Ver.
D_Z D_Z
) DC ) DC
1
The following table describes the monitoring board configurations in this scenario.
The following table describes the monitoring board configurations in this scenario.
BTS30 BTS 0 7 0 PM 0 0 0 3 - -
12AE 301 U
(Ver.D_ 2AE
Z) AC (Ver.
0 D_Z)
BTS 0 11 0 FM 0 0 1 14 - FAU
301 U
2AE
(Ver.
D_Z)
BTS 0 40 0 EM 0 0 0 2 - Option
301 U al
2AE
(Ver.
D_Z)
BTS30 BTS 1 7 0 PM 0 0 1 3 - -
12AE 301 U
(Ver.D_ 2AE
Z) AC (Ver.
1 D_Z)
BTS 1 11 0 FM 0 0 1 14 - FAU
301 U
2AE
(Ver.
D_Z)
The following figure shows the monitoring signal cable connections in two
BTS3012AE (Ver.D_Z) AC cabinets and two IBBS2.1/IBBS2.2 cabinets.
The following table describes the monitoring board configurations in this scenario.
BTS301 BTS 0 7 0 PM 0 0 0 3 - -
2AE 301 U
(Ver.D_ 2AE
Z) AC 0 (Ver
.D_Z
)
BTS 0 11 0 FM 0 0 1 14 - FAU
301 U
2AE
(Ver
.D_Z
)
BTS 0 40 0 EM 0 0 0 2 - Option
301 U al
2AE
(Ver
.D_Z
)
BTS301 BTS 1 7 0 PM 0 0 1 3 - -
2AE 301 U
(Ver.D_ 2AE
Z) AC 1 (Ver
.D_Z
)
BTS 1 11 0 FM 0 0 1 14 - FAU
301 U
2AE
(Ver
.D_Z
)
The following figure shows the monitoring signal cable connections in two
BTS3012AE (Ver.D_Z) DC cabinets.
The following table describes the monitoring board configurations in this scenario.
BTS30 0 40 0 EM 0 0 0 2 - Optional
12AE U
(Ver.D
_Z)
Z) BTS30 1 11 0 FM 0 0 1 14 - -
AC 12AE U
1 (Ver.D
_Z)
The following table describes the monitoring board configurations in this scenario.
NOTE
The following figure shows the connections of monitoring signal cables when the
OPM200 is configured and the BBU5900A is used for monitoring.
Figure 4-82 BBU5900A monitoring signal cable connection for the OPM200
NOTE
NOTE
If the output alarm port is configured, you do not need to add and bind the user-defined
alarms on the MAE.
----End
The following are MML command examples:
//Configuring an input alarm port with the parameters as follows: Cabinet No. is 0, Subrack No. (where the
EMU is located) is 40, Port No. is 0, Alarm ID is 65033, and Alarm Voltage is HIGH(High Voltage).
SET ALMPORT: CN=0, SRN=40, SN=0, PN=0, SW=ON, AID=65033, PT=BOOL, AVOL=HIGH;
//Configuring an output alarm port with the parameters as follows: Cabinet No. is 0, Subrack No. (where
the EMU is located) is 40, Port No. is 0, and Port Name is Water Alarm.
SET OUTPORT: CN=0, SRN=40, SN=0, PN=0, NAME="Water Alarm", SW=ON;
256521 Cabinet Temperature Set the upper limit of the cabinet temperature alarm
Unacceptable TUTHD 5°C lower than the ambient temperature or
set the lower limit TLTHD 5°C higher than the
ambient temperature, and wait more than 10s.
Set the preceding parameters only when the PMU is
configured. Select the configuration object of the
board to which the sensor is connected.
256722 Burglar Alarm Open the cabinet door and wait more than 10s.
256543 Battery Temperature In a high temperature scenario: Set the upper limit of
Unacceptable the battery temperature alarm TUTHD lower than the
ambient temperature or set the ambient temperature
higher than the upper limit, and wait more than 2s.
In a low temperature scenario: Set the lower limit of
the battery temperature alarm TLTHD higher than the
ambient temperature or set the ambient temperature
lower than the lower limit, and wait more than 2s.
Set the preceding parameters only when batteries are
configured. For details, see Power Supply
Management.
256504 Ambient Temperature In a high temperature scenario: Set the upper limit of
Unacceptable the ambient temperature alarm TUTHD lower than
the ambient temperature or set the ambient
temperature higher than the upper limit, and wait
more than 2s.
In a low temperature scenario: Set the lower limit of
the ambient temperature alarm TLTHD higher than
the ambient temperature or set the ambient
temperature lower than the lower limit, and wait
more than 2s.
Set the preceding parameters only when the EMU is
configured.
25651 Ambient Humidity In a high humidity scenario: Set the upper limit of the
Unacceptable ambient humidity alarm HUTHD lower than the
ambient humidity or set the ambient humidity higher
than the upper limit, and wait more than 2s.
In a low humidity scenario: Set the lower limit of the
ambient humidity alarm HLTHD higher than the
ambient humidity or set the ambient humidity lower
than the lower limit, and wait more than 2s.
Set the preceding parameters only when the EMU is
configured.
25653 Cabinet Humidity Set the upper limit of the cabinet humidity alarm
Unacceptable HUTHD 10% RH lower than the cabinet humidity or
set the lower limit of HLTHD 10% RH higher than the
cabinet humidity, and wait more than 10s.
Set the preceding parameters only when the EMU is
configured.
257415 GDU Temperature This alarm is reported when the temperature of the
Abnormal GDU+SLPA is beyond the normal range. This alarm is
cleared when the device temperature stays within the
normal range for 3 minutes.
257425 GDU Signal Output Perform either of the following operations. If an alarm
Abnormal is reported, the data is properly configured.
● Remove the feeder between the GDU+SLPA and
the GDU and keep the faulty state for 180s (by
default) or longer.
● Remove all the feeders between the GDU and the
BBU and keep the faulty state for 180s (by default)
or longer.
NOTE
1. This alarm is reported only when the temperature sensor is configured by default or is
installed in the cabinet by operators themselves.
The temperature sensor is not configured by default in the BTS3900, BTS3900L, or
BTS3900C cabinet.
The temperature sensor is configured by default in the BTS3900A (with RFC), DBS3900
(with RFC), and BTS3900AL cabinets.
2. This alarm is reported only when the door status sensor is configured by default or is
installed in the cabinet by operators themselves.
The door status sensor is not configured by default in the BTS3900, BTS3900L, and
DBS3900 (with the IMB) cabinets.
The door status sensor is configured by default in the BTS3900A, DBS3900 (with the
APM30H, TMC, or TP48600A), and BTS3900AL cabinets.
3. This alarm is reported only when batteries are configured in the cabinet.
4. This alarm is reported only when the EMU is configured.
5. This alarm is reported only when the GDU is configured.
----End
4.4.6 Reconfiguration
When reconfiguring parameters for monitoring devices, collect information about
parameters to be reconfigured based on onsite hardware configuration and
environment monitoring requirements. For details, see 4.4.3.1.1 MO Setting
Notes.
Run the MOD PMU command to reconfigure PMU parameters.
Run the MOD FMU command to reconfigure FMU parameters.
Run the MOD TCU command to reconfigure TCU parameters.
Run the MOD CCU command to reconfigure CCU parameters.
Run the MOD EMU command to reconfigure EMU parameters.
Run the MOD MEB command to reconfigure MEB parameters.
Run the MOD GDU command to reconfigure GDU parameters.
4.5.2 Precautions
Single-side configuration is recommended for monitoring devices in a multimode
base station. The monitoring devices can also be configured in dual-side
configuration mode. For details about the dual-side configuration, see section "4.6
Operation and Maintenance (Multimode Base Station)".
Cabinet No. BTSFMUABP.CN If the number of the RFC housing the FMU is 1, set
this parameter to 1.
Subrack No. BTSFMUABP.SRN This parameter specifies the number of the subrack
housing the FMU. Set this parameter to 11 or 12.
Slot No. BTSFMUABP.SN This parameter specifies the number of the slot
housing the FMU. Set this parameter to the default
value 0.
Special Alarm BTSFMUABP.SPECIALSW This parameter specifies the level specifications for
Valid Level ITCHERLEVEL the dedicated Boolean alarm. There are two
Configuration specifications: high-level and low-level alarms.
It is recommended that the dedicated Boolean
alarm function be disabled on the FMU. If all
sensors in the SBAF parameter are disabled, you do
not need to configure this parameter.
Manager Port BTSFMUABP.MPN This parameter specifies the number of the serial
No. port on the manager to which the board is
connected.
If the FMU is connected to the BBU:
● UPEU/UEIU (MON1): 1
● UPEU/UEIU (MON0): 0
If the FMU is connected to the CCU, it must be
connected to port D_COM1. Set this parameter
to 1.
FMU Board BTSFMUABP.FMUTYPE This parameter specifies the FMUA board type.
Type ● Set this parameter to OUTDOOR when the
board is installed in an outdoor cabinet.
● Set this parameter to INDOOR when the board is
installed in an indoor cabinet.
Cabinet No. BTSDHEUBP.CN This parameter specifies the number of the cabinet
housing the TCU.
If the number of the TMC housing the TCU is 1, set
this parameter to 1.
Subrack No. BTSDHEUBP.SRN This parameter specifies the number of the subrack
housing the TCU. Set this parameter to 8 or 14.
Slot No. BTSDHEUBP.SN This parameter specifies the number of the slot
housing the TCU. Value range: 0 to 3
If the TCU is installed in the BTS3900AL AC,
BTS3900AL DC, IBBS700D, or IBBS700T cabinet, set
this parameter as follows:
● Set the slot number of the CMUF/CMUEA to 0.
● Set the slot number of HAU0 to 1.
● Set the slot number of HAU1 to 2.
If the TCU is installed in the TP48600A cabinet,
set this parameter as follows:
● Set the slot number of the CMUF for cabinet
temperature control to 0.
● Set the slot number of the CMUF for battery
cabinet temperature control to 1.
● Set the slot number of HAU0 to 2.
● Set the slot number of HAU1 to 3.
If the TCU is installed in other cabinets, set this
parameter to 0.
Manager Port BTSDHEUBP.MPN This parameter specifies the number of the serial
No. port on the manager to which the board is
connected.
If the TCU is connected to the BBU:
● UPEU/UEIU (MON1): 1
● UPEU/UEIU (MON0): 0
If the TCU is connected to the CCU:
● The CMUF must be connected to port D_COM0
on the CCU. In this case, set this parameter to 0.
● The FAU0 or FAU1 must be connected to port
D_COM3 on the CCU. In this case, set this
parameter to 3.
If the module is connected to the RRU, set this
parameter to 0.
Cabinet No. BTSCCUBP.CN This parameter specifies the number of the cabinet
housing the CCU.
If the number of the BTS3900AL cabinet housing
the CCU is 0, set this parameter to 0.
Subrack No. BTSCCUBP.SRN This parameter specifies the number of the subrack
housing the CCU. Set this parameter to the default
value 15.
Slot No. BTSCCUBP.SN This parameter specifies the number of the slot
housing the CCU. Set this parameter to the default
value 0.
Manager Port BTSCCUBP.MPN This parameter specifies the number of the serial
No. port on the manager to which the board is
connected.
The CCU must be connected to port MON0 on the
BBU. In this case, this parameter must be set to 0.
The CCU must be connected to port EXT_ALM on
the RRU. In this case, this parameter must be set to
0.
Slot No. BTSDATUBP.SN This parameter specifies the number of the slot
housing the GATM. Set this parameter to the
default value 0.
ANT0 Alarm BTSDATUBP.MODE0 to This parameter specifies the mode for reporting
Mode to ANT5 BTSDATUBP.MODE5 the feeding current alarms of TMAs of branches 0
Alarm Mode through 5. When the feeding current exceeds the
threshold, an alarm is reported.
Value range: MODE1, MODE2, and MODE3
● MODE1: Only critical alarms are reported.
● MODE2: Warning and critical alarms are
reported. In this mode, both warning and
critical alarms are reported as fixed-value
current.
● MODE3: Warning and critical alarms are
reported. In this mode, warning alarms are
reported as periodic pulse current, and critical
alarms are reported as fixed-value current.
Periodic pulse current is reported when the
alarm reporting requirement is met within a
preset period. Compared with fixed-value
current, periodic pulse current is easily
reported.
The value MODE1 is recommended.
ANT0 ALD Over BTSDATUBP.MAJORALMU These parameters specify the thresholds for
Critical Alarm P0 to reporting the critical alarms related to the feeding
Threshold(mA) BTSDATUBP.MAJORALMU current of the TMA. When the feeding current of
to ANT5 ALD P5 the TMA onsite exceeds the threshold, ALM-28002
Over Critical GATM ALD Current Out of Range is reported.
Alarm
Threshold(mA)
ANT0 ALD Over BTSDATUBP.MINORALMU These parameters specify the thresholds for
Warning Alarm P0 to reporting the warning alarms related to the
Threshold(mA) BTSDATUBP.MINORALMU feeding current of the TMA. When the feeding
to ANT5 ALD P5 current of the TMA onsite exceeds the threshold,
Over Warning ALM-28002 GATM ALD Current Out of Range is
Alarm reported.
Threshold(mA)
ANT0 ALD Low BTSDATUBP.ALMD0 to These parameters specify the thresholds for
Current Alarm BTSDATUBP.ALMD5 reporting the warning alarms related to the
Threshold(mA) feeding current of the TMA. When the feeding
to ANT5 ALD current of the TMA onsite is less than the
Low Current threshold, ALM-28002 GATM ALD Current Out of
Alarm Range is reported.
Threshold(mA)
Manager Port BTSDATUBP.MPN This parameter specifies the number of the serial
No. port on the manager to which the board is
connected.
If the GATM is connected to the BBU:
● GATM0 is connected to MON0 on the UPEU.
Set this parameter to 0.
● GATM1 is connected to MON1 on the UPEU.
Set this parameter to 1.
If the GATM is connected to CCU:
● The GATM0 must be connected to port
D_COM5 on the CCU. In this case, set this
parameter to 5.
● The GATM1 must be connected to port
D_COM6 on the CCU. In this case, set this
parameter to 6.
Step 1 Prepare EMU/MEB configuration data. Before data preparation, check whether the
EMU/MEB needs to be configured by referring to Table 4-20 and Table 4-21. If
the EMU/MEB is required, prepare configuration data by referring to the following
table. Otherwise, skip this step.
Step 2 Prepare configuration data of the alarm signal input and output ports based on
the input and output requirements of customized alarms.
----End
● Prepare the configuration data for the ALMPORT MO by referring to Table
4-75.
● Prepare the configuration data for the OUTPORT MO by referring to Table
4-76.
Slot No. BTSDEMUBP.SN This parameter specifies the number of the slot
housing the EMU. Set this parameter to the
default value.
Manager Port BTSDEMUBP.MPN This parameter specifies the number of the serial
No. port on the manager to which the board is
connected.
If the EMU is connected to the BBU:
● UPEU/UEIU (MON1): 1
● UPEU/UEIU (MON0): 0
If the EMU is connected to the CCU, it must be
connected to port D_COM3. Set this parameter
to 3.
If the module is connected to the RRU, set this
parameter to 0.
Port No. ALMPORT.PN This parameter specifies the number of the alarm
port on each monitoring board as follows:
UPEU/UEIU: 0 to 7 (for Boolean alarms)
RRU: 0 to 3 (for Boolean alarms)
EMU/EMUB: 0 to 31 (for Boolean alarms)
EMU/EMUB: 32 to 35 (for analog alarms)
BBU3910A: 0 to 5 (for Boolean alarms)
Switch ALMPORT.SW Turn on this switch for the port configured with a
customized alarm. This parameter specifies the
state of the port switch and can be set as follows:
OFF(Off): indicates that the port is disabled and
alarms cannot be detected. This is the default
value for this parameter.
ON(On): indicates that the port is enabled and
alarms can be reported through the port
according to the customized alarm IDs. In
addition, the alarm voltage level (specified by the
AVOL parameter) for Boolean alarms or the
threshold for alarm generation can be set.
Upper Limit ALMPORT.UL This parameter specifies the alarm upper limit. If
the environment measurement value is greater
than the alarm upper limit of the sensor, an
alarm is reported.
Environment measurement value = Measurement
lower limit + (Measurement upper limit -
Measurement lower limit) x (Observed current or
voltage - Output lower limit)/(Output upper limit
- Output lower limit).
UL must be less than or equal to SMUL and
greater than LL.
Lower Limit ALMPORT.LL This parameter specifies the alarm lower limit. If
the environment measurement value is below the
alarm lower limit of the sensor, the alarm is
reported.
Environment measurement value = Measurement
lower limit + (Measurement upper limit -
Measurement lower limit) x (Observed current or
voltage - Output lower limit)/(Output upper limit
- Output lower limit).
LL must be greater than or equal to SMLL and
less than UL.
Sensor Type BTSENVALMPORT.ST This parameter specifies the type of a sensor. Set
this parameter to VOLTAGE or CURRENT based
on the external sensor specifications.
NOTE
If devices to be monitored connect to an MEB, the manager of the boards is the RRU which
also connects to the MEB.
Slot No. BTSDEMUBP.SN This parameter specifies the number of the slot
housing the MEB.
Manager Cabinet BTSDEMUBP.MCN The manager is the RRU which connects to the
No. board using a power cable. Set this parameter
to the cabinet number of the manager.
Manager Subrack BTSDEMUBP.MSRN The manager is the RRU which connects to the
No. board using a power cable. Set this parameter
to the subrack number of the manager.
Before configuring the PMU, FMU, TCU, or CCU, run the ADD CABINET command to
configure the cabinet where the PMU, FMU, TCU, or CCU is located if the cabinet is not
configured.
----End
----End
----End
----End
Step 2 Run the following commands to query the status of the input and output alarm
ports:
● Run the LST BTSENVALMPORT command to query the status of the input
alarm port.
● Run the LST BTSOUTPUT command to query the status of the output alarm
port.
Step 3 Based on the query results, run the following commands to enable the input
alarm port and disable the unused alarm port:
● Run the SET BTSENVALMPORT command to set the input alarm port.
● Run the SET BTSOUTPUT command to set the output alarm port.
Step 4 Add and bind the customized alarms on the base station to the MAE so that the
alarms can be identified and reported.
Log in to the MAE. Choose Monitor > Alarms > NE Alarm Settings from the
main menu. In the navigation tree on the left, choose User-Defined Alarm to add
configurations, bind the alarms, and modify the alarm severity. For details, see
"Operation and Maintenance > Fault Management > Alarms > Configuring Alarms
or Events > Precise Monitoring > Defining an NE Alarm" in the MAE product
documentation.
NOTE
If the output alarm port is configured, you do not need to add and bind the user-defined
alarms on the MAE.
----End
----End
NOTE
Single-side configuration has been supported since SRAN6.0. Versions earlier than SRAN6.0
support only dual-side configuration. RRU remote monitoring supports single-side
configuration only.
● The monitoring devices of the same base station must be configured on the
same RAT.
● The configuration must be consistent with actual cable connections. If a
monitoring device connects to a BBU, the monitoring device must be
configured on one RAT of the BBU.
● For a separate-MPT dual-mode base station, the monitoring devices are
configured in the following priority order: GBTS/eGBTS > NodeB > eNodeB
(FDD) > eNodeB (TDD) > gNodeB.
For example, assume that a UO+LO BTS3900A has the following
configurations: 2 APM30Hs+2 RFCs+2 IBBS200Ds/IBBS200Ts. In this example,
the monitoring devices of the BTS3900A should be configured on the NodeB.
● For a separate-MPT triple-mode base station, the monitoring devices should
be configured according to the monitoring signal cable connections in the
cabinet. If the monitoring signal cables are connected to the dual-mode BBU,
configure the monitoring devices in the following priority order: GBTS/eGBTS
> NodeB > eNodeB (FDD) > eNodeB (TDD) > gNodeB.
For example, as shown in the following figure, a separate-MPT GU+LO
BTS3900A has the following configurations: 2 APM30Hs+2 RFCs+2 IBBS200Ds/
IBBS200Ts. APM30H 0 and RFC 0 house GU devices (BBUs and RFUs), and
APM30H 1 and RFC 1 house LTE devices. The monitoring devices and their
cascaded monitoring devices of APM30H 1 are connected to APM30H 0. The
BBU in APM30H 0 performs monitoring management. In this example, the
monitoring devices should be configured on the GSM base station.
NOTICE
The HPMI board is configured in the APM30H (Ver.C), but is not configured in
the APM30H (Ver.D). Therefore, the monitoring signal cable connections
between the PMU and the HPMI do not need to be considered for the
APM30H (Ver.D).
● For a co-MPT multimode base station, the monitoring devices are configured
in the following priority order: GBTS/eGBTS > NodeB > eNodeB (FDD) >
eNodeB (TDD) > gNodeB.
For example, a co-MPT GUL BTS3900A (BBUs and RFUs) has the following
configurations: 1 APM30H+1 RFC+1 IBBS200D/IBBS200T. In this example, the
monitoring devices of the BTS3900A are configured on the GSM base station.
● In the evolution scenario, it is recommended that new monitoring devices be
configured on an existing RAT before the evolution to prevent reconstruction
on legacy devices. If the RAT existing before the evolution cannot be selected,
configure the monitoring devices in the following priority order: GBTS/eGBTS
> NodeB > eNodeB (FDD) > eNodeB (TDD) > gNodeB. Then, reconstruct
legacy devices.
For example, if a GBTS (BTS3900) has evolved into a GU dual-mode base
station, configure the monitoring devices of the evolved base station on the
GSM mode.
● In the RRU remote monitoring scenario, configure the monitoring devices of
the single-mode RRU on the RAT of the RRU. It is recommended that you
configure the monitoring devices of the GU, GL, or UL dual-mode RRU in the
following priority order: GBTS/eGBTS > NodeB > eNodeB (FDD) > eNodeB
(TDD) > gNodeB.
● In the RRU remote monitoring scenario, a BDU or SDU supporting the virtual
PMU in the voltage boosting power distribution subrack EPU02B/EPU02S-02/
EPU02S can only be configured as the PMU for one RRU.
Table 4-78 Common GSM parameters of the multimode base stations (1)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-79 Common GSM parameters of the multimode base stations (2)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-80 Common GSM parameters of the multimode base stations (3)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-81 Common UMTS, LTE, and NR parameters of the multimode base stations (4)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-82 Common UMTS, LTE, and NR parameters of the multimode base stations (5)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-83 Common UMTS, LTE, and NR parameters of the multimode base stations (6)
Object Parameter Parameter ID MML Command Setting Notes
Name
NOTICE
The HPMI board is configured in the APM30H (Ver.C), but is not configured in
the APM30H (Ver.D). Therefore, the monitoring signal cable connections
between the PMU and the HPMI do not need to be considered for the
APM30H (Ver.D).
● For a co-MPT multimode base station, the monitoring devices are configured
in the following priority order: GBTS/eGBTS > NodeB > eNodeB (FDD) >
eNodeB (TDD) > gNodeB.
For example, a co-MPT GUL BTS3900A (BBUs and RFUs) has the following
configurations: 1 APM30H+1 RFC+1 IBBS200D/IBBS200T. In this example, the
monitoring devices of the BTS3900A are configured on the GSM base station.
● In the evolution scenario, it is recommended that new monitoring devices be
configured on an existing RAT before the evolution to prevent reconstruction
on legacy devices. If the RAT existing before the evolution cannot be selected,
configure the monitoring devices in the following priority order: GBTS/eGBTS
> NodeB > eNodeB (FDD) > eNodeB (TDD) > gNodeB. Then, reconstruct
legacy devices.
For example, if a GBTS (BTS3900) has evolved into a GU dual-mode base
station, configure the monitoring devices of the evolved base station on the
GSM mode.
● In the RRU remote monitoring scenario, configure the monitoring devices of
the single-mode RRU on the RAT of the RRU. It is recommended that you
configure the monitoring devices of the GU, GL, or UL dual-mode RRU in the
following priority order: GBTS/eGBTS > NodeB > eNodeB (FDD) > eNodeB
(TDD) > gNodeB.
● In the RRU remote monitoring scenario, a BDU or SDU supporting the virtual
PMU in the voltage boosting power distribution subrack EPU02B/EPU02S-02/
EPU02S can only be configured as the PMU for one RRU.
Table 4-84 Common GSM parameters of the multimode base stations (1)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-85 Common GSM parameters of the multimode base stations (2)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-86 Common GSM parameters of the multimode base stations (3)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-87 Common UMTS, LTE, and NR parameters of the multimode base stations (4)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-88 Common UMTS, LTE, and NR parameters of the multimode base stations (5)
Object Parameter Parameter ID MML Command Setting Notes
Name
Table 4-89 Common UMTS, LTE, and NR parameters of the multimode base stations (6)
Object Parameter Parameter ID MML Command Setting Notes
Name
5 Parameters
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
----End
7 Glossary
8 Reference Documents