Specifications For The IManager U2000 Northbound Interface 07 (20170808)

Specifications for the iManager
U2000 Northbound Interface
Issue 07
Date 2014-01-07
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 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.
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
Issue 07 (2014-01-07) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Specifications for the iManager U2000 Northbound Interface INTERNAL
Contents
1 Introduction to the Northbound Interface ............................................................................... 1

2 Functions of U2000 Northbound Interfaces ............................................................................. 2
2.1 Alarm Interface ................................................................................................................................................. 3
2.1.1 Alarm CORBA Interface ......................................................................................................................... 5
2.1.2 Alarm Streaming Interface ...................................................................................................................... 5
2.1.3 Alarm SNMP Interface ............................................................................................................................ 6
2.1.4 Alarm File Interface ................................................................................................................................ 6
2.2 Performance Interface ...................................................................................................................................... 6
2.2.1 Performance File Interface (NE-Based) .................................................................................................. 7
2.2.2 Performance CORBA Interface................................................................................ 错误!未定义书签。
2.3 Configuration Interface .................................................................................................................................... 7
2.3.1 Configuration File Interface (NE-Based) ................................................................................................ 9
2.3.2 Command Line Interface ........................................................................................................................ 9
2.3.3 CORBA Interface for Basic Configuration ............................................................................................. 9
2.4 CME Configuration Interface ......................................................................................................................... 10
2.4.1 Configuration File Import/Export Interface (CME) .............................................................................. 12
2.4.2 CORBA Interface (CME)...................................................................................................................... 12
2.5 Inventory Interface ......................................................................................................................................... 12
2.6 Security Interface ........................................................................................................................................... 13
3 Recommended Interconnection Solutions ............................................................................. 14

4 Interconnection with NMSs of Leading Vendors................................................................. 15
5 Applications ................................................................................................................................. 17
A Acronyms and Abbreviations .................................................................................................. 19
Issue 07 (2014-01-07) Huawei Proprietary and Confidential ii

1 Introduction to the Northbound Interface
The northbound interface links the U2000 and the network management system (NMS).
Figure 1-1 shows the position of the northbound interface in a telecommunications
management network (TMN).
Figure 1-1 Position of the northbound interface in a TMN
Issue 07 (2014-01-07) Huawei Proprietary and Confidential 1

2 Functions of U2000 Northbound Interfaces
The U2000 is an operation and maintenance (O&M) system that centrally manages Huawei
mobile products and provides open northbound interfaces to the NMS.
As shown in Figure 2-1, the U2000 provides a full range of northbound interfaces to meet
various requirements of different customers.
Figure 2-1 U2000 northbound interfaces
The U2000 provides the following O&M services with different northbound interfaces:
 The fault management module is provided with the CORBA interface, ASCII streaming
interface, SNMP interface, and file interface.
 The performance management module is provided with the file interface.
 The configuration management module is provided with the file interface, command line
interface, and CORBA interface. The CORBA interface, however, is not recommended.
 The security management module is provided with the Security CORBA interface,
LDAP user management interface, LDAP user authentication interface, and RADIUS
user authentication interface.

 The inventory management module is provided with the file interface.

Huawei has established strategic partnerships with leading NMS vendors. Pre-interconnection
and interoperability tests have proved that the U2000 can interconnect with the NMSs of these
vendors seamlessly through northbound interfaces.
Huawei also provides customized northbound interconnection solutions tailored to the needs
of customers. Customers can discuss with Huawei local service engineers to determine the
interconnection solutions that they require.
By setting up seamless interconnection between the U2000 and the NMSs of partners, Huawei
provides customers with an end-to-end O&M solution that is applicable to the entire network.
The following sections describe U2000 northbound interfaces.
For details about U2000 northbound interfaces, see U2000 Release Documents, for example
“iManager U2000 V200R017C10SPC230 Release Documents-EN\07.Northbound File”
2.1 Alarm Interface

Alarm interfaces are categorized into the following types:
 Alarm CORBA interface
 Alarm ASCII streaming interface
 Alarm SNMP interface
 Alarm file interface
