IManager M2000 V200R012 Optional Feature Description (EWBB2.1) V1.1 (20120606)

iManager M2000 V200R012
Optional Feature Description(eWBB2.1)
Issue
02
Date
2012-06-01
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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 commercial contract made between
Huawei and the customer. All or partial products, services and features described in this document may not
be within the purchased scope or the usage scope. Unless otherwise agreed by 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.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com

Optional Feature Description
Contents
1 Overview......................................................................................................................................... 2
2 Optional Features (WOFD-900000) ............................................................................................ 3
2.1 Security Management ....................................................................................................................................... 3
2.2 Hardware and Software Management .............................................................................................................. 6
2.3 Fault Management ............................................................................................................................................ 9
2.4 Network Monitoring and Analysis ................................................................................................................. 10
2.5 Base Station Power Saving Management ....................................................................................................... 13
2.6 OSS Solution .................................................................................................................................................. 15
2.7 Intelligent Development Platform .................................................................................................................. 16
2.8 Wireless Bearer Network Management .......................................................................................................... 19
3 Acronyms and Abbreviations ................................................................................................... 21
Issue 02 (2012-04-12)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

Overview
This document describes the optional features provided by Huawei M2000 V200R012. This
document helps users understand the M2000 features.
The network elements (NEs) in this document refer to the network devices managed by the
M2000. The M2000 manages eWBB based on Long Term Evolution (LTE).
The M2000 manages the following eRAN NEs:
Base station: eNodeB, including DBS3900 LTE
Clock server: IP Clock Server
The M2000 manages the following evolved packet core (EPC) NEs:
Enterprise core network system: eCNS
Issue 02 (2012-04-12)


Optional Features (WOFD-900000)
2.1 Security Management

WOFD-210100 Encrypted Transmission
Availability
This feature was introduced in M2000 V200R005.
Summary
The M2000 uses encryption algorithms such as Secure Sockets Layer (SSL), FTP over SSL
(FTPS), and SSH FTP (SFTP) to ensure communication security between the M2000 and
network entities. Encrypted transmission for the M2000 involves transmission encryption and
certificate management.
Transmission encryption can be performed between the M2000 client and server, between the
M2000 server and NEs. Control channels and data transmission channels based on SSL, FTPS,
SFTP, or Hypertext Transfer Protocol Secure (HTTPS) are established before network entities
communicate with each other. This ensures transmission security.
To ensure data integrity and non-repudiation during communications, authentication based on
digital certificates is performed for involved parties. The M2000 provides the digital
certificate management function. M2000 can centrally manage certificates on the entire
network based on Certificate Management Protocol (CMP) V2. Currently, this function
applies to the M2000, eNodeB.
Benefits
This feature brings about the following benefits:
This feature guarantees the confidentiality of data transmitted through TCP and
effectively protects the privacy of user data.
The certificate authentication mode prevents untrustworthy connections. This ensures the
validity of SSL connections and further enhances transmission security.
Users can easily manage the digital certificates of the M2000 and devices, for example,
they can sign or revoke a certificate.
Issue 02 (2012-04-12)


Users can centrally manage the digital certificates of devices and the M2000, including
applying for certificates, activating certificates, and updating the certificate revocation
lists (CRLs).
Description
Transmission encryption:
Generally, Transmission Control Protocol (TCP) is used for communications between the
M2000 client and server, between the M2000 server and NEs. After SSL-based encrypted
transmission is used, an SSL-based encrypted data transmission channel, rather than a normal
TCP connection, is established between communication parties. Supported SSL protocol
versions are SSL 3.0, TLS 1.0, and TLS 1.2. This feature uses certificates for unidirectional
and bidirectional authentication between the M2000 and NEs. This ensures access validity.
In many scenarios, data is transmitted in files between network entities. For example:
The M2000 obtains performance, log, and configuration files from NEs.
The M2000 delivers performance and configuration files to third-party systems.
NEs download version and patch files from the M2000.
FTP uses plain text for data transmission in bearer networks, where files are exposed to
interception. To address this problem, this feature provides secure file transfer based on FTPS
and SFTP.
Security levels of network entities are determined by their roles and positions in the
communications network.
The M2000 provides different encrypted data transmission solutions in the following
scenarios:
Between the M2000 client and server: SSL, SFTP, and HTTPS
Between the M2000 server and NEs: SSL and FTPS
The M2000 supports both encrypted and unencrypted transmission modes. This feature allows
users to select data transmission solutions for the M2000 and NEs. Users can check in real
time whether the links between NEs and the M2000 use SSL connections. Users can also
manually change the status of these SSL connections, if necessary.
This feature will decrease the M2000's management capability because complex SSL
encryption algorithms occupy a large number of system resources and affect data transmission
efficiency.
Digital certificate management:
Supporting CMP V2
To comply with 3GPP specifications, the M2000 supports CMP V2. Using CMP V2, the
M2000 can establish an HTTP/HTTPS-based channel for managing digital certificates
with a Certificate Authority (CA). If NEs cannot directly communicate with the CA, the
M2000 can provide agent services for NEs. Agent services allow users to apply for and
update certificates.
Managing CA information
A CA is an entity that issues digital certificates. Users can set CA information on the
M2000, including IP address, uniform resource locator (URL), protocol, and port. Based
on the information, the M2000 sets up a connection with the CA to apply for or update
device certificates.
Issue 02 (2012-04-12)


