NetNumen U31 R10 V12.14.30 Unified Element Management System Product Description 595609
NetNumen U31 R10 V12.14.30 Unified Element Management System Product Description 595609
NetNumen U31 R10 V12.14.30 Unified Element Management System Product Description 595609
Version: V12.14.30
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION
Copyright 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
II
Intended Audience
This manual is intended for:
l Planning engineers
l Debugging engineers
Chapter Summary
1, Product Positioning and Describes the location and characteristics of the product on the
Characteristics network.
2, Product Architecture Describes the hardware, software architectures and the configuration
requirements of the product.
3, Product Functions Describes the service functions of the product, such as topology,
alarm and performance.
4, Networking Applications Describes the typical network solution mode of the product.
5, Interfaces and Protocols Describes the internal and external interfaces of the product and
related protocols.
6, Technical Specifications Describes the technical specifications of the product, including power
consumption and reliability.
II
1-1
l Based on the TMN hierarchical division, NetNumen U31 is located at the element
management layer.
l The NetNumen U31 provides upper level NMS/BBS with northbound interfaces.
l The NetNumen U31 provides lower level NEs with southbound interfaces.
1.2 Characteristics
The NetNumen U31 has the following characteristics:
1-2
l The NetNumen U31 supports multiple platforms and databases. The system is
developed based on the JAVA language, so it supports UNIX, Windows, and Linux
operating systems, and MSSQL Server and Oracle databases.
l The NetNumen U31 is modularized, so that it is easy to expand and upgrade. Clients
and servers are in platform + EMS mode. All EMSs and management function
modules are imbedded in the system platform as components. When you install
the NetNumen U31, you can select the devices to be managed to customize your
installation. In addition, the NetNumen U31 supports EMS systems of new products,
and is compatible with early and later versions. Because it is extendable, compatible,
and upgradable, it can meet specific network development needs.
l The NetNumen U31 provides open interfaces that can be used to integrate with a third
party EMS system. It supports SNMP and provides CORBA, TL1, FTP, DB, and ASCII
interfaces. In addition, it can be integrated with third party EMS systems, for example,
IBM Tivoli Netcool/OMNIbus and HP TeMIP. Therefore, carriers can construct an OSS
application system for the global network easily.
l The NetNumen U31 supports multiple access methods and networking modes.
Networks can be managed at any time and place. Depending on different application
scenarios, it can provide three access methods: GUI, CLI, and Web. It can be
accessed by either a local client or a remote client, and it can be maintained in a
unified manner or locally. You can select a client based on the application scenario,
habit, networking requirements, and bandwidth.
1-3
1-4
l Server
The NetNumen U31 server can operate on a Windows, Linux or UNIX platform. It
processes and saves NE data. In addition, the server communicates with upper level
NMS systems through the northbound interface. Based on functions, the NetNumen
U31 server can operate as either an application server or a database server. The
2-1
For the architecture of the NetNumen U31 software, see Figure 2-2.
2-2
l The NetNumen U31 system is based on a J2EE platform. It can operate on a UNIX,
Windows, or Linux OS. It uses a SQL Server or Oracle database.
l The NetNumen U31 server software is composed of multiple modules. Each mod-
ule provides certain functions, for example, configuration management, fault man-
agement, security management, topology management, performance management,
report management, policy management, and log management. The NetNumen U31
server software provides northbound interfaces for BOSS/NMS, and southbound in-
terfaces for NEs.
l The NetNumen U31 client software provides graphical user interfaces to operate and
maintain NEs.
l The NetNumen U31 system is designed with the load balance and disaster recovery
functions. Data is saved in a distributed manner to ensure system reliability.
2-3
2-4
3-1
Function Description
Server performance Checks server performance parameters (for example, CPU, memory, hard
management disk, and server process), and set system threshold parameters and
server performance alarms.
Database management Provides the following local database management functions: database
login, database resource view, database backup, database restoration,
data table backup, data table restoration, data table clearance, database
maintenance task, regular database maintenance task, and database
logout.
System data backup Provides backup and restoration functions for logs, alarms and
and restoration performance data.
Provides the backup function for database and files.
Other management Provides a unique Favorite function, which is similar to IE's Favorite
function, to offer fast link for frequently used functions.
Views the system time, prints settings, sets system styles, sets screen
lock, controls access rights, and sets window size.
License control Uses the license to control server-side MAC address, validity period,
number of user interface terminals, function package module, northbound
function package, device types under management and specific function
authorization.
3-2
Function Description
History data archive Executes periodically backup and deletion tasks for logs,
performance data, and alarms to prevent the database from being
overloaded.
Basic data backup Executes basic data backup tasks periodically. Back up all the basic
data of the network management system. Back up only data records
excluding the history data, such as table structure and history
alarms, notifications, logs, performance raw data (history data has
the dedicated backup function).
Version and database backup Executes NM version file and database backup tasks periodically.
File clearance Monitors data catalogs of different types, and executes periodically
clearance tasks when the index exceeds the threshold.
Automatic confirmation of Confirms history alarms before the set days automatically, so as to
history alarm improve the maintainability.
Function Description
Role management The user can create, modify, copy and delete a role set as well as assign a
role to a role set based on the operation rights.
The user can create, modify, copy and delete a role as well as assign
operation rights to a role based on the operation rights.
The user can set role rights for resources and an operation set, which means
that users of different roles manage different areas.
3-3
Function Description
User management A user has multiple attributes, including ID, password, user validity period,
password validity period, and department. The management functions
supported include: add/delete a user, associate a user with a role or a role
set, configure a user profile and modify a user password.
Check user lock status.
Views the information of the current logged-in user, and log out a logged-in
user if necessary.
Blacklist management: the users added to a blacklist cannot log in to the
system.
Sets a validity period for a user account.
Sets the validity period for a password.
Sets the working time, holiday, login IP range, and login MAC binding for a
user.
Sets concurrent login number for one user.
Sets the maximal and minimal length of a password.
Sets account lock upon login failure.
Sets automatic lock function.
Function Description
Operation log Saves user's access information, including the accessed function module,
operation process, operation time, and operation result.
System log Saves the operation information of the system or a module, for example,
when the system is started and turned off, the operation status of all
modules, system interruption, and module interruption.
3-4
Function Description
Function Description
Unified Report View The system provides a unified report view, including performance report
and alarm report.
Report Task Report task management generates reports periodically. The time and
Management report type can be set.
Report File Reports can be previewed, printed, and saved as Excel, Html, PDF, or
Management CSV files.
3-5
3-6
Clients include local clients and remote clients. They provide a GUI for operating and
monitoring NEs. Clients are connected to the server through the LAN or an MAN. These
two types of clients have the same operation capability.
4-1
4-2
4-3
The servers of the NetNumen U31 are operating on different machines. They operate
with each other to manage the devices on the entire network. Distributed deployment is
suitable for a large-scale network. Moreover, it is suitable for networks that will grow both
in scale and complexity.
4-4
Server-1 manages devices in domain 1 and server-2 manages devices in domain2. The
superior server-3 manages the two domains simultaneously.
4-5
4-6
Note:
The products with their names in red are not managed by U31 (Wireline).
4-7
The NetNumen U31 uses the unique PPU component technology that allows
carriers to determine the functions integrated into the EMS. This feature enables
ZTE to customize an EMS to meet the individual business needs of a carrier.
Furthermore, a variety of deployment schemes are available, and carriers can
find the very one for their current O&M mode. ZTE aims to help carriers drive up
their ROI.
Three access methods are available: GUI, Web, and CLI to support the local and
remote access requirements. O&M personnel can get access to U31 anytime
anywhere.
l Flexible system architecture for smooth evolution
Modular design for easy rollout of new services: The modular architecture
brings good scalability to U31, which allows only small adjustments for growth in
services or changes in NE management. Investment is protected, and customer
requirements in the future can be met.
Distributed deployment and flexible investment: Distributed deployment allows
a minimum investment when carriers are to build a network. The network
management capacity can be expanded flexibly if the network scale is growing.
Open interfaces for fast integration with third-party systems: A variety of
northbound interfaces are provided, which allows the integration of the NetNumen
U31 with third-party NMS/BOSS systems, such as IBM Tivoli Netcool/OMNIbus,
HP TeMIP, and Aircom Optima.
4-8
l Support multiple vendors IT devices and quick scalability to bring high customer
satisfaction
l Integrate with the U31 system to share resources and reduce investment costs
l Provides a uniform GUI and combined management capability to ensure high
management efficiency and service QoS.
l Provides carrier-class reliability, usability, and security
l Deployed independently or operated with the NetNumen U31 to meet the needs of
networks of different scales.
4-9
4-10
5-1
5-2
5.2.6 DB Interface
DB views are a transformation of database data, allowing users to retrieve database table
data in another way. Through this interface, NMS can query the data view in EMS by using
the uniform username and password, implementing integration between NMS and EMS.
5-3
5-4
Standard Design Complies with the IEC 60297-2 standard, and uses modular
standard design that facilitates capacity extension and maintenance.
Heat There are ventilation holes on the front door, back door, and
dissipation baseplate of the cabinet. The percentage of opening is 56%, so
the cabinet provides high heat dissipation performance.
6-1
Process Wiring design There are wiring holes at the top and bottom of the cabinet. The
specifications cabinet supports top routing and bottom routing.
The NetNumen U31 server can be a SUN-series server or ATCA blade server (with an
E4140 shelf). For the technical parameters of the E4140 shelf, refer to Table 6-2.
Standard Design 19-inch standard 14U shelf, complies with PICMG 3.0 R2.0.
standard
Empty-cabinet 35 kg.
weight
Full- 77 kg.
configuration
weight
Start Time used for starting a 7 seconds. Period from the time when a client is
speed client for the first time started for the first time to the time when
the dialog box for login is displayed.
Time used for logging in to 7 seconds. Period from the time when a client is
a client for the first time logged in to for the first time to the time
when the main page is displayed (not
including the time used for obtaining data
in the topology view).
Time used for starting a 2 seconds. Period from the time when a client is
client started not for the first time to the time
when the dialog box for login is displayed.
6-2
Time used for logging in to 3 seconds. Period from the time when a client is
a client logged in to not for the first time to the
time when the rack diagram is displayed
(not including the time used for displaying
the topology view). For a Citrix scenario,
every login is considered as the first
login.
Time used for switching 1 second. Time used for switching views, module
views or windows on a windows, and NE windows that have be
client opened on a client.
Time used for starting the 2 seconds. Time used for opening a subview on
command terminal the command terminal through EMS
commands, not OMM commands (OMM
commands are loaded on the back end,
and the time varies with the size of the
OMM version file).
Time used for starting the 5 minutes. If there are multiple processes on the
server server, this index refers to the time
used for starting these processes on the
server.
Opera- Operation interaction When a user performs an The system responds to an operation
tion re- between users and the operation in the system, for within 1 second. For an asynchronous
sponse EMS example, starting the client, the operation, the system sends an
system responds within one asynchronous command successfully
second. If the response time within 1 second. The time used for
is more than one second, the executing the command is not included in
system provides a response the response time (for an asynchronous
indication, for example, the command, the execution time is long).
arrow of mouse becomes a
funnel. If the response time is
more than five seconds, the
system provides a progress
bar.
6-3
Time used for querying 2 seconds. When a user queries 50,000 historical
logs logs among 1,000,000 historical logs,
the query results on the first page
are displayed within 2 seconds, and
all results can be retrieved within 30
seconds.
Time used for querying 2 seconds. Period from the time when the query
active alarms parameters are set to the time when
query results are displayed on the first
page (the alarm report speed is 50
alarms per second, and active alarms
are queried on less than 10 clients
simultaneously). If the active alarm
threshold is 20,000, the time is less than
or equal to 2 seconds. If the active alarm
threshold is 100,000, the time is less than
or equal to 5 seconds.
Time used for querying 5 seconds. When a user queries 50,000 historical
historical alarms alarms among 5,000,000 historical
alarms, the query results on the first
page are displayed within 5 seconds,
and all results can be retrieved within
30 seconds. If this index cannot be met
in some situations, the system sends a
prompt message through a dialog box or
progress bar.
Time used for querying 5 seconds. When a user queries 100,000 records
performance information among 5,000,000 records, the query
results on the first page are displayed
within 5 seconds, and all results
can be retrieved within 60 seconds.
Performance query operations mean all
operations related to performance data
query, including performance information
browsing. If this index cannot be met
in some situations, the system sends a
prompt message through a dialog box or
progress bar.
Time used for displaying 2 seconds. Time used for displaying basic
the rack diagram information about the rack and boards in
the diagram. The time used for retrieving
6-4
MML command response 2 seconds. Period from the time when a MML
time command is sent to the time when the
result is returned. Operation response
processing complies with the Operation
interaction between users and the
EMS index.
Time used for 5 seconds. The time that the EMS uses to
synchronizing alarms successfully send a single-NE
on a single NE alarm synchronization command (an
asynchronous operation) is less than or
equal to 1 second.
Time used for 60 seconds. The time that the EMS uses to
synchronizing alarms successfully send an entire-network
in the entire network alarm synchronization command (an
asynchronous operation) is less than or
equal to 3 seconds.
Dialog box and button 1 second. Time used for responding to an operation
response time performed through a menu or button
Menu (including shortcut 1 second. Time used for displaying a shortcut menu
menu and drop-down list) or drop-down list.
and shortcut key response
time
6-5
Time used for getting 2 seconds. Period from the time when a user presses
online help (in Topology, F1 in a module to the time when help
Fault, Security, information is displayed (if the user uses
Configuration, and Tools help for the first time, the period is 3
modules) seconds. If the size of the help file is
large, for example, the file contains a lot
of figures, the period may be more than
3 seconds).
Time used for getting MML 2 seconds. Period from the time when a user click
command online help the help tab on an MML page to the time
when help information is displayed.
Time used for turning 1 second. When a user browse data by pressing
pages turning to browse the PgUn (or PgDn) button or dragging
information (including the scroll bar, the windows do not flicker
alarm information, or fail to respond, and the scroll bar is
tracing information, MML smooth.
returning information, and
performance information),
selecting a node in a tree,
and switching windows
Alarm report delay 2 seconds. Period from the time when alarms
are uploaded through the northbound
interface to the time when the alarms
are received in the upper-layer network
management system.
Re- CPU usage of a client 65%. CPU usage of a client The period when CPU usage exceeds
source does not exceed 65% for a long 90% due to instantaneous peak traffic
usage period. must not be more than 10 seconds.
If CPU usage is increased due to an
operation, the CPU usage should be
reduced to a normal value after the
operation processing is completed.
CPU usage of the server 70. CPU usage of the server in lightly loaded
conditions or normal conditions (for
example, at least ten NEs download
software version file simultaneously, or
6-6
Man- Maximum number of NEs 50, 000 equivalent NEs (bearer For conversion between NE types and
agement managed by the system network). equivalent NEs, contact ZTE technical
capabil- 100,000 equivalent NEs (fixed supports.
ity network).
Maximum number of NEs 8,000 physical NEs (bearer Information about the NetNumen U31
managed by a single network). operation on a single server. The
server 40, 000 equivalent NEs (fixed configuration of the server is equal to or
network). higher than the hardware configuration
for network scale 6.
Alarm processing capacity Active alarm processing Total number of alarm generation
capacity: 100,000 alarms per messages and alarm clearance
second. messages processed per second.
Historical alarm processing
capacity: 10,000,000 alarms
per second.
During normal system
operation, the alarm processing
capacity is equal to or more
than 150 alarms per second.
The peak alarm processing
capacity is equal to or more
6-7
Performance processing Database storage efficiency: The system operates properly and stably.
capacity 300 per second. CPU usage and memory usage of the
server is normal.
Period when report data is Alarm data: 120 days. The original performance data table is
retained Original performance data: 90 retained for 30 days, hourly tables are
days (granularity: 15 minutes). retained for 90 days, and daily tables are
Report data: 13 months. retained for 180 days. The maximum
size of report data is 1.5 GB.
The period when report data is retained
can be modified based on the server
configuration.
Minimum bandwidth 32 kbps 256 kbps. l If the Citrix solution is used, the
between a client and the minimum bandwidth is 128 kbps.
server l If the Coolbit solution is used, the
minimum bandwidth between a
Coolbit browser and Coolbit server
is 32 kbps.
l If the Citrix solution or Coolbit
solution is not used, the minimum
bandwidth is 256 kbps.
l If the PSTN solution is used and
the client uses the Web mode, the
minimum bandwidth is 64 kbps.
6-8
Availability 0.99992. -
Time used for recovering 10 minutes. In bearer networks, the time used for
configuration data backing up configuration data is less than
5 minutes, and the performance archive
efficiency is greater than 6000 pieces per
second.
Time used for recovering 40 minutes. Time used for recovering data through
all data dual-server cluster software when a
server fails.
Time used for recovering 1.5 hours. Time used for recovering data and
the database and network operating the network management
management software system through dual-server cluster
software when a server fails.
Time used for switching 7 minutes. Time used for switching the active
the active and standby and standby servers automatically or
servers manually (The stop processes is stopped
with a 1-minute delay, the server is
started within 5 minutes, and the VCS
uses 1 minute for switching).
Backup and restoration The complete backup data is All servers in the system can be backed
retained for two weeks, and up, including the standby server. The
the incremental backup data is SAN backup mode is supported.
retained for one week.
Complete backup is performed
once a week, and incremental
backup is performed 6 times a
week.
6-9
Unified PDU - 10 W
6-10
Parameter Specifications
Parameter Specifications
7-1
l Central grounding mode: The working ground, protection ground and building
lightning ground for various communication equipments share a group of grounding
body.
The grounding resistance largely depends on soil types.
For areas with poor soil conditions, it is allowable to add some additive chemicals
around the grounding markers to reduce soil resistivity and contact resistance.
Variations of temperature and humidity also make the grounding resistance
change.
If the temperature is below 0 and humidity is much lower, grounding resistance
also varies greatly. In this case, bury ground markers deep into the soil and add
additive chemicals to satisfy requirements of grounding resistance.
Grounding markers should use angle irons with a length smaller than 2 m. If
conditions permit, it is recommended to use grounding nets.
Copper-coin connection cables must be used to connect grounding markers to
grounding bolts attaching to main equipments. The sectional area cannot be less
than 50 mm2. The cable length should be as short as possible, and sectional area
of copper cables should be extended if the cable length exceeds 50 m. Both ends
of connection cables should be coated with tins or soaked with hot tins. Moreover,
remove coating materials, varnishes, paints and oxidation layers away from fixing
points. This is to ensure good contact between metallic surfaces.
For all grounding junction pieces, corrosion protection is necessary. Use a
mechanical way to secure grounding bolts so that lower resistance connection
can be guaranteed.
l Ensure that the grounding resistance is less than 1 ohm. Additionally, several factors
should be considered, such as soil conditions, grounding body resistance, grounding
cables, and so forth.
l Prior to commissioning equipments, grounding resistance should be measured
precisely.
If the grounding resistance does not meet requirements, commissioning should be
delayed. Customers that still insist commissioning should present a written instruction
and make promises to bear responsibility for any problems caused by grounding.
Then, commissioning can be proceeded if ZTE Cooperation approves.
7-2
l If the temperature exceeds the normal temperature by 10, the equipment lifespan
is approximately shortened by fifty percent.
l In the case of much lower temperature, the performance of optical components and
crystal components cannot be guaranteed.
l Much higher humidity in a long term will result in degraded insulation performance of
insulating materials and even leakage; and then all kinds of metallic components for
the equipments are corroded.
l Much lower humidity in a long term will result in drying shrinkage of insulation
gaskets; and then connections of fastening bolts become loose. This will easily
lead to discharge of strong static electricity and damages to CMOS circuits within
equipments.
Temperature and humidity in the equipment room should satisfy following requirements as
listed in Table 7-3.
5 to 40 5 to 50 5% to 85% 5% to 90%
Short-term operating conditions refer to that the successive operating time is not more than 96 hours
and the accumulated operating time per year is not more than 15 days.
7-3
7-4
7.7 Illumination
Illumination in the equipment room should satisfy the following requirements.
l Install incandescent lamps or configure emergent lightning equipment in proper
places between racks to facilitate equipment installation and maintenance. However,
long-term, direct sunshine or light should be avoided to prevent the circuit boards
and other components from aging and deforming.
l It is recommended that use color glasses and non-transparent curtains for windows.
l Use the daylight lamps installed into the ceiling for the main body of the equipment
room. The average illumination between 150 lx~250 lX is recommended.
7-5
Neither the main equipment room nor the accessory equipment room should have
flammable and explosive materials placed inside. Warning boards bearing No Smoking
or Smoking prohibited shall be located in notable places. Prepare for effective
fire-protection appliances and put them within the reach. Install effective fire protection
water equipments in proper locations.
The water in store should suffice continuous fire-fighting for two hours. But the supplying
pipes (drainage pipes and rain pipes) should not traverse the equipment room; neither
shall the fire hydrant be placed in the equipment room.
7-6
ITU-T Proposals
l ITU-T M.3000, Overview of TMN recommendations
l ITU-T M.3010, Principles for a Telecommunications management network
l ITU-T M.3016, TMN security overview
l ITU-T M.3020, TMN Interface Specification Methodology
l ITU-T M.3100, Generic Network Information Model
l ITU-T M.3101, Managed Object Conformance Statements for the Generic Network
Information Model
l ITU-T M.3200, TMN management services and telecommunications managed areas:
overview
l ITU-T M.3300, TMN F interface requirements
l ITU-T M.3400, TMN Management Function
l ITU-T Temporary Document 69 IP Experts: Revised draft document on IP access
network architecture
l ITU-T X.701-X.709, Systems Management framework and architecture
l ITU-T X.710-X.719, Management Communication Service and Protocol
l ITU-T X.720-X.729, Structure of Management Information
l ITU-T X.730-X.799, Management functions
RFC Proposals
l RFC1157, Simple Network Management Protocol
l RFC1213, Management Information Base for Network Management of TCP/IP based
internets: MIB-II
l RFC1901, Introduction to Community-based SNMPv2
l RFC1902, Structure of Management Information for Version 2 of the Simple Network
Management Protocol SNMPv2
l RFC1903, Textual Conventions for Version 2 of the Simple Network Management
Protocol SNMPv2
l RFC1905, Protocol Operations for Version 2 of the Simple Network Management
Protocol SNMPv2
l RFC2037, Entity MIB using SMIv2
l RFC2233, The Interface Group MIB using SMIv2
l RFC1558, A String Representation of LDAP Search Filters
l RFC1777, Lightweight Directory Access Protocol
l RFC1778, The String Representation of Standard Attribute Syntaxes
8-1
TMF Proposals
l GB901, A Service management Business Process Model
l GB921Enhanced Telecom Operations Map
l GB909 Generic Requirements for Telecommunications Management Building
Blocks
l GB908Network Management Detailed Operations Map
l GB914System Integration Map
l GB917, SLA Management Handbook V1.5
l NMF038, Bandwidth Management Ensemble V1.0
l TMF508, Connection and Service Management Information Model Business
Agreement
l TMF801, Plug and Play Service Fulfillment Phase 2 Validation Specification V1.0
l TMF605, Connection and Service Management Information Model
l NMF037, Sub-System Alarm Surveillance Ensemble V1.0
OMG Standard
l Interworking Between CORBA and TMN System Specification V1.0
8-2
II
III
IV
DB
- Database
DDN
- Digital Data Network
EMS
- Element Management System
FTP
- File Transfer Protocol
GUI
- Graphical User Interface
IE
- Internet Explorer
IETF
- Internet Engineering Task Force
IP
- Internet Protocol
ISDN
- Integrated Services Digital Network
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
J2EE
- JAVA 2 platform Enterprise Edition
JRE
- Java Runtime Environment
LAN
- Local Area Network
LCT
- Local Craft Terminal
MAC
- Media Access Control
MAN
- Metropolitan Area Network
MIB
- Management Information Base
MML
- Man Machine Language
MTBF
- Mean Time Between Failures
MTOSI
- Multi-Technology Operations System Interface
MTTR
- Mean Time To Recovery
NE
- Network Element
NMS
- Network Management System
OAM
- Operation, Administration and Maintenance
OMG
- Open Mobile Gateway
OMM
- Operation and Maintenance Management
OPEX
- Operating Expenditure
ORB
- Object Request Broker
VI
OSS
- Operation Support System
PDU
- Power Distribution Unit
PM
- Performance Management
PPU
- Protocol Process Unit
PSTN
- Public Switched Telephone Network
QoS
- Quality of Service
RPO
- Recovery Point Objective
RTO
- Recovery Time Objective
SAN
- Storage Area Network
SFTP
- Secure File Transfer Protocol
SNMP
- Simple Network Management Protocol
SSH
- Secure Shell
TL1
- Transaction Language 1
TMF
- Telecommunication Management Forum
TMN
- Telecommunications Management Network
VCS
- Virtual Cluster System
VII