Table 2-1 describes the functions of these alarm interfaces.
Table 2-1 Description of alarm interfaces
Protocol Function Characteristics Scenario

CORBA  Reports alarms in real  Compatible with 3rd Applicable to
interface time. Generation Partnership scenarios that require
 Queries active alarms. Project (3GPP) Release high reliability and
6 where
 Filters alarms by
 Real-time alarm comprehensive
criteria. functions need to be
reporting
 Clears, acknowledges, performed.
 Comprehensive
and unacknowledges Applicable to
alarms. functions such as
filtering alarms by scenarios that
 Reports comply with 3GPP
criteria; clearing,
communication acknowledging, and Release 6
surveillance unacknowledging Applicable to
notifications. alarms scenarios where the
 High reliability NMS interconnects
achieved by querying with OSSs of
active alarms and multiple vendors.
reporting
communication
surveillance
notifications


ASCII  Reports alarms in real  Simple and easy Applicable to
streaming time. connection to the NMS scenarios that require
interface  Queries active alarms.  Real-time alarm real-time alarm
reporting reporting and easy
 Filters alarms by connection to the
criteria.  Simple functions of NMS.
 Resends alarms filtering alarms by
generated during the criteria
disconnection after  High reliability
connection is achieved by querying
resumed. active alarms and
 Reports handshake resending alarms
message. generated during the
disconnection after
connection is resumed
 SSL connection mode
is supported
SNMP  Reports alarms in real  Compatible with Applicable to
interface time. SNMPv1, SNMPv2c, scenarios that require
 Queries active alarms. and SNMPv3 the SNMP interface.
 Real-time alarm
 Filters alarms by
criteria. reporting
 Comprehensive
 Clears, acknowledges,
and unacknowledges functions such as
alarms. filtering alarms by
criteria, reporting
 Reports heartbeat heartbeat traps,
traps. querying active alarms,
and clearing,
acknowledging, and
unacknowledging
alarms
File Periodically exports  Periodic export of Applicable to
interface alarm data to files based alarm data to files scenarios that require
on preset criteria. based on preset criteria massive alarm query
 Query of a large and scheduled alarm
number of alarms verification.
Applicable to
scenarios where
multiple alarm
interfaces are used
together.
NOTE
This interface cannot
be used for reporting
alarms in real time.

2.1.1 Alarm CORBA Interface

The alarm CORBA interface complies with 3GPP Release 6. The interface definition language
(IDL) is defined by Huawei. The Object Request Broker (ORB) Core complies with the
Object Management Group (OMG) 2.3 standards. The CORBA notification service and
naming service comply with the OMG 1.0 standards.
The alarm CORBA interface provides the following functions:
 Reporting alarms in real time: The NMS subscribes to alarms from the U2000 using the
notification service. The U2000 then uses the notification service to send real-time
alarms to the NMS.
 Querying active alarms: If the NMS is disconnected from the U2000, the NMS queries
active alarms by synchronizing its active alarm list with that of the U2000 through the
CORBA interface.
 Clearing, acknowledging, and unacknowledging alarms: The NMS clears, acknowledges,
and unacknowledges active alarms through the CORBA interface.
 Filtering alarms by criteria: The NMS provides filter criteria for reporting alarms in real
time and querying active alarms.
 Implementing basic functions such as basic configuration management, notification
service, and communication surveillance.
− Basic configuration management allows users to query the main configuration data of
the objects that generate alarms. Note that this interface is not used for querying the
configuration data of the entire network.
− Notification service allows users to subscribe to notifications, cancel subscription,
and query subscription status. Notifications are reported using the notification
service.
− Communication surveillance allows users to set and query heartbeat intervals and
report heartbeat traps.
Alarm definitions may vary according to NE versions. For details about the alarm definitions,
see the alarm list of relevant NE versions. The alarm fields that may change include alarm ID,
alarm name, alarm severity, alarm category, and location information.
2.1.2 Alarm Streaming Interface