Managing certificates
The M2000 supports PEM and DER certificate formats defined in the ITU-T X.509v3
standard. The M2000 can manage device certificates, trusted certificates, and CRLs and
provides differentiated management functions for these certificates.
A device certificate is a file containing public keys and ownership information. This
certificate is digitally signed and issued by the CA and is used for authenticating parities
involved in communications.
When communicating properly with the CA, the M2000 provides one-stop automatic
services for applying for device certificates, including creating an application form,
applying for device certificates, and delivering the certificates to devices.
If the M2000 cannot communicate with the CA, users can manually apply for a device
certificate. The procedure is as follows: Users fill in a certificate application form on the
M2000 and the M2000 accordingly generates an application file; users submit the
application file to the CA and the CA signs the certificate; users then import the signed
certificate to the M2000 and deliver it to devices.
The M2000 allows users to view, activate, delete, and test device certificates and import
them in batches. The M2000 reports an alarm when a device certificate is about to expire,
fails to be loaded, has expired, or becomes invalid. This prevents service interruption due
to exceptions that occur on the certificate.
A trusted certificate can be a CA certificate or a certificate chain and it is used for
authenticating the validity of the peer certificate. The M2000 allows users to view,
import, and delete trusted certificates.
A CRL is a list for the CA to record revoked digital certificates. On the M2000, users
configure parameters for NEs to automatically obtain a CRL. The parameters include the
IP address, access port, and user name of the CA, and the save path and execution mode
of the CRL. The M2000 then delivers these parameters to NEs and NEs obtain the CRL
based on the user configuration. If NEs cannot obtain a CRL from the CA, users can
manually import the CRL to NEs on the M2000. If a digital certificate used for
SSL-based data communication between NEs is on the CRL, the communication fails.
Enhancement
The following function is added to M2000 V200R012C00:
The M2000 supports the SSL protocol version TLS 1.2.
The M2000 generates an alarm when a device certificate fails to be loaded, has expired,
or becomes invalid.
The following function is added to M2000 V200R010:
A digital certificate channel based on CMP V2 is provided between the M2000 and a CA
system.
The following function is added to M2000 V200R009:
Managing SSL connection status and eNodeB digital certificates
The following functions are added to M2000 V200R008:
SSL encrypted transmission between the M2000 client and the M2000 server
SSL encrypted transmission between the M2000 server and NEs
SSL encrypted transmission between the M2000 server and NEs based on authentication
mode
SFTP encrypted file transfer on the northbound file interface
Issue 02 (2012-04-12)


Dependency
Encrypted transmission applies to eRAN1.1 and later versions.
Digital certificate management applies to eNodeBs in eRAN1.1 and later versions.
2.2 Hardware and Software Management

WOFD-160100 Inventory Management
Availability
Summary
This feature allows the M2000 to centrally manage physical and logical asset information
about network devices.
Benefits
The M2000 assists operators in understanding the physical and logical asset information about
the existing network devices, such as NE versions and hardware service expiry data. The
information acts as a reference for allocating and changing resources.
It provides accurate reference data in scenarios such as troubleshooting, system upgrade, and
system expansion.
Description
The system allows users to browse, query, maintain, synchronize, import, and export
inventory data.
Browsing inventory data

Inventory data is categorized into logical inventory data and physical inventory data.
Logical inventory data includes cell data and NE versions.
Physical inventory data includes information about racks, subracks, slots, boards,
antennas, and ports. Physical inventory properties include the device name, device type,
device version, electronic label, device manufacturer, serial number, and delivery date.
Inventory data varies according to NEs.
The inventory management module can manage the inventory data of the M2000.
Logical inventory data includes the version information about M2000 software, accessed
NEs, operating systems, and databases. Physical inventory data varies slightly according
to platforms.
This feature allows users to query inventory data on the live network. The hierarchy
between objects in the inventory data is displayed in a navigation tree, and object
properties are displayed on a list. In addition, inventory data can be queried through filter
or search criteria. Query results can be displayed on a list and saved in a TXT, XML, or
CSV file.
Issue 02 (2012-04-12)


