Documente Academic
Documente Profesional
Documente Cultură
Description
V4
NetNumen U31(CN) Product Description
Contents
1 Overview ......................................................................................................... 1
7 Functionality ................................................................................................. 24
7.1 Fault Management .......................................................................................... 24
7.1.1 Fault Collection ............................................................................................... 24
7.1.2 Fault Display ................................................................................................... 25
7.1.3 Alarm Acknowledgement and Un-acknowledgement ...................................... 25
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. III
NetNumen U31(CN) Product Description
9 Reliability ...................................................................................................... 50
9.1 System Reliability ........................................................................................... 50
9.1.1 Data Security .................................................................................................. 50
9.1.2 System Security.............................................................................................. 51
9.2 Hardware Reliability ........................................................................................ 53
9.3 Software Reliability ......................................................................................... 55
9.4 Principle for Network Bandwidth ..................................................................... 57
9.4.1 Bandwidth Calculation between U31(CN) Server and NMS ............................ 57
9.4.2 Bandwidth Calculation between U31(CN) Server and Client ........................... 58
9.4.3 Bandwidth Calculation between U31(CN) Server and NE ............................... 58
11 Appendixes ................................................................................................... 61
11.1 ZTE-Joined Standard Organizations ............................................................... 61
11.2 Acronyms and Abbreviations .......................................................................... 62
FIGURES
TABLES
1 Overview
NetNumen U31(CN) (hereafter, U31(CN) is used) system is built on a unified NM platform
of ZTE, provides centralized management for all kinds of core network equipment of
GSM/WCDMA/TD-SCDMA/CDMA/Wimax/EPC, such as MSC, MSC Server, MGW, HLR,
SGSN, GGSN, MSCe, PDSN, AGW, AAA, MGCF, MME, SGW/PGW, DRA,TWAG and
CG.
U31(CN) is located in EMS layer of TMN model, and provides northbound interface such
as FTP File, CORBA, SNMP and MML.
2 Highlight Features
3 System Principle
Designed on TMN (Telecommunication Management Network) concept and operating
mechanism proposed by ITU, U31(CN) system satisfies the architecture and function
requirements of TMN. U31(CN) system is in the EMS layer of the TMN, and provides a
part of functions of the NMS layer.
As shown in the figure below, the functions of TMN are classified into five layers, from
upper to lower layers, namely: Business management layer, Service management layer,
Network management layer, Network element management layer and Network element
layer in sequence. U31(CN) system is located in Network element management layer,
and includes a part of functions of Network management layer. The layers directly related
to U31(CN) system include Network management layer and Network element layer.
MO
Q3
Agent
Service management layer
Manager
MO
Q3
Agent
Network management layer
Manager
MO
Q3/Corba
Agent
Network element management layer
Manager
MO
Qx
MO
The business management layer consists of management functions that support the
decision of the entire enterprise, such as generation of economic analysis reports and
quality analysis reports, and setting of tasks and objectives. Its user is the top-level
administrator of the telecom operator.
The service management layer comprises functions of service provision, service control
and monitoring and service-related charging processing, which involves such services as
telephone switching services, IN services, mobile communication services and leased
data line services. Its user is the service operation administrator.
The network element management layer implements operation and management of one
or more NEs, such as remote operation and maintenance of the switches and the BSCs,
and equipment software and hardware management. It is not responsible for the issues
between the NE management layer and the NE. Its user is the equipment O&M operator.
The Network element layer is a network factor in the telecom network, realizing basic
functions of the telecom network. It plays a managed role in the network management,
providing original data of network management. In the WCN, the network elements
include MSC, MSC Server, MGW, HLR, SGSN, GGSN, and CG.
TMN specifies that, the layers are interconnected with each other by Qx interface, and
the CORBA interface may be employed, and the CORBA/MML interface to the upper
NMS. Along with the TMNs developing, the CORBA interface with simple realization,
unified standard and object-oriented structure, has become the mainstream interface
between the NMS layer and EMS layer.
U31(CN) system provides standard management functions defined by the TMN system,
i.e., security management, fault management, performance management and
configuration management, etc. For the ease of use, it provides functions of log
management and report printing. In addition, it provides many supplementary tools in the
NE layer (some of the tools are optional, i.e., not included in the standard software
configuration of the system. The following is the same).
U31(CN) system realizes functions of Network element management layer and a part of
functions of the Network management layer in the TMN. It is to make centralized
management, monitoring and counting on the NE devices of the lower layer. The higher
the management layer is, the weaker the function of the NE operation and maintenance
is, and meanwhile, the function of the network centralized management is stronger.
U31(CN) system adopts the general architecture of J2EE, and uses the excellent idea of
JDMK (Java dynamic management tool set).
4 System Architecture
P
NMF
l
Application
a
NetNumen U31(CN) t
NAF f
o
r
m
WSF OSF
NEF
MIF
Work Station Function WSF: responsible for the friendly presentation of the NE
information to user in the form of letter and graphic interface. Meanwhile, it transfers
the operation of the operator to the Operating System Function (OSF). OSF
organizes the application logic handling of the operation. WSF realizes the interface
G and interface F in the TMN, among which interface G is man-machine interface,
and interface F is the interface between WSF and OSF.
Operating System Function OSF: handling the information related to the application
of NE management, supporting and controlling the realization of NE device
management function, and including several system management application
functions, i.e., fault management, performance management, security management,
configuration management.
NE Function NEF: the managed network devices of various kinds, such as MSC
Server, SGSN, HLR.
Northward interface Access Function NAF: the access agent function of upper layer
NM system NMF, providing four kinds of access interfaces, MML, CORBA, DB and
SNMP. Through the agent function, it can realize the accessing of management
applications, to implement the network layer management functions of the integrated
NM system.
The operating system platform of U31(CN) system may select Windows NT/2000 or
Sun Solaris, realizing the platform non-relativity through JVM. The database system
can be purchased according to the users needs. The employed database is
suggested to be ORACLE;
It is allowed that some functions are not installed in the system (for example,
performance management is not installed), and other functions can run normally (the
basic functions such as configuration must be installed).
NMS
Manager Network Management
Center
CORBA/FTP/SNMP/ MML
U31(CN)
WSF Manager
U31
F Agent
Agent Agent Agent Layer
Qx Qx Qx Qx
NE Layer
NE NE NE NE
U31(CN) server
Fault Configuration Security Topology Performance
management management management management statistics
Local
LMT LMT LMT LMT LMT
maintenance
5 Networking Structure
Remote Client
DCN
Remote DB Backup
Core Network
The above figure shows the networking of a local area network. If the network condition is
complex and the network crosses different areas, networking by area is recommended.
There is another remote networking scheme named Reverse. In this case, the reverse
client only can manage local NEs through the remote U31(CN) server, as shown in
Figure 5-4:
DDN mode has a high speed and stable transmission. Its bandwidth is from 64kbps to
2Mbps with routers and modems. It is shown in the Figure 5-5 as follows:
Note: the rented DDN speed rate depends on the bandwidth, and the needed bandwidth
is calculated by the number of remote RNC and clients.
5.3.2 E1 Mode
HDSL (High-data-rate Digital Subscriber Line) has modems on two ends of one or more
twisted pairs. HDSL provides a symmetrical transfer rate; viz. the UL rate is equal to the
DL rate. The effective transferring distance can reach 5km by only one twisted-pair.
However, if HDSL is not stable, it is not recommended to be used in the network, with
reference to Figure 5-7:
Notes: Nowadays, HDSL has been updated to G.SHDSL. If G.SHDSL is used, the HDSL
modem above will be replaced by SHDSL modem. Its spec. type is ASMi-52 product.
6 Hardware Structure
Normally, U31(CN) shares the rack with other NEs, which are based on ZTE ETCA
platform.
U31(CN) ETCA shelf follows PICMG3.0 standard, and the form factor is
619.5mm*482.6mm*415mm (H*W*D). U31(CN) shelf uses dual-insert structure, which is
based on ETCA architecture. There are 14 slots, Slots 1~6 and 9~14 are only used for
installing the blade server and Slots 7~8 are only used for installing switching network
boards.
SWB is ETCA switch sub-system developed by ZTE, which realizes Giga Ethernet
switching function of system BASE and FABRIC plane, and provides 16 GE inter-shelf
cascade ports by backboard externally.
OPB board provides 4 GE electrical ports and 1 RS232 port is provided by back board.
IPMB0
IPMB1
ETCA plug-in box has an intelligent hardware management system based on IPMI
specification. CMM board realizes physical resource management and monitoring of
manageable equipment in ETCA plug-in box, provides out-of-band system management
interface for external or embedded system manager to realize bottom management of the
entire system. CMM is the managing center of ETCA plug-in box; it is responsible for
power-on control, status management, sensor data management of whole plug-in box.
CMM is the key equipment for other suppliers ETCA boards to realize interconnection
and interworking test. IPMC controller connects with boards by IPMB and makes them
work under IPMI architecture management. It mainly fulfills monitoring, control and
management of ETCA boards or key hardware resources of other shelf components; it
also communicates with CMM by intelligent IPMB, reports various events to CMM and
accept management and control from CMM.
Serdes Update
Serdes Base 0
Serdes Base 1
Serdes Fabric 0
Serdes Fabric 1
Internal Fabric consists of Base Channel Network, Fabric Channel Network, Update
Channel Network and Clock Synchronization Network.
Products follow ETCA standard system design, including power supply input and
distribution, engine structure, system intelligent management, backplane topological
structure, connector, optical/electric channel, switch function and I/O interfaces.
Easy-to-expand
It can improve products operating performance by addling blade server or cascade shelf;
it supports smooth upgrading and expansion.
Highly-reliable
Redundancy Protection
Provide redundancy protection for key functional modules, when there is some
fault, system will automatically switch to backup modules.
CMM supports 1+1 active & standby redundancy protection, and automatic data
synchronization between active and standby modes.
Fault-tolerance
Provide anti-reverse connection for power supply and isolation design for power
fault.
Fault management
FRU unit realize fault detection and report by its IPMC module.
Provide fault detection for fan plug-in shelf and access power supply module.
Easy-to-maintain
6.3 Reliability
U31(CN) adopts ZTE new-generation V4 platform, it uses ETCA architecture, and strictly
follows telecom equipment standard, and perfect design in tele-magnetic compatibility,
over/under-voltage protection, ventilation and heat elimination, intelligent management,
which effectively ensures system reliability and stability.
U31(CN) also adopts IP-SAN disc array for data storing, and this disc array adopts
RAID5+hotspare technology, to ensure data security.
U31(CN) system adopts 1+1 active & standby for all boards, system performs automatic
detection for important resources (network interface, hard disc, etc) of boards, switch
automatically for boards fault and alarm, which effectively ensures system reliability.
U31(CN) uses commercial IP-SAN disk array, which is capable of hard disc capacity
expansion and is convenient for operators to expand capacity.
U31(CN) adopts dual network ports to make a redundancy of key links such as links
connected with core network NEs and link among GES switchboards, which guarantees
the security of transmission.
7 Functionality
The abnormal statuses generated by the NE will generate alarm information. The
information includes serial number (sequence number), alarm type, alarm severity, the
NE generating the alarm and location information, alarm generating time, and alarm
reason. The alarm information details are shown in the following table.
The client of the fault management displays current alarm situation of the NE. The alarm
information, which can be displayed, includes all the contents collected in the fault
collection.
The way of viewing alarms include list way and rack diagram way. The rack diagram way
displays the physical location and level of each alarm by showing the real rack physically.
The alarm list and rack diagram can differentiate different levels of alarms by colors.
In the list way, a user can sort alarms according to any displayed information category,
for example, serial number (sequence number), alarm type, time information, location
information, and alarm status sequence, which is convenient for comparing and handling
the alarms. Additionally, current alarms and history alarms are separately displayed.
The alarm and its recovery information are sent to the topology management interface for
displaying. Meanwhile, they are sent to the alarm box for broad and attractive displaying.
All the displayed information will be influenced by the user setting, such as alarm filtering
and re-definition information set by the user.
The alarm acknowledge/un-acknowledge are convenient for maintenance staff. When the
alarm is found and maintenance staff has taken some measures, if this alarm need not be
observed any more, the maintenance staff can set the alarm status as Acknowledged;
after the alarm is acknowledged, if it is found that this problem has not been solved yet
and needs to be observed again, the maintenance staff can set the alarm status back to
Un-acknowledged.
The normal user with alarm operation right can only un-acknowledge his/her own alarm.
Admin users can un-acknowledge all the alarms.
Alarm clear can clear one alarm data from network equipment and network management
system. This function is used when the manual clearing is needed since alarms cannot
be resumed due to some reasons. When the network management system cannot
connect with the alarmed equipment, the alarm clear operation will fail.
When the link is recovered between client and server, client will automatically
synchronize with server.
The broken link between front end and foreground equipment is recovered.
2. Manual synchronization
When a user finds the alarm data of NM system may be different from the network
equipment, Manual synchronization can be used on client to synchronize the alarm data
of specific network equipment.
Alarm manual forward function is to forward the alarms in system by email or SMS to the
maintenance staff.
Alarm data export function is to export all alarm data in alarm view to files. The supported
file formats include: TXT, EXCEL, PDF, HTML, CSV, etc.
When server receives the alarm and notification message, it will decide the processing
manner according to the predefined rules. The rule customization function on client can
conveniently view, modify, and delete the rules in server, or create new rules and submit
them to server. All the rules are available only for the alarms and notifications generated
after these rules are created.
The system equipment summarizes some alarm handling experiences after the long-time
operation as a reference for the similar problem in the future. The summary of these
handling experiences is the alarm handling suggestion.
The alarm handling suggestion interface displays the alarm system type index. For each
alarm, the system provides the default handling suggestion. Users can record the
handling suggestions according to their experiences. These alarm-handling suggestions
can either be imported or exported. The file formats include Excel, PDF, HTML, and Txt.
Fault management module allows users to modify parameters related with alarms:
Alarm box setting: to set a series of actions after the alarms are sent to the alarm box. For
example, voice alarms are only generated for Class one or Class two alarms.
Alarm color setting: different alarm classes have corresponding colors in client interface.
Users can set the corresponding relationship between the alarm class and color
according to their own situation.
The user can obtain various detailed and desired fault information by fault browsing.
The user can set various alarm browsing conditions, including location of device, alarm
level, current alarm status, alarm type, fault reason, time of alarm generating, recovering
and confirming.
The browsing result can generate a report, which can be printed or saved as a file.
The user can count the current alarms and history alarms of the system in frequency. The
statistics result can be used as the basis for analyzing system faults. The statistics can be
made according to the alarm time, alarm type, alarm level, and NE where the alarm
occurs. The statistics filter condition can be set by alarm location, alarm level, alarm
category, alarm time, and status. The statistics result can be shown by a diagram.
Event (notification) can be viewed by the list way, and can be queried.
The alarm box is usually placed at an outstanding position of the NM equipment room,
and displays various faults of the system in the form of sound and light to remind
maintenance personnel to focus on and handle the faults.
Moreover, the alarm box can send the alarm information to the maintenance personnel
who have mobile phone and email address in the form of short message and email, so
that the maintenance personnel will not miss important alarm information when he is not
in the equipment room.
U31(CN) fault management system provides the function of alarm box setting, including
the setting of short message user and the setting of alarm box parameters. The
information of the maintenance personnel and what level of alarm will be sent to the
personnel may be set, controlling the alarm level sent to the alarm box and the sound &
light displaying situation.
Display the NE devices as a tree in the interface, and the navigation tree is formed. The
topology map and the node of the navigation tree are in one to one correspondence. The
navigation tree and the topology view are synchronized with each other. The navigation
tree provides navigation function to the topology view, and the topology map displays the
nodes of the related layer of the selected node in the navigation tree. The node of the
navigation tree provides the functions related to the node, such as viewing the property,
modifying the NE information, counting the sub nodes.
The topology map of U31(CN) provides the panorama display of the device topology
structure of the whole network. The NE device can be quickly located in the topology map.
The topology map employs the coordinates of longitude and latitude, supporting
geographical information system. The icon of NE device can be displayed in the actual
geographical location of the map. The user can lock the setting of the NE device icon, so
that it cannot be moved to other position, and can be moved only when it is unlocked. The
node icon of the topology map can display the statistics information of the NE device,
such as NE number under the node, link number, group number, and alarm information.
U31(CN) system supports moving the whole map, zooming in by each level, zooming out
by each level, back to the original, whole view display, and partial zooming in. It supports
forwarding and rewinding of browsing the topology map layers, and locating to any
browsed map layer, and finding a specified NE device in the topology map. It supports
changing background map of the topology. It can be configured as world map and China
map to realize the NE device management of a large scope. In addition, it can be
configured as a local area map and equipment room display map, so that the display of
topology view is more human.
After the data synchronization of U31(CN) system is finished, the client will be refreshed,
ensuring that the topology data are consistent with configuration data, while the relation
of NE devices set in the topology map will not be influenced. The topology management
module can set the layout way of NEs in the topology view, and deploy the display of NEs
according to the set layout way. The layout includes five ways: cascading layout, tree
layout, actinomorphic layout, explosion layout, and equidistant layout.
The topology view of U31(CN) system can use NE, group, link set, group name, NE
name, link number prompt to build a filter tree to filter the topology view, and it can
implement the filtering directly according to the NE name input by the user.
U31(CN) system does not display the NE node and topology management module that
the user is not authorized to operate, improving the security of the system and being
convenient for the user to use at the same time.
The icon of NE device/links between NEs in U31(CN) system can display the color of the
highest level alarm in the corresponding physical devices. In addition, it can prompt the
number of each alarm level and confirm the status. Additionally, the function of querying
alarm and notification is provided.
U31(CN) system provides the function of creating virtual NE/virtual link. The user can set
the NE to indicate peripheral device or device node, or set virtual link to indicate that two
NE nodes are interacted or interconnected.
The grouping nodes are logic nodes defined by the user, and distributes the NE devices
of physical view to the grouping nodes.
The data configuration function of U31(CN) system supports the data configuration
function of various NEs, including the creating, deleting, modifying and querying of
configuration data. It manages various NE data in a centralized way, and saves multiple
sets of configuration data of NE. It supports the function of batch creating and related
creation of the configuration data. The configuration of U31(CN) system is organized in
the way of tree structure, convenient for the user to select and browse in the configuration
object visually.
The configuration of U31(CN) system supports the following parameters and contents:
Configuration of physical resources: physical resources refer to the physical entity of the
NE devices and their relation, mapping relation, such as the situation of rack, chassis,
slot, ant port, and the connection situation of each physical entity. Name of physical entity:
number and working mode are configured in the physical resources configuration too. It
provides a real rack diagram for configuration, convenient and visual.
The modification of the configuration will perform the consistency check, ensuring that no
error occurs in the configured data of the system.
The modification on the configuration parameters made by the user will be recorded in
the log in detail, convenient for tracing the configuration modification later. It includes the
name of operator, modification time and the information of parameter value before and
after being modified.
It is possible to export the current configuration data of the NE to a plain text file (xls, xml),
and supports configuring the NE by importing a plain text file (xls, xml).
The dynamic data management of U31(CN) system provides the function of observing
and managing the resources such as circuit, signaling link, route office direction, Sigtran
coupling, AAL2 path.
The data transmission of U31(CN) system can synchronize the configuration data in the
NE. The transmission schedule can be displayed at the client, and the detailed
transmission log can be recorded.
U31(CN) system provides the version control function to manage the software running in
the NE. Including the functions such as file management of software version, version file
downloaded to NE, NE uploading version file, and software version querying. Through
software version management, it is convenient to upload NE software, control NE
software version, and obtain NE software information.
When discovering the downloaded software version runs abnormally, you can roll over
the version to the original one. To shorten the upgrade time, U31(CN) provides batch
downloading and distribution to improve the efficiency.
The Intelligent script tool provides the simple Project Dynamic Script Language and an
integrated development environment for script editing, debugging, and running.
Meanwhile, this tool can also connect to NEs and send MML commands to them.
U31(CN) can publish scripts to the server by this tool so that the scripts can be executed
on the server, and U31(CN) also can create timing tasks by this tool. U31(CN) can use
the Intelligent script tool and compile project dynamic scripts for repeated maintenance
work realizing automation maintenance work and improve efficiency. Script management
consists of script file operations, script debugging, and script running. Script projects
which are published to the server can be executed regularly by timing tasks.
QoS task management includes the functions such as creating, deleting, querying,
modifying the QoS task, activating/suspending QoS task, deleting expiring task, detecting
and identifying QoS task when configuration module deletes measurement object, QoS
task alarm and alarm synchronization. QoS task management makes index settlement
according to the data reported by the corresponding QoS task, generates 4-level alarms
if the threshold is reached, and transfers the alarm information to the alarm module.
The user can view the performance data saved in the database and the original data. The
result of querying the original data is shown in the form of list, and it can be printed or
saved as a file. For the query mode, the user can set the query scope (office or NE),
query date and time, traffic type, and performance object.
U31(CN) provides performance counting functions to help the user count the
performance indices of the system. The user can count through the template provided by
the system, and freely customize some data template to count. In addition, the user can
modify, view and delete related templates. This function enables the user to flexibly count
the indices of the system according to various combinations.
U31(CN) system adds the statistics project that users are especially concerned with to
the database as default statistics indices. Users can view the definition way, realizing
method and algorithm of these statistics projects. For some statistics projects that users
are quite concerned with, users may tailor the statistic project by customizing the project
functions, including its name and algorithm.
The queried and counted result of the reports can be indicated by the form of the data list
and diagram. It can be saved as the file in the form of Excel, text or HTML.
The statistics analysis function of U31(CN) system can make a second counting of the
performance data according to the statistics counting formula, and get the data of
statistics analysis. The analysis ways are statistics analysis of fixed conditions, and
statistics analysis of customized conditions.
U31(CN) system can periodically generates simple reports in query result format and
sends them to the user by email. The simple reports are generated via the report task
maintenance which includes report task creation, task deletion, task modification and
task content display. The report format includes xml, csv, txt, html, PDF, and excel.
Login management authenticates an identity of a login user, including login time of the
user, login IP, whether the user is locked, whether the user is disabled, and whether the
number of the current users reaches the maximum login threshold.
A super user is automatically generated while the system is being installed, and the super
user has the highest authority. The super user can create other users and assign
authorities to other users. Other users can also create users and assign authorities to
them, but the authorities of the created users cannot exceed the authorities of the
creators.
The security management module can generate some user-concerned security events,
for example, authentication failed, user locked, and user disabled. These events are
recorded to the log module for user query in log management.
Role is a set of some operation authorities. One role can be assigned to multiple users,
and the system authenticates the user according to the user role. Roles can be locked. If
one role is locked, the users of this role lose the authorities of the role.
Role set is a collection of a group of roles. To assign a role set to a user is to assign
multiple roles of this role set to the user. Role set can also be locked. If a role set is
locked, the users with this role set lose the authorities corresponding to the role set.
U31(CN) system sets rules of user account through the function, including password
policy, password length, and account length.
Password policy
Support weak password check, such as minimum length, must include at least
three kinds of characters, etc.
Account lock rule: include never lock, lock permanently, lock temporary, lock after
wrong password entering for N times, etc.
Account check: Cannot be same with nearly N days deleted accounts, Notify account
expiry before N days.
Log Management
Log management records logs and manages logs. In terms of log contents, there are
three log types as follows.
Operation log
Records users operation information, including the user names, operation levels,
operation names, command functions, operation objects, NE groups, NE addresses, start
time, results, failure causes, host address and access modes.
Security log
Records information of user login and logout, include the user names, host address, log
names, operation time, access modes and detailed information.
System log
Record the completion status of the severs timed tasks, including sources, levels, log
names, detailed information, host address, start time, end time and associated logs.
Using the log management function, the operator can query logs, view detailed
information, as well as set and query log-filtering conditions.
U31(CN) system records detailed log information, including operation log, system log,
and security log.
The operator can query all kinds of logs, and specify log query conditions, including user
name, time range, operation permission, etc.
The operator can sort the displayed log records in an ascending or descending order
according to a field.
The user can set the filtering conditions (such as a filtering level), and the logs lower than
the level are filtered.
U31(CN) system supports exporting and printing queried results or log data of the current
page to the specified path. After data exporting, the system still keeps the log records.
U31(CN) supports kinds of file formats, such as TXT, HTML, PDF, excel, etc.
U31(CN) system provides log backup policy, and the policy of log recovering and being
saved in the database. Through the log backup scheme, the log can be exported to a file
format in a fixed time or periodically. Through the scheme of log recovering and being
saved in the database, the log which failed in being written in the database can be
recorded in the database again.
It provides backup and deleting of log, performance, and alarm history data. It modifies
task-executing conditions and views the execution log.
It provides OMM database backup, makes backup of all basic data, it only backs up the
data record, not including table structure and history alarms, notifications, log, primary
performance data etc, the alarm data has independent backup functions.
It provides backup for both database and file system, the database backup is for all
database structure(including all database objects structure ) for OMM , and basic data
records, not including history alarms, notifications, log, primary performance data etc,
these history data has independent backup functions. The required file types in file
system include: version file, configuration, and operation period files.
File Cleanup
It monitors performance, alarms, log, database files etc directories, which stores data, to
prevent the size from being to large, and provides regular cleanup function for directories.
It provides monitoring functions for OMM server, system administrator queries server
performance in daily maintenance work, and monitors application servers CPU usage
rate, memory usage rate, hard disc usage rate etc KPI. Users set corresponding
monitoring threshold according to actual configuration of application server, system
automatically initiates monitoring on corresponding indices and sends related alarm
information.
For OMM database server, system administrator monitors database resource in daily
maintenance work, such as query table space, data table information etc; execute data
table import & export, data table cleanup. maintenance, etc. Users set corresponding
monitoring threshold according to actual configuration of application server, system
automatically initiates monitoring on corresponding indices and sends related alarm
information.
The U31(CN) server uses CGSL as the operating system, the system provides the
watchdog function, the watchdog function can automatically restart the CGSL operating
system in case the operating system crashes.
U31(CN) provides a completely integrated setup package with GUI interface for the user
to install U31(CN) database, U31(CN) client, and U31(CN) server. User can upgrade the
U31(CN) client, server, or database from a certain old version to a new version by
executing the scripts that exist under a certain directory of the setup package. U31(CN)
also supports centralized update. U31(CN) sends the NE software for updating to NE
side. NE received the update order, it will update automatically with the update software
getting from U31(CN).
System can provide a unified, centralized, batch, remote, automatic update function for
variant network elements. The NE Version Management supports the following functions:
Customized upgrade for both back end (BE) software and front end (FE) service version;
Batch and remote upgrade according to the NE type; Batch and remote upgrade
according to the area type; Supports rollback when upgrade fail; Supports scheduled
version upgrade; Supports upgrade detailed log.
It maintains and manages software and hardware inventory information in NE layer, and
provides this information to subordinate OMM by Itf-N, as per operator requirements on
unified management of telecom inventory. Now the management covers rack, frame,
board, host etc main inventory, as well as router, switch, network concentrator, electricity,
alarm box, printer, firewall, DNS, NTP, CGSL server etc affiliated equipment. Users view
related inventory resources, and provides inventory export function in file format.
It provides separate presence of inventory according to NEs, and views asset type and
quantity. It also provides asset exporting function, the exported files support xml, txt, xls,
csv, etc.
Signaling tracing is from client in the way of task. This task is then transferred to the
signaling tracing front-end module through server. In the task, some tracing conditions
such as signaling type are defined. When the service process generates a signaling, the
signaling will first be checked if it is satisfied with the pre-defined condition set by
signaling tracing front-end module. If satisfied, the signaling will be sent to the signaling
tracing front-end module, processed in server, stored in database, and finally transferred
to client.
The general information of the signaling is displayed in client in form of list. If user needs
to check the detailed information of one signaling, it can be displayed in form of tree
through decoding program.
The tracing condition of signaling tracing task includes: subscriber tracing select (for all or
partial subscriptions), network element module number select, signaling type select,
tracing duration, signaling tracing number (after tracing one certain number of signaling,
the tracing will pause), self-defined tracing beginning/ending time.
Signaling list: overview of the general signaling; the order of signals, signals missing
or not, used to identify if the service flow is right.
Signaling detail information: check if the content of each field of each signaling is
right; check if process and service state is right.
Signaling codec information: check the original hex information of the signaling;
compare the detailed information of the codec and signaling; limit the scope of error
signaling; check if codec is right.
Signaling specific format: save signaling list and signaling detail information as the
particular file format, this can only be opened by signaling program.
Text format: save decoded signaling detail information into TXT file. Use can view
the content with other particular tools.
Network Time Protocol (NTP) is a protocol for computer time synchronization, it helps the
computer synchronize the time resource or server, to keep time synchronization for the
system and an accurate time resource, and prevent malicious protocol attack by
encryption. It is usually used for hosts in LAN to synchronize the clock with other NTP
hosts via Internet, and then continues to provide time synchronization to other clients in
LAN.
EMS system is based on standard SNTP protocol; it realizes time synchronization among
different hosts in the same LAN. EMS OMM, as NTP server, provides NTP clock
resource, it pushes other OMMs in the LAN work as NTP client and performs time
synchronization; EMS OMM works as NTP client, and synchronize the third-party clock
server.
U31(CN) system provides clock function to query and set the clock and timer of the NE
devices. The clock consistency function can keep the clock of the internal MSC NEs, NE
and U31(CN) consistent. The clock modification function can modify the time employed
by NE or U31(CN).
U31(CN) provides the centralized user data management function for NE user data, such
as MSC Server, MSCe, SGSN, GGSN, PDSN, HSS, MME, PGW, SGW.
Configure data of all NEs can be managed in a centralized way on U31(CN). Four sub
functions are included, and they are configure data backup, configure data restore,
configure data export, configure data view.
For northbound interface, U31(CN) can connect NMS with IPV4 or IPV6 protocol For
southbound interface, U31(CN) can access network elements with IPV4 or IPV6 protocol.
In the web performance report system, some predefined report templates are provided
for traffic model analysis of network element of 3G or 4G (PS&EPC). Via Web GUI the
query of these traffic model reports, current network traffic state and changing tendency
can be checked. Furthermore, the specific report requirement of operator can be
customized developing.
In the web performance monitor system, the monitored KPI can be defined based on
common counter of monitor model. For KPIs computational formula definition, arithmetic
operation of addition, subtraction, multiplication, and division can be adopted. Both
pre-defined KPI and user-defined KPI are supported in performance monitor subsystem.
User can add, delete, scan, or modify KPI for user-defined ones. But for pre-defined KPI,
only query and scan operation is permitted.
Networking management: it creates, modifies and deletes Pool, and it can configure their
associated parameters. It also supports query alarm and notification of Pool.
Task Manager: it provides the timing data verification after setting Pool-related
configuration.
Manual data verification: it provides manual data verification after setting Pool-related
configuration.
Dynamic management: in the GUI interface and the command terminal, it provides the
capability of executing multiple management commands on network elements in the Pool.
It also supports Transferring Pool User and Load Balance configuration.
8 System Interface
U31(CN) system provides kinds of NM interfaces to the upper level NMS, CORBA, SNMP,
and MML interface. The NMS can realize the operations such as configuration
management, fault management, performance statistics, security management etc.
through the NM interface.
The application process of the NMC and U31(CN) are running on ORB. The
communication between ORBs employs the IIOP protocol running on TCP/IP. Any
protocol of data link layer and physical layer is applicable only if TCP/IP is supported. The
CORBA interface of U31(CN) is as shown in the following figure.
NMS
M essage of
C O R B A interface
ZX W N O M C server
Server application process
NE
The CORBA interface complies with 3GPP32, and has done IOT with some operators; it
has been used in the network for Chine Mobile, China Telecom, etc.
NMS
(SNMP Manager)
SNMP Itf-N
OMC
SNMP Agent
Inner invoke
FM PM MIB
NE
SNMP Agent
SNMP manager function is used when network element system can be managed by
SNMP. At this time, network elements act as SNMP Agent to manage by NMS.
SNMP agent function is used when upper network management requires managing core
network management in SNMP (for example, the upper network management system is
HP NNM). At this time, the upper network management system acts as SNMP Manager.
Core network management system only implements fault management via SNMP north
bound interface.
port, multiple NMS terminals can be connected, and the mutual non-relativity of multiple
NMS connection can be ensured.
NMS
MML
command
OMC
Server
Server application process
NE
User can define the period of data file saving. The default value is 3 days. Data file from
U31(CN) to NMC, at most 20 minutes is needed. U31(CN) inventory information stored
includes as a minimum physical location (building, floor, suite, rack, shelf, slot, port),
equipment electronic serial numbers, firmware level, and software level information.
U31(CN) provides inventory information to NMS fined interface via north interface in a
standard file formats such as XML/CSV format. File interface also can be used for
inventory information transmission.
8.5 DB Interface
U31(CN) DB interface is the interface of middle database, which acts as the medium to
establish the data connection channel between U31(CN) system and NMS.
Middle DB has two parts: DB management function and DB. DB management function is
in charge of:
Read the data (performance data, configuration data) in OMM system in fixed time,
and save to local database according to some filtering rule.
DB is used to save the filtered data. The interface of DB is provided for upper NMS
system for DB access.
NMS
DB Interface
OMC
Medium DB System
System
Interior Inter-system
Interface interface
9 Reliability
For U31(CN) software, it can be completely backed up, or just backup some pivotal
configuration files, such as INI file.
For the configuration network resource data, the backup is done to different modules,
such as configuration management data, alarm management data, performance statistic
data.
For all the data, such as statistic data, alarm data, log, etc, they can be exported or
imported.
For the log files, they can be deleted automatically and periodically after backup, in order
to release the system space.
All the above backup operation, the system supports the following methods:
Manually or automatically, for the latter method, the backup period, content can be
configured.
When export or backup the data, the system will prompt the operator if need to delete the
original data.
Corresponding to the backup mechanism, U31(CN) can recover the data backed up to
the NM system. The recovering process can recover all the backup data, or recover part
of the data of the switching office. The recovery mechanism can be combined with the
backup mechanism to completely copy the data of some offices into a new switching
office. This function is also used in the deployment and maintenance of the switching
office.
Support the access restriction for the IP address of U31(CN) client, thus to prevent
the accessing by unlawful client.
Provide encryption and authentication for the interface between NMS and U31(CN),
to prevent the accessing of unlawful NMS.
Provide perfect management mechanism and support the dividable permission and
dividable domain management function. All the permission is divided into multi
levels, the operator can only do the operation under his permission, thus to prevent
operating mistakes.
NetNumen U31(CN) supports the management of user valid period; the following
parameters can be configured: the login time duration, useful-life of accounts and
password, the prompt in advance is also supported.
NetNumen U31(CN) supports simple password detection, such as: empty, all digits,
all letters; accounts name cannot be the same as the telephone number, cannot be
the repetition of accounts name and telephone, cannot be the backformation of
accounts name and telephone number; the max repeated time of one character can
be configured (2-10); when the password is expired, it must be modified forcibly, and
cannot be the same as the latest one or some.
If the user fails to log in, the failed times is limited, and if the max times is up to, the
user will be locked by the system, and this event will be reported to U31(CN) as an
alarm. The user just can be unlocked by the administrator or the limited time duration
is expired.
NetNumen U31(CN) provides perfect log management and audit functions. The user
operation, login and authentication, interface accessing, system running status and
others are written into log files, and the content includes: user ID, login time, logout time,
date and time of important operation, operation content and result; friendly audit interface
is offered and query can be done under different conditions.
Separate Multi-IP network segment are designed, the IP segment within the
equipment is individual, it is divided with U31(CN) and this can guarantee the safety
of NE.
NetNumen U31(CN) supports SSH, SFTP and other third party software, Telnet/FTP
is seldom used; SSL VPN, IPSec VPN are also supported, all of these can
guarantee the safety of transmission.
NetNumen U31(CN) adopts high-performance server and OS, such as SUN Solaris.
If users login and do some operation, it will be reported to U31(CN), so the operation
status can be known.
Monitor operations of all users, and generates maintenance reports. The user
admin has the right to kick out any user.
NetNumen U31(CN) provides perfect log management and audit function. The user
operation, login and authentication, interface accessing, system running status and
others are written into log files, and the content includes: user ID, login time, logout
time, date and time of important operation, operation content and result; friendly
audit interface is offered and query can be done under different conditions.
In Windows 2000 system, TCP/IP is normally used. By default, there isnt any restriction
for the communication ports, some of which is special for certain services, such as port
25 is used for SMTP (Simple Mail Transfer Protocol) , because these ports are known as
the special ports, which can be easily attacked. Therefore, if these services are not
needed, the corresponding ports should be closed.
In Windows system, there are some default sharing directory and files, there is not any
safeguard for them and they may be attacked. Therefore, the sharing directory of
U31(CN) should be closed.
Many services are default startup items in Windows 2000 system, but some of there
services are not very safe, such as Telnet. Therefore, these services should be forbidden,
and for others, which are not so unsafe, the startup type should be configured.
IIS (Internet Information Server) service has the default configuration; there are some
safety leaks, so it should be closed.
This can prevent the operation by the attacker if the accounts or the password is
interpreted by the attacker.
For the database management software, there are some default parameters or
configurations that may be attacked, this will damage the database, causing the
important data to be lost or be decrypted and the database may even be broken forever.
Through the configuration of the management parameters, the system will be safer.
U31(CN) system server can employ the physical configuration of dual server + shared
disk array, as in the following figure. One server works as active server, the other works
as backup server. In normal running, the system is running in the server, and the backup
server does not bear any system load. While the active server fails, it is automatically
switched to the backup server.
RAID hard disks for standby including OS backup and U31(CN) backup
Remote redundancy solution includes 1+1, 2+2 and others. The following figure
shows 2+2 solutions.
Node B has the same configuration with Node A. The data on disk array on the two
nodes keeps synchronization.
Dual Ethernet is used for links among the NEs and U31(CN) Server for mutual backup.
The system uses two 3-layer switches and has a metric with two sets of unequal routes.
Usually data flows go through the small link of the metric. When one link fails, data flows
go through the other link automatically. The OSPF is used as the routing protocol. It can
automatically calculate the metric. It takes network congestion as a metric. When one
route is congested, the other route is used.
Connection server at the client. In the interaction between the server and the
foreground, there is version-detecting mechanism to check whether the software
versions of them are consistent. The software version which is not consistent will not
be normally connected.
While the service of the system gets abnormal, and the process of the server gets
abnormal, the system will record the failure information in the system log, resume the
service automatically or generate alarm information. To prevent data loss due to
unpredictable problems like system abnormality, network failure and natural disasters
and human accidents, the following backup solutions are required:
If one database backup server is used in an area, the solution is to be determined by the
actual situation. If the network condition is favorable and fibers are used for
interconnection, then Managed Snapshot Services (MSS) can be used to provide
snapshot for database running in real time. If the network condition is below the standard,
daily FTP mode can be used to download database backup files.
Normally Client and U31(CN) Server are located in the same site, so they are in the same
LAN and bandwidth between them can be ignored. However, when the LMT is put in the
remote site, the bandwidth should be considered.
Normally, it is based on different LANs between U31(CN) Server and NMS, so the
bandwidth between them should be considered.
The message between U31(CN) Serve and NMS is mainly include alarm data,
performance data and configuration operation (query, modify, delete and data report).
Normally the size of an alarm is 2K bytes. U31(CN) Serve will not report notification to
NMS, only report alarm, and almost 0.05 pieces alarm per second for one NE, so the
bandwidth requirement of alarm from U31(CN) Serve to NMS is 0.05*2048*8/1024=0.8
kpbs.
The statistic granularity of the performance job setting by the NMS is normally less 15
minutes, so U31(CN) Serve will report statistic data to NMS every 15 minutes at most.
The data will be transferred to NMS by FTP file. Supposing every time the file is 60K
bytes, the bandwidth required is 60*8/60=8 kbps.
Therefore, the bandwidth required between U31(CN) and NMS is (when all the NE is in
the normal state.)
2*(0.8*Nn+0.8*Nn+8*Nn)=19.2*Nn Kbps.
=2*(2*1024*0.05*Nn+1*1024*0.5*Nn+2*1024*3/60+1024*20*50*1/100+10*1024/8+5*10
24/8) Byte/s
The message between U31(CN) and NE is mainly including system communication data,
alarm data report, performance data report and configuration operation (query, modify,
delete and synchronization), the bandwidth between U31(CN) and NE is different from
different NE type. Detailed information is listed as following table:
NE type bandwidth
MSC Server/MSCe 256K
MGW 128K
SGSN 76K
GGSN 128K
CG 16K
HLR(FE) 128K
HLR(BE) 64K
MME(uMac) 16K
SGW(xGW) 40K
PGW(xGW) 96K
EPC HSS 64K
10 Technical Indices
This chapter provides the technical indices of U31(CN) system, which can be used as the
reference of the project.
collection
Log query delay <2s
Maximum number of alarm 2million
History alarm storage time 3 month
Storage Capacity
(depend on the hard disk Original performance data 1 month (granularity: 15
capacity) storage time minutes); 3 months
(granularity: 1 hour)
Log storage time 3 months
MTBF(Mean Time Before 6563919 hours
Failure)
MTTR(Mean Time To 30 minutes
Repair)
MLDT(Mean Logistical 12 hours
System Availability Delay Time)
Availability 99.9998%
RTO (Recovery Time < 5 hours
Objective)
RPO (Recovery point < 24 hours
Objective)
Power
Equipment Consumptio Remarks
n
ATCA blade front board
OPBB1(SBC41) 145W
165W =>power consumption >= 120W
OPI1(RSB11) 15W ATCA blade back board
RSB/D(RSB13) 15W ATCA blade back board(Fiber), for TSM
SWBB2(USCC_ Switch front board
55W
3) 55W =>power consumption >= 45W
SWI3(RGE2) 10W Switch back board
ATCA rack
E4140 280W
280W =>power consumption >= 150W
ETCA rack
E8280 320W
320W =>power consumption >= 200W
11 Appendixes