After the NMS is connected to the U2000 through the alarm streaming interface, the NMS can
receive alarm data in real time. The alarm streaming interface transmits data in ASCII format.
The U2000 sends the alarm data collected from NEs to the alarm streaming interface in real
time.
The alarm streaming interface provides the following functions:
 Synchronizing alarms: When the NMS is disconnected from the U2000, alarms are
buffered. After the NMS is connected to the U2000 again, the U2000 sends the alarms
generated within five hours before the reconnection. The buffer duration is set to 5 by
default. Users can change the value. It is recommended that this value be set to be
smaller than or equal to 5.
 Querying active alarms: When the NMS is connected to the U2000, the NMS issues
commands to instruct the U2000 to report active alarms. When reporting active alarms,
the U2000 buffers real-time alarms. After the active alarms are reported, the U2000
reports the buffered real-time alarms.

 Reports handshake message: The alarm streaming interface provides handshake

messages. If the NMS does not receive any handshake messages within a preset period,
the connection is considered as failed. The handshake period is configurable. The default
period is 60 seconds.
 Filtering alarms: The alarm streaming interface filters alarms by NE type, NE name,
object name, alarm category, alarm severity, or alarm type. This function allows users to
obtain the alarm information that they require.
The alarm streaming interface does not allow users to clear, acknowledge, or unacknowledge
alarms.
2.1.3 Alarm SNMP Interface

The SNMP requires User Datagram Protocol (UDP). The U2000 northbound SNMP interface
supports the SNMPv1, SNMPv2c, and SNMPv3 protocols.
The alarm SNMP interface provides the following functions:
 Reporting alarms in real time
 Querying active alarms
 Clearing, acknowledging, and unacknowledging alarms
 Filtering alarms to be reported or queried
 Reporting heartbeat traps
2.1.4 Alarm File Interface

The alarm file interface periodically exports alarm data from the database to files based on
preset criteria. Exported alarm files are provided by the following methods:
 The NMS uses FTP or SFTP to obtain the exported alarm files from a specified directory
on the U2000 server.
 The U2000 uses FTP or SFTP to upload the exported alarm files to a specified server
after a server IP address and a file directory are specified by the NMS.
The alarm file interface periodically exports alarm data, including current alarms, historical
alarms, and events on the entire network. Exported alarm files are saved in CSV or XML
format. Compressed alarm files are in ZIP or GZIP format.
2.2 Performance Interface

The file interface is the most commonly used performance interface. The performance file
interface periodically exports performance data to files based on preset export criteria. Users

can obtain exported performance files using the NMS or the U2000. The methods of obtaining
performance files are the same as the methods of obtaining alarm files. For details, see section
2.1.4 "Alarm File Interface."
Table 2-2 Description of performance interfaces
File interface  Periodically exports  Short delay This interface is

(NE-based) performance data to files. for file recommended.
 Generates one result file for export
each NE in each period.  No impact
 Exports the original NE on the
measurement results. database
Aggregated measurement
results and measurement
results for user-defined
counters cannot be
exported.
 Saves the exported file in
XML format, which
complies with the 3GPP
specifications.
2.2.1 Performance File Interface (NE-Based)

After the U2000 mediation receives performance files from NEs, it parses and then sends
them to the northbound interface, where they are converted into XML files. This shortens file
export duration because files are not exported from the U2000 performance database and has
no impact on importing performance data into the U2000 performance database.
This interface generates only one file for each NE in each period.
The exported file is saved in XML format, which is a common format used by the 3GPP
specifications. Compressed exported files are in GZIP format.
Only the original data of NEs can be exported through this interface. Aggregated data and
user-defined counters cannot be exported.
Performance counter definitions may vary according to NE versions. For details about the
performance counter definitions, see the performance counter list of relevant NE versions.
The performance counter fields that may change include measurement unit ID, measurement
unit name, counter ID, counter name, and counter formula.
2.3 Configuration Interface

The northbound configuration interface consists of the file interface, CORBA interface, and
command line interface. The file interface is the most commonly used configuration interface.
The configuration file interface periodically exports configuration data of the entire network
to files. These files are saved in XML or CSV format. Users can obtain exported configuration
files using the NMS or the U2000. The methods of obtaining configuration files are the same
as the methods of obtaining alarm files. For details, see section 2.1.4 "Alarm File Interface."