The M2000 allows users to query the electronic label of base stations boards even when
the boards are offline.
Synchronizing inventory data

The M2000 provides the function of synchronizing inventory data so that the inventory
information on NEs is synchronized with that stored on the M2000 database. The M2000
supports manual and automatic synchronization. Synchronization operations are
performed as a task. Manual synchronization is performed by users on the basis of actual
requirements. Automatic synchronization is triggered by preset parameters in centralized
tasks (WOFD-071200).
Users can set task parameters such as task start time, execution period, and NEs. Users
can also view the execution progress and status of the task.
Automatic notification of inventory data change

After the inventory data of an NE is changed, the NE automatically notifies the M2000
of the change. This ensures that the inventory data on the M2000 is consistent with that
on the NE. Currently, only eNodeBs support this function.
Exporting inventory data

The M2000 allows users to export the inventory data of a single NE or MO.
Users can export the inventory data about NEs or MOs to the M2000 client. Inventory
data about an NE or multiple MOs can be exported as a TXT, XML, or CSV file, while
inventory data about a single MO can be exported as an XML or CSV file.
Importing information about outsourcing parts

The information about outsourcing parts can be collected by importing files. Users can
import inventory information about NEs by importing files in XML format, and
inventory information about MOCs by importing files in CSV or XML format. The
objects that support this function are subrack, cabinet, board, slot, port, antenna, and
software.
Maintaining inventory data

Users can change certain inventory data such as the user ID and end of service (EOS)
date. The results are saved in the M2000 database.
Enhancement
The following functions are added to M2000 V200R011C00:
Saving query results in TXT, XML, or CSV filesAutomatic notification of eNodeB

inventory data change
Querying the electronic label information of offline boards in LTE base stations
Importing information about outsourcing parts
Supporting the inventory management of the eNodeB
Dependency
None
Issue 02 (2012-04-12)


WOFD-280800 Antenna Management System LTE

Availability
This feature is introduced in M2000 V200R012C00.
Summary
The centralized ALD management feature provides a GUI that is based on the B/S
architecture. Using this GUI, users can perform centralized operation and maintenance on
eNodeB ALDs. This GUI accesses the server using HTTPS, ensuring data transmission
security.
Benefits
Telecom operators can remotely and centrally maintain ALDs, without operating the
ALDs on the NE side. This reduces maintenance costs for telecom operators.
A user-friendly GUI is provided, which simplifies operations. This helps users focus on
important maintenance work and significantly improves maintenance efficiency.
This feature allows users to add, adjust, and upgrade ALDs in batches. This requires less
maintenance workforce and reduces manual errors.
This feature is based on the B/S structure. Therefore, users can manage ALDs through a
web browser without installing the client software.
Description
The M2000 displays the NE topology view of the antenna management feature based on the
hierarchal structure of NEs. Before managing ALDs, users can select multiple eNodeBs from
the NE topology view and perform batch operations on ALDs, such as power supply
management, configuration management, software management, and log management. This
improves maintenance efficiency.
The antenna management system provides the following functions:
ALD power supply management

Users can query the states of ALD power supply switches and the alarm thresholds of the
current. Users can also set the states of ALD power supply switches and the alarm
thresholds of the current in batches on the GUI, or set the information in a file and
import the file to the M2000 to implement batch settings.
Users can customize the types of non-standard ALD power supply systems.
ALD configuration management

Users can manage ALDs and ALD parameters, such as querying, scanning, adding,
modifying, and deleting ALDs and ALD parameters.
The ALDs that can be managed include Remote Electrical Tilts (RETs) and Smart Tower
Mounted Amplifiers (STMAs). The configuration management functions provided by
each type of ALD are as follows:
RET: querying parameter information, calibrating the tilt, setting the tilt, resetting the
RET, and downloading configuration data.
STMA: querying parameter information, and setting gains and working modes.
Issue 02 (2012-04-12)


Users can add ALDs or modify the parameters of RETs and STMAs in batches in an
XLS or XML file and import the file to the M2000 to implement batch addition or
modification.
In addition, the M2000 allows users to export the configuration data of ALDs to an XML
or XLS file. The exported configuration data includes the supplier code, serial number
(SN), and software and hardware version information. The configuration data helps users
collect inventory data about ALDs on the live network.
ALD software management