Table 2-3 Description of configuration interfaces

File interface  Periodically  Simple and Applicable to
(NE-based) exports stable interfaces scenarios where the
configuration  Integrated data northbound
data of the configuration interface
 Two file
entire network is required by
to files. structures are non-RAN NEs.
provided: tile
 Generates one Highly recommended
and tree.
file for each when configuration
NE. data needs to be
 Saves exported queried but not to be
files in XML or modified.
CSV format. Not applicable to
 Supports radio real-time or
access network incremental data
(RAN) and core export.
network (CN) Not applicable to
NEs. configuration file
 Exports import.
configuration Not applicable to
files. BulkCM.
NOTE
The tile structure is
recommended.
Command line  Queries and The MML Recommended for

interface modifies commands for querying or modifying
configuration querying and a small amount of
data. modifying configuration data.
 Issues configuration data This interface can also
maintenance should be be used together with
commands in supported by the the file interface
addition to NEs and (NE-based). When
configuration corresponding used together, the file
commands. U2000 mediation. interface is used to
SSL connection query a large amount
mode is supported. of data while the
command line
interface is used to
modify simple data
configuration.


CORBA interface  Queries the Compatible with Not recommended.
for basic standard 3GPP 3GPP Release 6 Not applicable to
configuration configuration configuration
data on the parameter
entire network. configuration.
 Notifies users of Not applicable to
configuration BulkCM.
data changes.

NOTE
Supports RAN
and CN NEs. If the customer requires
this interface, contact
Huawei MO.
2.3.1 Configuration File Interface (NE-Based)

The configuration file interface (NE-based) periodically exports configuration data to files.
The exported files are saved in CSV or XML format. Compressed exported files are in GZIP
format.
This interface does not export real-time or incremental data.
2.3.2 Command Line Interface

The northbound command line interface provides connection between the NMS and the NEs
managed by the U2000. This interface receives MML commands from the NMS in command
line mode and issues commands to NEs. The prerequisite for using this interface is that both
the NEs and related mediations should support the MML protocol.
MML command definitions may vary according to NE versions. Therefore, the NMS should
support MML commands of different NE versions. For details about the MML command
definitions, see the MML commands of relevant NE versions.
This interface has a new feature available in U2000 V200R009 and later releases to allow
users to issue MML commands in batches.
The NMS can generate an MML script in the specified format and save it to a specified
directory on the U2000 server. The NMS then issues commands to activate the MML script.
The command line interface parses the script and issues the MML commands contained in the
script to NEs. The MML command execution results will be saved into files. The NMS can
use FTP or SFTP to obtain these files from a specified directory on the U2000 server.
2.3.3 CORBA Interface for Basic Configuration

The CORBA interface for basic configuration complies with 3GPP Release 6 and provides the
following functions:
 Querying the standard 3GPP configuration data on the entire network
 Notifying users of configuration data changes
This interface does not provide the following functions:
 Modifying configuration parameters

 BulkCM
For detailed functions of the CORBA interface, see 3GPP Release 6.
NOTE
If the customer requires this interface, contact Huawei MO.
2.4 CME Configuration Interface

The CME configuration interface supports the import and export of RAN configuration data
and also supports BulkCM. Currently, the CME configuration interface does not support
non-RAN NEs.
The CME configuration interface provides a whole-process configuration solution, which
involves the process of obtaining northbound configuration data to activating the data. It
provides the file interface and CORBA interface that can be used for importing and exporting
configuration data.

Table 2-4 Description of CME configuration interfaces

Configuration Configuration file  Simple and stable Applicable to base
file export interface: interfaces station creation and
import/export  Exports RAN  Data integrity batch reconfiguration.
interface configuration data Applicable to querying
 XML files are in
(CME) on the entire NE configuration data.
the tile structure.
network. Applicable to NEs on
 Supports periodical RAN including GBSS,
data export and UTRAN, and eRAN,
manual data but is not applicable to
export. NEs on CN or other
 Saves networks.
configuration files Applicable to the
in XML format. scenario where
Configuration file customers need to send
import interface: configuration data to
NEs through the
 Imports RAN northbound interface.
configuration files
in XML format. Not applicable to
incremental data
 Imports export.
reconfiguration
policies in XML
files issued by the
NMS to the U2000
(CME). After the
U2000 (CME)
parses and sends
the XML files to
NEs, these
reconfiguration
policies take effect
on these NEs.
 Supports BulkCM
operations.
CORBA  Queries the Compatible with Applicable to base
interface standard 3GPP 3GPP Release 6 station creation and
(CME) configuration data batch reconfiguration.
on the entire Applicable to querying
network. NE configuration data.
 Notifies users of Applicable to NEs on
session status RAN including GBSS,
changes. UTRAN, and eRAN,
 Modifies but is not applicable to
configuration NEs on CN or other
parameters. networks.
 Supports BulkCM. Applicable to scenarios
where the CORBA
interface is required.

2.4.1 Configuration File Import/Export Interface (CME)

The CME file interface supports the export and import of configuration data.
Imported configuration data files are saved in XML format.
Exported configuration data files are saved in XML format. Compressed exported
configuration data files are in ZIP format.
The interface supports manual data export in real time but does not support incremental data
export.
2.4.2 CORBA Interface (CME)

The CORBA interface (CME) complies with 3GPP Release 6 and provides the following
functions:
 Querying the standard 3GPP configuration data on the entire network
 Notifying users of session status changes
 Modifying configuration parameters
 BulkCM
2.5 Inventory Interface

The inventory interface periodically exports inventory data to files. The NMS can use FTP or
SFTP to obtain the exported inventory data files from a specified directory on the U2000
server. Alternatively, the U2000 can use FTP or SFTP to upload the exported inventory data
files to a specified server if the server IP address and a directory have been specified by the
NMS.
An inventory data file contains the following data:
 Logical inventory data: information about cells and NE versions.
 Physical inventory data: information about racks, subracks, slots, boards, antennas, and
ports. Physical inventory attributes include the device location, device name, device type,
device version, electronic label, serial number, device vendor, and delivery date.
There are two file formats, NE-based inventory files and MOC-based inventory files.
NE-based inventory files are saved in CSV, XML, or TXT format. They cannot be
compressed.
MOC-based inventory files are saved in CSV or XML format. They cannot be compressed.
This interface supports full data export, but does not support incremental or real-time data
export.
For details about the types of NE that support inventory management, see the function list of
relevant U2000 version.

2.6 Security Interface

Table 2-5 describes the functions and recommended scenarios of different security interfaces.
Table 2-5 Description of security interfaces
Interface Function Recommended Scenario

LDAP user Complies with LDAP. Through this Applicable to scenarios where
management interface, a third-party security the LDAP interface is required
interface management system can create, by a third-party user
modify, delete, and query accounts of management system for the
Huawei OSS systems. interconnection of security
management.
LDAP user Supports the account authentication Applicable to scenarios where
authentication based on LDAP. Supports remote the LDAP interface is required
interface authentication of user names and by a third-party user
passwords. authentication system for the
interconnection of central
authentication services.
RADIUS user Supports the account authentication Applicable to scenarios where
authentication based on RADIUS. Supports remote the RADIUS interface is
interface authentication of user names and required by a third-party user
passwords. authentication system for the
interconnection of central
authentication services.
Security The ORB Core used by the security Applicable to scenarios where
CORBA CORBA interface complies with the the security CORBA interface
interface OMG 2.3 standards. Through this is required by a third-party user
interface, a third-party security management system for the
management system can query, create, interconnection of central
modify, and delete users, and authorize authentication services.
users by adding them to a user group.

3 Recommended Interconnection Solutions
The interconnection solutions listed in Table 3-1 are recommended.
Table 3-1 Recommended solutions
Service Scenario Recommended Solution