Users can check the current software versions of ALDs and upgrade ALD software in
batches.
ALD log management

Users can manage NE operation logs for ALDs. NE operation logs record the
ALD-related MML commands that have been executed on eNodeBs. Users can query,
sort, and search for these logs and export them to an XLS or XML file.
ALD alarm management

Users can view the details about alarms related to ALDs managed by the M2000 and
acknowledge or clear the alarms.
Enhancement
None
Dependency
None
2.3 Fault Management

WOFD-120100 Alarm Remote Notification
Availability
Summary
The M2000 automatically notifies related O&M personnel of the alarms that meet the preset
conditions using SMSs or emails.
Benefits
By sending information about major network faults to related maintenance personnel, this
feature allows the maintenance personnel to remotely monitor the running status of the
network in real time. As a result, telecommunications rooms can be left unattended.
Description
The M2000 sends alarm notifications using SMSs or emails. The M2000 allows users to set
alarm notification conditions such as alarm severities, types, names, and sources. It also
Issue 02 (2012-04-12)


allows users to set different time for sending alarm notifications. For example, users can
select a specific time segment during a workday to send the notifications.
For details about alarm sources in the filter criteria, see the feature WOFD-010300 Alarm Viewer.
If the M2000 sends alarm notifications using SMSs, the short message center (SMC) or the
short message modem of GSM, CDMA or WCDMA data card modem needs to be configured.
When configuring the short message modem, users can set the short message modem
communication parameters and specify mobile numbers on the GUI. When configuring the
message gateway, users can set the parameters such as the host address, port number, user
name, password, and coding protocol on the GUI.
If the M2000 sends alarm notifications using emails, a mail server is required. Users can set
the mail server and the communication parameters of emails on the M2000 GUI.
The M2000 allows users to set the maximum size of information that can be received by a
mailbox or the maximum number of SMSs that can be received within a certain period to
prevent the errors when large-size data and many short messages are sent within a certain
period. The alarm data and the number of SMSs that exceed the thresholds are discarded. The
time unit can be minute or hour.
Enhancement
Sending SMSs about alarm information through the WCDMA data card modem.
The alarm traffic control function in remote alarm notification mode.
Dependency
None
2.4 Network Monitoring and Analysis

WOFD-190100 Real-Time Performance Monitoring
Availability
Summary
This feature implements the collection, display, and analysis of KPIs in quasi-real time. By
using this function, users can view the analysis results in multiple graphical modes.
Benefits
This feature provides multiple graphical display modes, enabling users to directly view the
dynamic changes of KPIs.
Issue 02 (2012-04-12)

10

This feature displays the running status of the network in time through correlation data
analysis, threshold alarms, and threshold messages, providing a shortcut for routine network
maintenance and problem localization.
Description
This feature implements the real-time collection and analysis of KPIs in task mode. Users can
start a monitoring task, select an object to be monitored, and set parameters such as the object
class, monitoring type, and monitoring counters. The M2000 allows users to quickly search
for objects by entering keywords. By default, the M2000 monitors the common KPIs. By
default, the M2000 monitors commonly used KPIs.
The M2000 provides default monitoring tasks and default KPIs. Users do not need to select
KPIs or objects for default monitoring tasks.
The M2000 provides the function of monitoring object groups of an NE type. Object group
types are defined by default, whereas object group instances can be customized. Users can
create a monitoring task after selecting object group instances as monitored objects.
Real-time performance monitoring is classified into common-period monitoring and
short-period monitoring. Each type of NE supports only one monitoring period at a time.
Tasks of both monitoring types can monitor default KPIs.
Common-period real-time performance monitoring whose period is configurable supports the
following functions:
The periods of real-time performance monitoring supported by NEs are the same as the
periods described in the feature WOFD-030100 Performance Measurement Data Collection
and Storage. The system sets the default KPI monitoring periods for each type of NE. Users
can also modify the monitoring periods as required. The new monitoring periods take effect
when new monitoring tasks are started.
The counters that can be monitored in real time are not the raw performance counters, but the
KPIs calculated based on the raw performance counters. The results of the counters that are
monitored in real time can be displayed in a list, line chart or column chart. The M2000
supports the following functions for displaying monitoring results:
The system allows users to set the counters that can be monitored in real time and set
filter criteria. The settings are used to generate threshold alarms. The thresholds to be set
consist of the upper and lower thresholds, which are set by being compared with
historical values. Users can set the time range for the preset threshold to take effect.
The M2000 supports the integrity check of monitoring data. Users can set to use curves
in special colors to identify missing status or loss status.
When the system displays monitoring results in a list, users can adjust the display of the
monitoring list by setting counter thresholds. In the list, the counter values that are
greater than the upper threshold or less than the lower threshold are displayed according
to the preset formats. Users can also set the filter criteria of counter results so that the
system displays or hides only the data that meets the filter criteria.
When the system displays monitoring results in a line chart or column chart, users can
adjust the display of the monitoring charts by setting the counter thresholds, including
the upper threshold and the lower threshold. Users can also set the property, background,
tick table, and curve color of monitoring charts. They can also print a monitoring chart or
save it as a figure. When the data is displayed in a line chart, the horizontal axis
represents time and the vertical represents counter values. When users zoom in the line
chart, the interval of the horizontal axis changes accordingly.
Issue 02 (2012-04-12)