Configuration RAN The configuration file import/export interface
(CME) is recommended.
CN The configuration file interface (NE-based) is
recommended.
Mixed network where The configuration file import/export interface
RAN and CN coexist (CME) is recommended for RAN.
The configuration file interface (NE-based) is
recommended for CN or other NEs.
Performance N/A The performance file interface (NE-based) is
recommended.
Alarm N/A The CORBA interface is highly recommended.
The alarm streaming interface in NAMEVALUE
format is the second choice.
Security N/A The LDAP user management interface and
LDAP user authentication interface are
recommended.
Inventory N/A The file interface is recommended.
NOTE
 The recommended interconnection solutions for China Mobile, China Unicom, and China Telecom
are provided in other documents.
 The U2000 cannot be interconnected with NMSs provided by equipment suppliers. For example,
Nokia Siemens Networks, Ericsson, and Alcatel-Lucent company.
 Unless otherwise requested by customers, recommend appropriate interfaces based on their
characteristics and application scenarios.

4 Interconnection with NMSs of Leading

Vendors
The U2000 has been successfully interconnected with the NMSs of some leading NMS
vendors and obtained relevant certificates. The interconnections with NMSs of other vendors
are in progress.
Table 4-1 Interconnection with the NMSs of other vendors
NMS NMS Interface Interconnection Description

Partner Product Type
HP TeMIP CORBA The interoperability test is successful. The

(FM) test report and certificate are available.
ASCII The interoperability test is successful, but the
(FM) test report and certificate are not available.
OVPI File (PM) The interoperability test is successful. The
test report is available but the certificate is
not available.
IBM Netcool CORBA The interoperability test is successful. The
ASCII The interoperability test is successful. The
SNMP The interoperability test is successful. The
(FM) test report is available but the certificate is
not available.
Vallent File (PM) The interoperability test is successful. The
Metrica test report and certificate are available.
Mycom NIMS-PrOpti File (PM) The interoperability test is successful. The
ma test report and certificate are available.
Aircom Optima File (PM) The interoperability test is successful. The
test report and certificate are available.
Datasafe File (CM) The interoperability test is successful. The

NMS NMS Interface Interconnection Description

Partner Product Type
TTI Netrac Fault CORBA The interoperability test is successful. The
Telecom Management (FM) test report and certificate are available.
Netrac File (PM) The interoperability test is successful. The
Performance test report and certificate are available.
Management
Remedy ARS CORBA The interoperability test is successful. The
(TTM) test report and certificate are available.
Inspur NetWatcher CORBA The interoperability test is successful. The
CORBA The interoperability test is successful. The
(TTM) test report and certificate are available.
MetarNet MetarWork CORBA The interoperability test is successful. The
CORBA + The interoperability test is successful. The
File (PM) test report and certificate are available.
CORBA The interoperability test is successful. The
(CM) test report and certificate are available.
Cramer Cramer 6 File (IM) The interoperability test is successful. The
not available.
Comptel NIMS File (IM) The interoperability test is successful. The
not available.
Harris NetBoss ASCII The interoperability test is successful. The
(FM) test report in the Claro project is available
and the certificate is available.
FlexiTon Ariadne File (IM) The interoperability test is successful. The
test report in the Ufone project is available
but the certificate is not available.
InfoVista VistaInsight File (PM) The interoperability test is successful, but the
test report and certificate are not available.
Subex TrueSource File (CM) The interoperability test is successful. The

5 Applications
The U2000 northbound interfaces have been deployed on the networks of many leading
telecom operators.
Table 5-1 Applications
Operator Interconnection Interconnection NMS Vendor

Module Interface
China Alarm Alarm streaming Bright Oceans, MetrarNet, and
Mobile others
China Configuration CORBA Bright Oceans, MetrarNet, and
Unicom others
Performance CORBA Bright Oceans, MetrarNet, and
others
Alarm CORBA Bright Oceans, MetrarNet, and
others
China Configuration CORBA and file Bright Oceans, MetrarNet, and
Telecom others
Performance CORBA and file Bright Oceans, MetrarNet, and
others
Alarm CORBA Bright Oceans, MetrarNet, and
others
Etisalat Performance File Etisalat
UAE
Alarm Alarm streaming HP TeMIP
SUNDAY Performance File SUNDAY
Hong Kong
Alarm Alarm streaming SUNDAY
AIS Performance File AIS
Thailand
Alarm Alarm streaming AIS
KPN Configuration File Cramer

Operator Interconnection Interconnection NMS Vendor

Module Interface
Netherlands Performance File Metrica, SEMORE, RRD
Alarm CORBA Netcool
Vodafone Alarm CORBA HP TeMIP
Spain
Performance File MYCOM
Configuration File MYCOM
O2 Performance File MYCOM
Germany
Configuration File MYCOM
T-Mobile Performance File T-Mobile
Germany
Orange Alarm CORBA Netcool
Poland
Reliance Alarm CORBA TTI
India
Performance File Reliance
TI Italy Alarm CORBA HP TeMIP
Optimus Alarm CORBA Optimus
Portugal
Movilnet Alarm SNMP Network Monitoring on the
Venezuela Web(GTE laboratories)
Clearwire Alarm SNMP Netcool
America
Performance File ClearTrack

A Acronyms and Abbreviations
Numerics
3GPP 3rd Generation Partnership Project
A
ASCII American Standard Code for Information Interchange
B
BML Business Management Layer
C
CORBA Common Object Request Broker Architecture
E
EML Element Management Layer
EMS Element Management System
L
LDAP Lightweight Directory Access Protocol
M
MML Man-Machine Language
N
NEL Network Element Layer

NML Network Management Layer

NMS Network Management System
O
OMG Object Management Group
ORB Object Request Broker
R
RADIUS Remote Authentication Dial In User Service
S
SML Service Management Layer
SNMP Simple Network Management Protocol
T
TMN Telecommunication Management Network
U
UDP User Datagram Protocol


Specifications For The IManager U2000 Northbound Interface 07 (20170808)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Specifications For The IManager U2000 Northbound Interface 07 (20170808)

Hochgeladen von

Copyright:

Verfügbare Formate

Specifications for the iManager

U2000 Northbound Interface

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 07 (2014-01-07) Huawei Proprietary and Confidential i

1 Introduction to the Northbound Interface ............................................................................... 1

3 Recommended Interconnection Solutions ............................................................................. 14

Issue 07 (2014-01-07) Huawei Proprietary and Confidential ii

1 Introduction to the Northbound Interface

Figure 1-1 Position of the northbound interface in a TMN

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 1

2 Functions of U2000 Northbound Interfaces

Figure 2-1 U2000 northbound interfaces

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 2

 The inventory management module is provided with the file interface.

2.1 Alarm Interface

Table 2-1 Description of alarm interfaces

Protocol Function Characteristics Scenario

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 3

Protocol Function Characteristics Scenario

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 4

2.1.1 Alarm CORBA Interface

2.1.2 Alarm Streaming Interface

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 5

 Reports handshake message: The alarm streaming interface provides handshake

2.1.3 Alarm SNMP Interface

2.1.4 Alarm File Interface

2.2 Performance Interface

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 6

Table 2-2 Description of performance interfaces

Protocol Function Characteristics Scenario

File interface  Periodically exports  Short delay This interface is

2.2.1 Performance File Interface (NE-Based)

2.3 Configuration Interface

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 7

Table 2-3 Description of configuration interfaces

Protocol Function Characteristics Scenario

Command line  Queries and The MML Recommended for

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 8

Protocol Function Characteristics Scenario

2.3.1 Configuration File Interface (NE-Based)

2.3.2 Command Line Interface

2.3.3 CORBA Interface for Basic Configuration

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 9

2.4 CME Configuration Interface

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 10

Table 2-4 Description of CME configuration interfaces

Protocol Function Characteristics Scenario

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 11

2.4.1 Configuration File Import/Export Interface (CME)

2.4.2 CORBA Interface (CME)

2.5 Inventory Interface

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 12

2.6 Security Interface

Table 2-5 Description of security interfaces

Interface Function Recommended Scenario

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 13

3 Recommended Interconnection Solutions

The interconnection solutions listed in Table 3-1 are recommended.

Table 3-1 Recommended solutions

Service Scenario Recommended Solution

Issue 07 (2014-01-07) Huawei Proprietary and Confidential 14