11

The M2000 allows users to export the data in a monitoring chart or in a monitoring table
to files. The supported file formats are XLS, CSV, HTML, and TXT.
The M2000 supports the trend analysis of counters. The system displays the counter
trend in a line chart according to the objects, counters, the difference between an upper
threshold and a historical value, and the difference between a lower threshold and a
historical value set by users. The curves of the upper thresholds, lower thresholds, and
actual values are displayed in different colors.
The M2000 supports the function of displaying counter monitoring results in a topology
view. After the tool tip is set, if users place the pointer on the topology icon of a
measured NE, the tip label of the counter monitoring results of the latest period is
automatically displayed.
Historical values refer to the performance counter values collected by sampling and calculating the
recent historical data.
The period of short-period real-time monitoring is fixed, and each type of NE supports only
one short period.
Table 2-1 lists the NEs supporting short-period real-time monitoring and whether the NEs
support user-defined KPIs.
Table 2-1 NEs supporting short-period real-time monitoring and whether the NEs support
user-defined KPIs
NE Type
Period (Unit: Minute)
Whether User-defined
KPIs Are Supported
eNodeB
No
The M2000 supports the following functions for displaying monitoring results:
When the system displays monitoring results in a list, users can adjust the display of the
monitoring list by setting counter thresholds. In the list, the counter values that are
greater than the upper threshold or less than the lower threshold are displayed according
to the preset formats. Users can also set the filter criteria of counter results so that the
system displays or hides only the data that meets the filter criteria.
When the system displays monitoring results in a chart, users can adjust the display of
the interface by setting the counter thresholds, including the upper threshold and the
lower threshold. Users can also set the property, background, tick table, and curve color
of monitoring charts. The M2000 also allows users to print a monitoring chart or save it
as a figure. When the data is displayed in a line chart, the horizontal axis represents time
in minute and the vertical axis represents counter values. When users zoom in the line
chart, the interval of the horizontal axis changes accordingly.
The M2000 allows users to export the data in a monitoring chart or in a monitoring table
to files. The supported file formats are XLS, CSV, HTML, and TXT.
Enhancement
Searching for objects to be monitored
Issue 02 (2012-04-12)

12

Real-time monitoring based on the object groups
Configuration of common monitoring periods
Short-period real-time monitoring of the eNodeB
Dependency
Short-period real-time monitoring applies to eNodeB in eRAN1.0 and later versions.
2.5 Base Station Power Saving Management

WOFD-200200 Base Station Power-Saving Management LTE
Availability
Summary
The M2000 provides the function of flexibly configuring power-saving policies of the
eNodeB to reduce the energy consumption of a lightly loaded eNodeB. Users can easily check
the power-saving status of an eNodeB and configure the power-saving parameters. The
M2000 also provides the functions of checking the eNodeB energy consumption and
collecting the energy consumption statistics.
Benefits
Users can flexibly set eNodeB power-saving policies so that the M2000 enables the
power-saving feature for an eNodeB when the eNodeB traffic load is low. This reduces
eNodeB energy consumption without affecting ongoing services, and reduces O&M
costs.
Users can easily monitor the power-saving status of eNodeBs and reconfigure
power-saving parameters.
Users can check the eNodeB energy consumption and collect the energy consumption
statistics to directly learn about the actual network energy consumption.
Description
The eNodeB power-saving management feature provides the following functions:
Configuring and managing power-saving policies

The M2000 provides the function of configuring the eNodeB power-saving feature to
implement the flexible management of eNodeB power-saving policies. The policy
properties that can be set include valid time segment, power-saving function switches,
shutdown decision thresholds, and restoration conditions. The M2000 provides the
following eNodeB power-saving features: dynamic adjustment of power amplifier (PA)
Issue 02 (2012-04-12)

13

voltage, intelligent carrier shutdown, intelligent RF channel shutdown, low-energy

consumption mode, and scheduled eNodeB power-on and power-off.
Dynamic adjustment of PA voltage: Users can adjust the offset voltage of the PA
based on different output power and modulation modes to ensure that the PA
efficiently runs in power-saving mode in different situations.
Intelligent carrier shutdown: This feature applies to the scenario where an area is
covered by multiple carriers. Based on the traffic distribution of each carrier, users
can perform related settings so that some carriers are shut down when the carrier
traffic is low. Then, the eNodeB enables UEs to migrate to some of the carriers and
shut down the carriers whose traffic is low.
Intelligent RF channel shutdown: Based on the distribution of cell traffic, users can
perform related settings so that the eNodeB retains only one RF TX channel and shuts
down other RF TX channels to reduce static energy consumption in case of light
traffic.
Low-energy consumption mode: Users need to force a cell to switch to low-energy

consumption mode in case of exceptions such as power supply undervoltage. Then,
users can reduce specifications such as cell TX power and available service
bandwidth of cells to prolong the system service duration.
Scheduled eNodeB power-on and power-off: This feature applies to special scenarios
such as the high-speed railway coverage scenario. If the traffic load within a time
segment is 0, the M2000 automatically powers off the eNodeB during the time
segment.
Checking power-saving status of the eNodeB

Users can check the current power-saving policy of the selected eNodeB, check whether
a certain power-saving feature is enabled, and check the detailed configuration
parameters of the feature. In addition, users can further reconfigure the detailed
configuration parameters according to the actual requirements.
Querying and measuring energy consumption and traffic load of eNodeBs

The M2000 allows users to query, measure, and compare energy consumption and traffic
load of eNodeBs. This facilitates evaluating energy-saving effects.
Querying energy consumption and traffic load

When querying eNodeB energy consumption and traffic, users can specify an object
type to query the traffic data aggregated hourly. The M2000 displays query results in
tables and charts and allows users to export the results as an XLS file or a PNG, JPG,
or GIF image.
Displaying network energy-saving effects

The M2000 compares energy consumption and throughput of eNodeBs in different
periods. Then, the M2000 displays historical trends and changes of energy
consumption and throughput in tables and charts. Comparison results can be saved as
an XLS file or a PNG, JPG, or GIF image. This helps users evaluate eNodeB
energy-saving effects.
Enhancement
The following features are added to M2000 V200R011C00:
Issue 02 (2012-04-12)
Displaying network energy-saving effects

14

Dependency
Users can use the preceding power-saving features only after the corresponding eNodeB
features are already purchased.
2.6 OSS Solution

WOFD-540100 Network Time Synchronization Solution
Availability
Summary
The M2000 provides a complete time synchronization solution for the mobile O&M network
and ensures that the time of the entire network is consistent.
Benefits
The M2000 ensures that the time of all the network devices is consistent, enhancing operation
and data reliability.
The standard time reference source provided by the M2000 is both time and cost efficient.
Description
The system directly obtains the standard time from the GPS or the GLONASS by using the
dedicated time source server. Then, on the basis of the NTP/SNTP, the solution provides the
M2000 server and managed NEs with the time synchronization information.
SYN CLOCK V5 BITS, which is developed independently by Huawei, is used as the time
source server. It provides two NTP service channels for mutual backup. SYN Clock V5 serves
as the top-level time server node of the NTP time server. It provides the standard time source
for the M2000 server and the NEs that support the NTP/SNTP.
If the telecom operator already provides the NTP server at the highest layer, but cannot
provide the NTP service for all the nodes on the mobile O&M network owing to reasons such
as networking, SYN Clock V5 can serve as the middle-layer NTP server. SYN Clock V5
obtains time from the upper-layer NTP server and provides the time synchronization service
for the M2000 server and the managed NEs.
GPS is a Global Positioning System provided by USA, and GLONASS is a global navigation satellite
system provided by Russia. The navigation satellites use atomic clocks to provide the most accurate
Coordinated Universal Time (UTC).
Enhancement
Issue 02 (2012-04-12)
The M2000 server functions as an intermediate NTP server.

15

Dependency
This feature applies to the NEs that support WOFD-070800 Supporting Network Time
Synchronization.
To ensure that the final delivery can meet the expectations and requirements of customers, this
solution must be delivered with the dedicated solution analysis, planning, and implementation
services provided by Huawei. These services, however, are not contained in the software
license of this feature.
2.7 Intelligent Development Platform

WOFD-520100 iSStar
Availability
Summary
The iSStar is a secondary development platform. It provides an integrated developing,
debugging, and operating environment that is based on the High-level Script Languages
(HSL). It also provides various function libraries.
Benefits
The iSStar relieves the burden of tedious and repetitive work and significantly improves
work efficiency.
The iSStar changes repeated and error-prone work to automatic scripts, allowing users to
focus on core services.
The iSStar provides users with real time updated function libraries for constant
improvement.
The language and environment of the iSStar is easy to learn, which reduces the cost of
learning.
The iSStar scripts are easy to copy and distribute, which helps telecom operators share
the O&M experience.
Description
The iSStar provides users with the integrated development environment of the HSL and the
task scheduling function.
The iSStar is used in the following scenarios:
Monitoring daily report
Inspecting equipment (health check)
Upgrading versions
Adjusting global data
Issue 02 (2012-04-12)

16

Adjusting parameters
Backing up data
The iSStar provides the following functions:
HSL-integrated development environment

The interface of the HSL-integrated development environment consists of the script
editing pane, debugging pane, running pane, and the feedback pane.
The script editing pane provides the basic text editing functions such as copying, pasting,
cutting, searching, replacing, undoing, and redoing. The script editing pane also provides
the syntax check function.
The debugging pane provides powerful functions for debugging scripts. For example,
users can run the script step by step or in skip mode, set or cancel breakpoints, and
perform or ignore sub-processes. In addition, users can view the stacks and variables of
the memory in the feedback pane.
The running pane provides a running environment for scripts. The supported execution
modes are partial execution, complete execution, execution for a single NE, and
execution for multiple NEs. Users can pause, resume, and forcibly stop a running script.
The running status of a script such as the output information, the MML messages
returned from NEs, and the execution result are displayed in the feedback pane in real
time.
The iSStar retains the difference-based display of keywords, character strings, numerals,
names of invoked functions, comments, and matching brackets for easy browsing. The
display mode meets the requirements of program development engineers.
The iSStar provides the auto-indent function to increase the efficiency of editing scripts.
The iSStar provides a scalable HSL foundation class (HFC). It encapsulates complicated
and common service implementation such as file operation and MML text resolution to
functions. These service functions can be flexibly expanded, meeting various
requirements. The HFC function library provides input association, through which the
system searches for the associated functions that map the starting letters of user input.
The associated results are displayed in a list on the GUI for users' selection.
The iSStar supports the logical debugging through virtual NEs. Users can set virtual NEs
in the debugging environment so that they can perform basic logical debugging on the
target scripts.
Script task scheduling

Scripts are executed through tasks. The iSStar supports scheduled tasks, periodic tasks,
and immediate tasks. When creating a task, users can set the start time, period, execution
times, associated NEs, main script, and accessory script of the task.
Script execution tasks are managed and scheduled by the centralized task module.
Through the task manager, users can view the task information such as name, status, type,
period, start/end time, whether the last execution is successful, and execution times.
Users can also start, pause, and stop the task.
Users can download the execution result report of a task. The execution result of a task
can be displayed on the GUI or exported to a report. The results of periodic tasks cannot
be displayed on the GUI. The results are displayed on the GUI in the form of transaction
messages and MML messages. Report output is the function provided by the HSL.
Report results are saved as XLS or HTML files. The result reports of a periodic task can
be stored for seven days.
HSL
The HSL is the script language that is based on python. It seamlessly integrates with the
MML. The HSL provides variable numeric types, operators, condition check, loop, and
Issue 02 (2012-04-12)

17

built-in functions. The HSL provides various library functions and allows users to
customize functions.
The script language mechanism is as follows:
Numeric types include integer, floating point, character string, Boolean, list,
dictionary, and file object.
Operators include basic operators, bit operators, comparison operators, Boolean

operators, sequence operators, and dictionary operators.
Statements support simple statement and compound statement such as assignment

statement, simple expression, compound expression, condition check, loop, and
custom functions.
The HSL supports the following library functions:
NE operation functions
MML message parsing functions
CSV parsing functions
XML parsing functions
Alarm message parsing functions
Database operation functions
Alarm operation functions
EMS operation functions
Type switchover functions
Time functions
Information input/output functions
Network operation functions
Report operation functions
Directory and file operation functions
GUI exchange database functions
Task management functions
Assert functions
Mail sending functions
Application project management

The iSStar allows users to organize and manage scripts by taking an application project
as a unit, supporting the development of multiple scripts. Application projects are the
advanced organization of programs. Compared with files, application projects feature
high independence, integrity, and consistency. The iSStar allows users to compile
application projects. It provides an interface for users to operate the configuration
parameters related to application projects, helping users design and use application
projects.
The iSStar provides the following functions related to project management:
Issue 02 (2012-04-12)
Opening or creating a project
Adding or creating a file in a project
Closing a project
Deleting a project
Running a project
Compressing a project

18

Editing project properties
Editing the configuration parameters of a project
Decompressing a project
Enhancement
The function of recording MML commands that have been executed by running iSStar scripts
into M2000 logs is added to M2000 V200R011C01.
The logical debugging through virtual NEs is added to M2000 V200R009.
In M2000 V200R008, the functions of the iSStar are enhanced. The new functions are as
follows:
New functions of the HSL integrated development environment
Retaining the difference-based display mode
Providing the auto-indent function to increase the efficiency of editing scripts
Providing the predictive input of the HFC function
Application project management
Dependency
None
2.8 Wireless Bearer Network Management

WOFD-290300 IP QoS Management LTE
Availability
Summary
During routine operation and maintenance, the M2000 provides the functions of monitoring
IP link alarms and key performance indicators (KPIs). Therefore, the IP QoS management
feature helps users learn about the recent network performance.
Benefits
Users can monitor QoS counters in real time and query the historical data of QoS counters to
learn about the network performance, facilitating network optimization and fault analysis.
Description
The IP QoS management feature provides the following functions:
Issue 02 (2012-04-12)
IP link management

19

Users can view IP link information and alarm status information. In addition, the M2000
can automatically update the configuration information about IP links. Currently, the
supported IP link types are as follows: IPPATH, PPP Link, MP Group, FE port, IP PM.
QoS management
The M2000 provides the function of managing the QoS of the IPPATH, PPP Link, MP
Group, FE port, IP MP. Therefore, users can query the historical data of QoS counters of
IP links or monitor the QoS counters in real time. The query results or monitoring results
of QoS counters can be displayed in a table or a chart such as a column bar or line bar.
Enhancement
None
Dependency
None
Issue 02 (2012-04-12)

20

Acronyms and Abbreviations
Numerics
3GPP
3rd Generation Partnership Project
A
ACL
access control list
ALD
antenna line device
ATAE
Advanced Telecommunications Application Environment
B
BSIC
base transceiver station identity code
C
CA
Certificate Authority
CAPEX
capital expense
CGI
cell global identity
CORBA
Common Object Request Broker Architecture
CRL
certificate revocation list
D
DST
daylight saving time
Issue 02 (2012-04-12)

21

ESN
electronic serial number
F
FDN
full distinguished name
FTP
File Transfer Protocol
G
GPS
Global Positioning System
GSM
Global System for Mobile Communications
GUI
graphical user interface
H
HFC
HSL foundation class
HSL
High-Level Script Languages
HTTP
Hypertext Transfer Protocol
I
ICA
independent computing architecture
ICIC
inter-cell interference coordination
K
KPI
key performance indicator
L
LDAP
Lightweight Directory Access Protocol
LTE
Long Term Evolution
M
MD5
message digest algorithm 5
MLB
mobility load balancing
MML
man-machine language
MOCN
multioperator core network
MRO
mobility robust optimization
Issue 02 (2012-04-12)

22

N
NTP
Network Time Protocol
O
O&M
operation and maintenance
OPEX
operating expense
OSS
operations support system
P
PC
personal computer
R
RAI
routing area identity
RAN
radio access network
RAT
radio access technology
RRM
radio resource management
S
SLS
multi-server load-sharing
SNMP
Simple Network Management Protocol
SNTP
Simple Network Time Protocol
SSH
Secure Shell
SSL
Secure Sockets Layer
SSO
single sign-on
T
TA
tracing area
TCP
Transfer Control Protocol
TLS
transport layer security
Issue 02 (2012-04-12)

23

UDP
User Datagram Protocol
UMTS
Universal Mobile Telecommunications System
V
VPN
virtual private network
VSWR
voltage standing wave ratio
Issue 02 (2012-04-12)

24

IManager M2000 V200R012 Optional Feature Description (EWBB2.1) V1.1 (20120606)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

IManager M2000 V200R012 Optional Feature Description (EWBB2.1) V1.1 (20120606)

Загружено:

Авторское право:

Доступные форматы

iManager M2000 V200R012

Optional Feature Description(eWBB2.1)

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base