Sjzl20072647-NetNumen M32 (V1[1].00) Technical Manual

NetNumen™M32Integrated Network Operation System

Technical Manual

Version 1.00

ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: [email protected]

LEGAL INFORMATION Copyright © 2006 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information. The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Date Revision No. Serial No. Reason for Issue

Dec 2, 2007 R1.0 sjzl20072647 First edition

ZTE CORPORATION Values Your Comments & Suggestions! Your opinion is of great value and will help us improve the quality of our product documentation and offer better services to our customers.

Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057.

Thank you for your cooperation!

Document Name NetNumen™M32 (V1.00) Integrated Network Operation System Technical Manual

Product Version V1.00 Document Revision Number R1.0

Serial No. sjzl20072647 Equipment Installation Date

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)


Your evaluation of this documentation

Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Your suggestions for improvement of this documentation

Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Make it more concise/brief

Improve the Contents Add more step-by-step procedures/tutorials

Improve the organization Add more troubleshooting information

Include more figures Make it less technical

Add more examples Add more/better quick reference aids

Add more detail Improve the index

Other suggestions

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

# Please feel free to write any comments on an attached sheet.

If you wish to be contacted regarding your comments, please complete the following:

Name Company

Postcode Address

Telephone E-mail

This page is intentionally blank.

Contents

About This Manual ............................................................ i

Purpose................................................................................ i Intended Audience ................................................................. i Prerequisite Skill and Knowledge .............................................. i What Is in This Manual ........................................................... i Related Documentation.......................................................... ii Conventions......................................................................... ii How to Get in Touch............................................................. iii

Chapter 1..........................................................................1

System Overview.............................................................1

Telecommunication Management Network (TMN).................1 Basic Concepts .....................................................................1 Logical Structure...................................................................2

Operation and Maintenance Center (OMC) ..........................3 Basic Concepts .....................................................................3 System Structure..................................................................4 System Features...................................................................4 Network Element (NE) ...........................................................5

Chapter 2..........................................................................7

Technical Specifications...................................................7

Performance Indices..............................................................7

Server Configuration .......................................................8 Basic Server Configuration .....................................................9 Dual-Server Hot Backup Configuration .....................................9 Server Hardware Configuration Calculation Formula ................. 10 Typical Server Hardware Configurations ................................. 11 Server Software Configurations............................................. 13

Client Configuration....................................................... 13 Client Hardware Configuration .............................................. 13

Client Software Configuration................................................14

System Interface .......................................................... 14 Communication Interface .....................................................14 Physical Interface................................................................15

Chapter 3........................................................................17

Software Structure ........................................................17

Design Description ..............................................................17 Software Model ...................................................................17

Software Framework ..................................................... 19

Java GUI Operation Framework .............................................19 Web Operation Framework ...................................................20 Interface Modules Framework ...............................................21

Chapter 4........................................................................23

Networking Modes.........................................................23

OMC System Architecture .....................................................23 Non-Cascaded Networking ....................................................25 Centralized Cascaded Networking ..........................................32 Hybrid Networking...............................................................34

Chapter 5........................................................................37

OMC System Functions ..................................................37

Topology Management .........................................................37 Configuration Management ...................................................39 Performance Management ....................................................39 Alarm Management .............................................................40 Test Management................................................................42 Security Management ..........................................................42 Log Management.................................................................43 Policy Management..............................................................43 Command Line Interface ......................................................44 Report Management ............................................................44 Software Version Management ..............................................44 System Management ...........................................................45 Northbound Interface Access Functions ..................................46

Appendix A.....................................................................49

Abbreviations.................................................................49

Appendix B.....................................................................53

Figures............................................................................53

Tables.............................................................................55

Index..............................................................................57

Confidential and Proprietary Information of ZTE CORPORATION i

About This Manual

Purpose

This manual provides procedures and guidelines for understanding the technical features of NetNumen™M32 (V1.00) Integrated Network Operation System.

Intended Audience

This document is intended for engineers and technicians who perform operations on NetNumen™M32 (V1.00) Integrated Network Operation System. It also addresses the technical managers & engineers.

Prerequisite Skill and Knowledge

To use this document effectively, users should have proper understanding of wireless telecommunications technology.

What Is in This Manual

This manual contains the following chapters:

T AB L E 1 – M AN U AL S U M M AR Y

Section Summary

Chapter 1, System Overview

Introduces basic concepts of Telecommunication Management Network (TMN), NetNumen™M32 (V1.00) Integrated Network Operation System, and Network Element (NE).

Chapter 2, Technical Specifications

Introduces performance indices, server configuration, client configuration, and system interfaces.

Chapter 3, Software Structure

Explains OMC system software model and software framework.

NetNumen™M32 (V1.00) Integrated Network Operation System Technical Manual

ii Confidential and Proprietary Information of ZTE CORPORATION

Section Summary

Chapter 4, Networking Modes

Explains OMC system architecture and networking modes.

Chapter 5, OMC System Functions

Explains OMC system functions in detail.

Appendix A, Abbreviations

Lists all the abbreviations used in this manual.

Appendix B, Figures and Tables

Lists all the figures and tables used in this manual.

Index Index of terms and definitions appeared in this manual.

Related Documentation

The following documents are related to this manual:

NetNumen™M32 (V1.00) Integrated Network Operation System Documentation Guide

NetNumen™M32 (V1.00) Integrated Network Operation System Software Installation Manual

NetNumen™M32 (V1.00) Integrated Network Operation System Operation Manual (Configuration Management)

NetNumen™M32 (V1.00) Integrated Network Operation System Operation Manual (Performance Management)

NetNumen™M32 (V1.00) Integrated Network Operation System Operation Manual (Fault Management)

NetNumen™M32 (V1.00) Integrated Network Operation System Operation Manual (Security & System Tools)

Conventions

ZTE documents employ the following typographical conventions.

T AB L E 2 – TY P O G R AP H I C AL C O N V E N T I O N S

Typeface Meaning

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Bold Menus, menu options, function names, input fields, radio button names, check boxes, drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens and company name.

Constant width Text that you type, program code, files and

Typographical Conventions

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION iii

Typeface Meaning

directory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Select one of the parameters that are delimited by it.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before proceeding further.

Tip: Indicates a suggestion or hint to make things easier or more productive for the reader.

T AB L E 3 – M O U S E OP E R AT I O N C O N V E N T I O N S

Typeface Meaning

Click Refers to clicking the primary mouse button (usually the left mouse button) once.

Double-click Refers to quickly clicking the primary mouse button (usually the left mouse button) twice.

Right-click Refers to clicking the secondary mouse button (usually the right mouse button) once.

Drag Refers to pressing and holding a mouse button and moving the mouse.

How to Get in Touch

The following sections provide information on how to obtain support for the documentation and the software.

If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at [email protected]. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830.

ZTE welcomes your comments and suggestions on the quality and usefulness of this document. For further questions, comments, or suggestions on the documentation, you can contact us by e-mail at [email protected]; or you can fax your comments and suggestions to (86) 755 26772236. You can also browse our website at http://support.zte.com.cn, which contains various interesting subjects like documentation, knowledge base, forum and service request.

Mouse Operation

Conventions

Customer Support

Documentation Support


iv Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION 1

C h a p t e r 1

System Overview

This chapter introduces basic concepts of Telecommunication Management Network (TMN) and NetNumen™M32 (V1.00) Integrated Network Operation System. It also explains Network Element (NE), which is the management object of NetNumen™M32 (V1.00) Integrated Network Operation System. This chapter covers the following sections:

Telecommunication Management Network (TMN)

Operation and Maintenance Center (OMC)

Network Element (NE)

Telecommunication Management Network (TMN) This section explains the following topics:

Basic Concepts

Logical Structure

Basic Concepts

Telecommunication Management Network (TMN), set by ITU-T since 1985, is the international standard of telecommunication network management. TMN is independent of telecommunication network and has its own network management, making TMN running, management, and maintenance simple, standard, and automatic.

TMN is based on a unified system architecture with a series of standard interfaces. It provides an organized network structure to make different Network Management System (NMS) to interconnect with telecommunication equipments, providing various management functions.


2 Confidential and Proprietary Information of ZTE CORPORATION

TMN size can be large or small. Generally, TMN has several different NMSs. Through different interfaces with telecommunication network, TMN receives information of the telecommunication network to control the telecommunication network running.

Logical Structure

The logical hierarchical structure of OMC system network management is based on TMN management framework, as shown in Figure 1.

F I G U R E 1 – TMN LO G I C AL H I E R AR C H I C A L S T R U C T U R E

Perform

ance Managem

entNE Management Layer

Network Management Layer

Service Management Layer

Business Management Layer

Configuration M

anagement

Fault M

anagement

.

.

.

.

.

.

According to TMN standards, telecommunication network management is divided into four layers:

NE management layer

This layer realizes operation and management for one or more NEs. Users of this layer are equipment operation and maintenance personnel.

Network management layer

This layer provides comprehensive management functions for various types of NEs in different network. Users of this layer are telecommunication network organizers and supervisors.

Service management layer

This layer performs functions relevant to telecommunication services, including service providing, service control and monitoring, and service charge. Users of this layer are service operators.

Business management layer

Chapter 1 - System Overview


This layer provides management functions for decisions of the entire telecommunication enterprise. Users of this layer are the enterprise’s highest decision-maker.

TMN also performs a series of modularized management functions for telecommunication network and telecommunication services, including:

Performance management

Configuration management

Accounting management

Fault management

Security management

Operation and Maintenance Center (OMC) This section explains the following topics:

Basic Concepts

System Structure

System Features

Basic Concepts

NetNumen™M32 Integrated Network Operation System is Operation and Maintenance Center – Radio (OMCR) for ZTE mobile radio products. It is also called as Mobile Integrated Network Operating System (MINOS). Through this system, users can implement daily operation and maintenance for NEs, and perform centralized and unified network management functions for various types of NEs.

Note:

In this document, NetNumen™M32 Integrated Network Operation System is called as OMC system for short.

OMC system is strictly designed according to TMN standards. It can be expanded and transplanted flexibly, and is highly fault-tolerant. OMC system provides Common Object Request Broker Architecture (CORBA) interface to upper level and supports cascading among multiple OMC systems.



System Structure

MINOS adopts the distributed client/server architecture as shown in Figure 2.

F I G U R E 2 – OMC S Y S T R M D I S T R I B U T E D AP P L I C AT I O N AR C H I T E C T U R E

The application server directly establishes communication connection with radio network subsystem to satisfy various application requirements. The client only functions as an interface for user to input instructions and view output results.

System Features

OMC system has the following features:

It adopts client/server architecture. The application server establishes communication connection with radio network subsystem to satisfy various application requirements. The client only functions as an interface for users to input instructions and view output results.

The server can run on UNIX or Windows platform. It supports many databases such as Oracle and Sybase.

System software is divided into modules. Different modules can run on different machines according to actual requirements to enhance system processing capabilities.

Chapter 1 - System Overview


OMC system also supports Network Management (NM) cascading or interconnection, which facilitates organizing and managing the network in some large engineering sites.

The entire system architecture design follows the TMN system architecture requirement specified by ITU-T.

It realizes centralized management for multiple types of NEs and supports accessing 40 equivalent NEs at maximum. It also satisfies maintenance and management requirements for WCDMA, TD-SCDMA, and 2G mobile communication systems.

System functions are designed according to TMN specifications and 3GPP specifications. More value-added functions are provided for users in addition to the standard management functions. All these functions are organized in a way that management objects are taken as the core assisted by many management tools.

It provides various external interfaces including NMC management interface. Specific forms of NMC interface depend on NMC requirements, and CORBA interface, SNMP interface, database and file interface are available now. It also supports TeMIP alarm access and collecting Optima performance data.

It supports GUI and character operating interface, and supports MML commands.

The entire system running status can be monitored through network topology map. The topology map is divided into different levels, such as global network topology and local topology. Alarms within the global network can be displayed in real time in both the topology map and the rack view. System gives different audio/visual prompt for different alarm level. Performance data of the entire network are managed in a centralized way, which facilitates query, statistics and report generation.

Network Element (NE)

OMC system manages many types of radio network subsystems, including WCDMA, TD-SCDMA and GSM, and the NEs it manages include RNC and Node B in WCDMA, RNC and Node B in TD-SCDMA, and BSC and BTS in GSM.

OMC system connects the actual NE equipment through NE proxy. The NE proxy shields differences between various NEs, collects NE data and reports them to OMC, and converts requests issued by OMC system to instructions that can be processed by the actual NE.

The NE proxy directly connects with RNC or BSC in the radio network subsystem and performs site management through



IPOA management or BSC management. Figure 3 shows the connection relationship between OMC system and NEs.

F I G U R E 3 – CO N N E C T I O N S R E L AT I O N S H I P B E T W E E N OMC S Y S T E M AN D NE S

Note:

Generally, the management objects of NMS are called as ‘Foreground’, which refers to all real equipments and system objects managed by NMS.

The software system used to manage ‘Foreground’ is called as ‘Background’, which performs monitoring and management for the foreground equipments and management objects. OMC system is sometimes referred to as ‘Background’ in this manual.


C h a p t e r 2

Technical Specifications

This chapter covers the following sections:

Performance Indices

Server Configuration

Client Configuration

System Interfaces

Performance Indices

Table 4 describes the performance indices of OMC system.

T AB L E 4 – OMC S Y S T E M PE R F O R M AN C E I N D I C E S

Performance Index Values

The maximum number of cells managed by a single server

15000

The maximum number of equivalent NEs supported by a single server

40

The maximum number of clients supported by a single server

80

The maximum number of on-line users supported by a single server

80

Capacity

The maximum number of cascading servers

6



Performance Index Values

The maximum number of cascading clients

180

Northbound interface types supported

DB/CORBA/SNMP/FILE/SOCKET

The maximum number of alarm records stored in a single server

108

The maximum number of performance records stored in a single server

1.4 × 109

Data storage duration

Alarm data: 120 days

Performance data: 3 months

Report data: 360 days

System startup time 15 minutes

Whether LMT is supported

Yes

OMCR MTBF 6500 hours

Interface and other performance indices

MTTR 2 hours

Server Configuration OMC system adopts client/server architecture, in which the server implements network management functions and is the core of OMC system. It uses Sun Fire series machine (or PC Server) and the database system is Oracle 9i or Oracle 10.

The server provides the following three types of services:

Database service

The server provides database access and storage services through commercial database software.

Application service

Such services include performance management, alarm management, configuration management, security management, topology management, and OMCR system management and analysis.

Web service

The server provides Web access functions.

This section covers the following topics:

Basic Server Configuration

Chapter 2 - Technical Specifications


Dual-Server Hot Backup Configuration

Server Hardware Configuration Calculation Formula

Typical Server Hardware Configurations

Server Software Configurations

Basic Server Configuration

In basic server configuration, database service, application service, and web service are deployed in one server. It is the simplest configuration, as shown in Figure 4.

F I G U R E 4 – BAS I C S E R V E R C O N F I G U R AT I O N

Application serviceDatabase serviceWeb service

ETHERNET

The basic server configuration has low requirement for cost, and the reliability is comparatively low.

In this configuration solution, independent RAID storage device is configured for the server to realize RAID1 or RAID5 backup, which improves the system reliability.

Dual-Server Hot Backup Configuration

In dual-server hot backup configuration, two mutual-backup servers are used together to implement the same service. Of the two servers, one is primary server and the other is standby server.

In normal cases, the primary server provides service for application system and the standby server monitors the primary



server’s running status (the primary server also detects whether the standby server works normally). If the primary server works abnormally, the standby server works as the primary server to guarantee system running continuously.

Figure 5 shows the dual-server hot backup configuration solution.

F I G U R E 5 – DU AL -S E R V E R H O T B AC K U P C O N F I G U R AT I O N S O L U T I O N

NM server

NM server

Independent RAID storage device

ETHERNET

As shown in Figure 5, there are two NM servers: a primary server and a standby server. Database information is saved in the independent RAID storage device. When the primary server works abnormally, the standby server reads data from RAID and works as the primary server.

Server Hardware Configuration Calculation Formula

For every 1000 cells, at least one CPU is required.

For the basic server configuration:

Memory size = 1.36 MB × the number of cells + 1.35 GB

The disk size required in OMC system is relevant to the accessed NE type.

For accessed WCDMA NE:

Disk size = 147.2 MB × the number of cells + 9.6 GB

For accessed TD-SCDMA NE:

Disk size = 118 MB × the number of cells + 9.5 GB

For accessed GSM NE:

Disk size = 84 MB × the number of cells + 12.6 GB

CPU

Memory

Disk



Typical Server Hardware Configurations

In practical applications, hardware configuration of the server depends on the network size it manages. The OMC system size is categorized according to the number of cells that the server manages.

This section introduces typical server hardware configurations in three circumstances for Unix Server and Windows server:

Number of cells managed is 2000



UNIX Server

Table 5 describes the typical hardware configuration of SUN server.

T AB L E 5 – TY P I C AL UNIX S E R V E R H AR D W AR E C O N F I G U R AT I O N

Number of Cells (cnum) Management Object (max) cnum <=

2000 2000 < cnum <= 8000

8000 < cnum <= 15000

Number of server & server type

1

Sun Fire V490 +FE6140

1


1


Number of CPUs

UltraSPARC IV+ ×2

UltraSPARC IV+ ×4

UltraSPARC IV+ ×8

Memory 8 GB 16 GB 32 GB

Built-in hard disk

146 GB × 2

(RAID1)

146 GB × 2

(RAID5)

146 GB × 4

(RAID5)

Disk array FE6140:146×5

(RAID5)

FE6140:146×6

(RAID5)

FE6140:146×8

(RAID5)

Network card The server should be configured with at least two network cards.

For dual-server hot backup configuration, the server should be configured with four network cards.



Windows Server

For Windows server adopting DELL computer, the hardware configuration is shown in Table 6.

T AB L E 6 – TY P I C AL DELL S E R V E R H AR D W AR E C O N F I G U R AT I O N


2000 2000 < cnum <= 8000

8000 < cnum <= 15000


1

DELL PE2900

1

DELL PE6800

1

DELL PE6800

Number of CPUs

Intel XEON 5110 dual-core processor

1.6 GB × 2


2.6 GB × 2


2.6 GB × 4


Built-in hard disk

146 GB × 4

(RAID5)

146 GB × 8

(RAID5)

146 GB × 12

(RAID5)

Disk array None None None

For Windows server adopting HP computer, the hardware configuration is shown in Table 7.

T AB L E 7 – TY P I C AL HP S E R V E R H AR D W A R E C O N F I G U R AT I O N


2000 2000 < cnum <= 8000

8000 < cnum <= 15000


1

HP ML350G5

1

HP ML570G4

1

HP ML570G4

Number of CPUs


1.6 GB × 2


2.6 GB × 2


2.6 GB × 4


Built-in hard disk

146 GB × 4

(RAID5)

146 GB × 8

(RAID5)

146 GB × 12

(RAID5)

Disk array None None None

DELL Server

HP Server



Server Software Configurations

Table 8 describes the server software configuration.

T AB L E 8 – S E R V E R S O F T W AR E C O N F I G U R AT I O N

Management Object

Windows Server UNIX Server

Operating system Windows 2000 Professional

Windows 2003

Solaris10

Database Oracle 9i or Oracle 10 Oracle 9i or Oracle 10 for SUN Solaris

Anti-virus software McafeeVirusScan 8.5, Norton, or Trend Micro

Trend Micro

Redundancy solution software

Veritas or Legato Veritas or Legato

Client Configuration This section covers the following two topics:

Client Hardware Configuration

Client Software Configuration

Client Hardware Configuration

The client adopts PC work station. The minimum configuration is shown in Table 9.

T AB L E 9 – C L I E N T H AR D W A R E C O N F I G U R AT I O N

Management Object Configuration

Number of CPUs Pentium IV 2.6G

Memory 1 GB

Built-in hard disk 80 GB

Disk array None



Client Software Configuration

Table 10 describes the client software configuration.

T AB L E 10 – CL I E N T S O F T W AR E C O N F I G U R AT I O N

Management Object

Configuration

Operating system Windows 2000 Professional

Windows XP

Browser Netscape

Internet Explorer (V6.0)

Office software Microsoft Office 2000

Anti-virus software McAfee VirusScan 8.5, Norton, or Trend Micro

System Interface This section covers the following two topics:

Communication Interface

Physical Interface

Communication Interface

In OMC system, communication interface performs the following functions:

Provides CORBA Notification service. It bears CORBA protocol, and provides notifications of configuration, alarm, and performance to Network Management Center (NMC).

Provides FTP service. It bears FTP protocol, and is used to transmit configuration file, alarm file, and performance data file for NMC, and transmit files with NE equipment.

Provides Telnet service. It bears Telnet protocol and is used to provide command line access interface.

Provides NTP service. It bears NTP protocol and provides external NTP clock synchronization interface.

Provides interface for SNMP reporting alarm between NMS and NMC. It bears SNMP protocol.

Provides communication interface between NMS and NEs. It bears TCP/IP protocol.



Physical Interface

In OMC system, physical interface performs the following functions:

Self-adapts to 10/100 Mbps Ethernet interface.

Provides X.25 interface.

It can be flexibly expanded to Gigabit Ethernet.


C h a p t e r 3

Software Structure

This chapter explains OMC system software model and software framework, including the following sections:

Design Description

Software Model

Software Framework

Design Description

J2EE framework, which is easily expanded, is suitable for large enterprise-level distributed applications. OMC system design strictly follows TMN standard and adopts J2EE framework in software structure.

Based on J2EE, OMC system conveniently realizes load balance, and supports online capacity expansion, that is, adding new servers and managed NEs during running process. Moreover, the distributed architecture also enhances the system fault tolerant capability. On the other hand, the TMN-based software design guarantees OMC system to interconnect and communicate with other NMSs.

Software Model

OMC system software is divided into three layers:

Platform Support Layer (PSL)

Platform Framework Layer (PFL)

Platform Application Layer (PAL)

Figure 6 shows the hierarchical model of OMC system software.



F I G U R E 6 – OMC S O F T W AR E H I E R AR C H I C AL M O D E L

The three layers are described as follows:

PSL provides all functions of the bottom layer required by a large distributed system. These functions can be applied in both NMS and various large distributed management systems. PSL mainly performs the following four functions:

J2EE application server

J2EE application server extended function

Standard network management protocol stack

Other general toolkits

Some common software frameworks are extracted to form the layer PFL. All specific management applications are based on part of the layer or the entire layer.

On the basis of PFL, PAL provides specific management functions. All these functions can be disassembled. User can choose to load specific management functions according to actual requirements.

Platform Support Layer

Platform Framework

Layer

Platform Application

Layer

Chapter 3 - Software Structure


OMC system is designed with the above distributed and expandable system architecture, flexibly realizing all functional modules.

Software Framework OMC software framework is based on OMC software hierarchical model, providing functions such as performance management, fault management, topology management, report management, configuration management, and security management.

This section explains the following three topics:

Java GUI Operation Framework

Web Operation Framework

Interface Modules Framework

Java GUI Operation Framework

In OMC system, Java GUI operation framework is adopted in the following functions:

Performance management

Fault management

Topology management

Report management

Configuration management

Security management

Note:

Fault management, topology management, report management, and security management can also be realized through calling Web service. Refer to Web Operation Framework for details.

Figure 7 shows Java GUI operation framework.



F I G U R E 7 – JAV A GUI OP E R AT I O N FR AM E W O R K

Web Operation Framework

In OMC system, application calls the server’s Web service through Internet Explorer (IE), Web service calls EJB of OSF, and then EJB of OSF calls EJB of EMF to implement NE information exchange.

Figure 8 shows Web operation framework.

F I G U R E 8 – WE B OP E R AT I O N FR AM E W O R K

Chapter 3 - Software Structure


Interface Modules Framework

Network management Access Function (NAF) performs CORBA access, converts CORBA request to internal operation request, and then transmits it to server to complete the operation.

OSF command line access module converts the input MML command to internal operation request, and then transmits it to server to complete the operation.

Note:

OMC system provides network management northbound interfaces, including CORBA interface, database interface, SNMP interface, and Socket interface.


C h a p t e r 4

Networking Modes

This chapter explains OMC system architecture and networking modes, including the following topics:

OMC System Architecture

Non-Cascaded Networking

Centralized Cascaded Networking

Hybrid Networking

OMC System Architecture

OMC system adopts client/server architecture and provides network management functions as well as various interfaces for integrated network management access.

OMC system manages many types of NEs. It directly manages Node B and manages BTS through BSC. Figure 9 shows the networking architecture of OMC system.



F I G U R E 9 – OMC S Y S T E M NE T W O R K I N G AR C H I T E C T U R E

System components are described as follows:

Server

It is the core of OMC system and performs system management functions. OMC client communicates with the server and exchanges information with NEs through the server.

Server configuration depends on actual requirements, and should guarantee enough processing capability, reliable data storage and satisfactory response time.

Client

It provides two forms for users: command line and Man-Machine Interface (MMI). User performs NE management functions and monitors and manages OMC system through the client. Multiple clients can work at the same time in OMC system.

According to the connected server and the physical position of managed NE, there are three client types:

Local client, which is in the same LAN as the connected server.

Remote client, which is in the remote LAN and there is no NE in the remote LAN

OMC System Components

Chapter 4 - Networking Modes


Migration client, which is in the remote LAN and there is NE in the remote LAN.

Networking equipment

It is used to connect OMC system and the foreground NE system or upper-level NMC. Networking equipments include hub used in local networking and router and transmission equipments used in remote networking.

The following three parts are performed for OMC system configurations:

Server configuration: CPU, memory, disk, and RAID devices;

Client configuration: CPU, memory, and disk;

Networking configuration: local networking and remote networking.

Non-Cascaded Networking

There are three types of non-cascaded networking modes:

Local networking

Remote networking

Combined networking

Local Networking

It is the simplest networking mode for OMC system. In this mode, it is required that OMC system and the managed NEs are physically in the same location, in other words, OMC server, OMC client, and NE are in the same LAN, and are interconnected through Ethernet.

Figure 10 shows the topological structure of OMC non-cascaded networking mode.

OMC System Configurations

Topological Structure



F I G U R E 10 – OMC N O N -C A S C AD E D N E T W O R K I N G M O D E S O L U T I O N (LAN S T R U C T U R E )

There are fewer network equipments in non-cascaded local networking mode. User may select 10/100 Mbps self-adaptive hubs with certain number of ports and twisted pairs (network cable) according to the number of host machines (i.e. the number of servers + the number of clients).

Table 11 lists equipment requirements for the non-cascaded local networking mode.

T AB L E 11 – EQ U I P M E N T S I N N O N -C AS C AD E D LO C AL N E T W O R K I N G

No. Category Type Amount Remark

1 16-port hub ZXR10 1816

n n depends on actual requirements

2 Twisted pair Type-3 or type-5

x m x depends on actual requirements

Equipment Requirements



Remote Networking

There are three circumstances for non-cascaded remote networking:

Client is remote

NE is remote

Both client and NE are remote

There are several transmission modes available for non-cascaded remote networking, such as DDN private line, E1 transmission, and HDSL. Considering that the maximum bandwidth of X.25 is 64 kbps, it is not recommended to use X.25.

Although there are many remote networking forms, their basic network topological structure is similar and is of the same principle. Specific transmission equipments are used to connect WAN and standard interfaces are used between transmission equipments and routers. LAN consists of router, hub, NE, server, and client. Therefore, OMC system can adopt any remote networking mode that is supported by transmission equipment and router.

The transmission bandwidth for remote networking depends on actual conditions. According to OMC system design, performance requirements and data flow, the bandwidth calculation formula is as follows:

Given the following preconditions:

Number of clients: c

Number of WRNCs managed by server: WRNCNum

Number of TDRNCs managed by server: TDRNCNum

Number of GSM cells managed by server: GSMCellNum

Transmission bandwidth (bps) = max(328k×c, 564.8×WRNCNum, 564.8×TDRNCNum, 510.4×GSMCellNum)

The following introduces two non-cascaded remote networking modes:

DDN private line mode

E1 transmission mode

Digital Data Network (DDN) is stable and reliable, with high transmission rate from 64 kbps to 2 Mbps.

DDN adopts router + baseband modem solution: it accesses the router through hub at the server, the router then connects leased line through baseband modem; the remote client accesses leased line through Ethernet interface with the same method.


Transmission Bandwidth

DDN Private Line Mode



Figure 11 shows the DDN private line networking mode.

F I G U R E 11 – C E N T R AL I Z E D N O N -C AS C AD E D R E M O T E NE T W O R K I N G (DDN P R I V AT E L I N E M O D E )

Table 12 lists equipment required in DDN private line mode for non-cascaded remote networking.

T AB L E 12 – EQ U I P M E N T I N N O N -C AS C AD E D R E M O T E NE T W O R K I N G (DDN P R I V AT E L I N E M O D E )


1 Router ZXR10 GAR2604

1+n n depends on the number of LANs at remote client

2 Switch ZXR10 1816

Depends on actual requirements

16-port, connects equipments (such as server and client) in LAN; the number of ports depends on actual requirements

3 Twisted pair

Type-3 or type-5





4 Router subcard RA-4HS 1+n

Used to access local baseband modem

n depends on the number of LANs at remote client

5 Router cable V.35C1 1+n

Connects router and baseband modem


6 Baseband modem

ASM-40 1+n

Used to access DDN in case of large bandwidth requirement, with the maximum rate 2048 kbps


The transmission rate of remote RNC baseband modem and leased DDN private line depends on the required bandwidth, which is determined by the local network management. Refer to Transmission Bandwidth for details.

When transmitting IP packets through 2 Mbps E1 cable, timeslot extracting device is required at both ends of E1 cable. The maximum transmission rate of each timeslot is 64 kbps. Transmission rate can be increased by adopting channel technology, i.e. occupying N timeslots simultaneously to increase the transmission rate to be N × 64 kbps. E1 transmission mode adopts router and E1 module as timeslot extracting device, enabling reliable and stable system performance.

E1 Transmission

Mode



F I G U R E 12 –CE N T R AL I Z E D N O N -C AS C AD E D R E M O T E N E T W O R K I N G (E1 TR AN S M I S S I O N M O D E )

Table 13 lists equipment required in E1 transmission mode for non-cascaded remote networking.

T AB L E 13 – EQ U I P M E N T I N N O N -C AS C AD E D R E M O T E NE T W O R K I N G (E1 TR AN S M I S S I O N M O D E )


1 Router ZXR10 GAR2604

1+n n depends on the number of LANs at remote client

2 Switch ZXR10 1816

Depends on actual requirements

Connects equipments (such as server and client) in LAN; the number of ports depends on actual requirements

3 Twisted pair

Type-3 or type-5





4 Router subcard

RA-4CE1－75 1+n

E1 interface board, adopting coaxial interface


5 E1 cable DT75/3- 1+n

Connects router to E1 transmission network


Combined Networking

The combined networking is combination of local networking mode and remote networking mode. In this mode, the following circumstances are allowed:

Both local NE and remote NE exist

Both local client and remote client exist

Both of the above two circumstances exist

Figure 13 takes DDN networking for example to illustrate the topological structure of combined non-cascaded networking mode.




F I G U R E 13 – N O N -C AS C AD E D C O M B I N E D N E T W O R K I N G (DDN M O D E )

Centralized Cascaded Networking

If the network size is very large, multiple cascading servers can be adopted to realize networking. The lower-level server manages local network, responds network requests and performs data processing. The upper-level server connects with multiple lower-level servers, processes messages from lower-level servers and requests from upper-level clients, and manages the entire network through lower-level servers.

According to physical connection relations between upper-level server and lower-level server, there are two cascaded networking modes:

Local networking

Remote networking

Local Networking

In local cascaded networking mode, upper-level server and lower-level server are in the same local network. Refer to Non-Cascaded Networking for details of connection methods between server and clients.



This section only introduces the situation when both server and its connected clients adopt local networking mode. Figure 14 shows the topological structure of local cascaded networking mode.

F I G U R E 14 – LO C AL C AS C A D E D N E T W O R K I N G

Remote Networking

In remote cascaded networking mode, upper-level server and lower-level server are connected through DDN private line or E1 cable. Refer to Non-Cascaded Networking for details of connection methods between server and clients.

Figure 15 shows the topological structure of remote cascaded networking mode.





F I G U R E 15 – R E M O T E C AS C AD E D N E T W O R K I N G

Hybrid Networking

In hybrid networking mode, centralized NM and local NM are usually connected through remote networking mode, i.e. centralized NM server connects with local NM server through Wide Area Network (WAN). The hybrid networking can adopt any networking mode that is supported by transmission equipment and router.

Figure 16 takes E1 transmission for example to illustrate the hybrid networking mode.




F I G U R E 16 – H Y B R I D N E T W O R K I N G


C h a p t e r 5

OMC System Functions

This chapter explains OMC system functions, including the following topics:

Topology Management

Configuration Management

Performance Management

Alarm Management

Test Management

Security Management

Log Management

Policy Management

Command Line Interface

Report Management

Software Version Management

System Management

Northbound Interface Access Functions

Topology Management

Topology management module performs both physical topology management functions and logical topology management functions.

Elements in topology map

Topology map can display elements including tree view, topology connection diagram, panoramic view, and query list.

Hierarchical display of topology map

Topology map not only displays actual NE, virtual NE, link, virtual link, packet and pipe, but also displays the hierarchical relations between them.



Topology view

Topology map provides both physical view and logical view. It also supports creating, modifying, filtering, deleting, expanding, and zooming view operations.

Grouping

Elements in logical view can be grouped. For such groups, topology management supports creating group, creating subgroup, modifying, deleting, moving, copying, pasting, import, and export operations.

NE and NE proxy

In topology management, operations related to NEs include the following:

Creating virtual NE

Moving NE

Deleting NE

Modifying NE topology property

Displaying NE topology property

Displaying NE statistics information

Viewing NE alarm information

Displaying customized information

Navigating to alarm module or performance module

Viewing asset list

In topology management, operations related to NE proxy include:

Creating NE proxy

Modifying NE proxy property

Deleing NE proxy

Staring/stopping NE proxy

Copying NE proxy

Starting NE management

Viewing NE log

Starting NE configuration data synchronization

Link

In topology view, the connection relations between NEs, between NE and sub-network, and between sub-networks, are described by links.

Operations related to link include

Creating virtual link

Deleting virtual link

Chapter 5 - OMC System Functions


Modifying link topology property

Pipe

Pipe is the container for link reconstruction.

Operations related to pipe include:

Creating pipe

Modifying pipe topology property

Deleting pipe

Displaying pipe topology property

Configuration Management

Configuration management module performs configurations for radio terrestrial equipments and radio resource data.

During system installation, it provides initial configuration to initialize data for terrestrial resource and radio resource, and creates Management Object (MO) for such data.

During system running, it performs resource reconfiguration and parameter modification to adjust network parameters and optimize the entire system configuration.

Configuration management performs the following functions:

Creates, modifies, deletes, and queries parameters for terrestrial resource, radio resource, and transmission of various NEs such as RNC, Node B, BSC, and site.

Dynamic data management

Software version configuration

Full table synchronization and increment synchronization

Rapid configuration

NE data upload

Performance Management

Performance management module checks network performance indices, optimizes and maintains the entire network. It performs the following functions:

Customizes performance management task

User can customize measurement task, Quality of Service (QoS) task, and Key performance Index (KPI).

After customizing measurement task and QoS task, system collects data according to set running period and performs necessary data statistics.



KPI describes key indices of various measurement object types while PI describes non-key indices. In addition to the default KPI/PI provided by system, user can also define new KPI/PI according to actual requirements.

Generates performance alarm

For important indices that influence network running quality, user can set QoS task to start automatic monitoring for performance alarm parameters.

When the collected performance data satisfy the set alarm threshold, system automatically judges alarm level and generates performance alarm.

Queries performance data

User can customize the collected performance data according to actual requirements, and the query result can be displayed in table form or chart form.

Alarm Management

Alarm management module performs the following functions:

General functions

These functions include alarm monitoring, alarm browsing, alarm acknowledgement/de-acknowledgement, alarm clearance, alarm forwarding, and special monitoring.

Alarm checking

It includes current system alarm query, history alarm query, notification query, real-time alarm monitoring, real-time notification monitoring, detailed alarm information, and alarm track.

During alarm checking, after user selects an alarm in the alarm list, the alarm can directly be positioned in the topology tree or NE rack view.

Alarm box setting

OMC system provides two alarm box modes:

Software alarm box: provided with tool software of OMC installation program.

Hardware alarm box: independent alarm hardware equipment.

Both software alarm box and hardware alarm box can be set by user.

Alarm system setting

User can set different prompting sound and color for different alarm level in a template, making alarm severity to be easily



identified. User can also set forwarding content in the template.

Rule setting

OMC system software provides various alarm management rules. Through these rules, user can customize alarm types, alarm levels, audio/video processing modes for alarms, whether automatic processing is required and automatic processing modes.

Alarm management rule settings include:

Alarm delay rule setting

Alarm suppressing rule setting

Alarm counting rule setting

Alarm timing rule setting

Alarm collecting rule setting

Alarm global filtering rule setting

Alarm warehousing filtering rule setting

Alarm user filtering rule setting

Notification warehousing filtering rule setting

Alarm automatic acknowledgement rule setting

Alarm automatic clearing rule setting

Alarm automatic forwarding rule setting

Processing advice setting

With accumulation of on-site alarm solving experience, user can supplement alarm processing advices in the original alarm knowledge database, enabling knowledge sharing and improving troubleshooting efficiency.

Alarm level redefinition setting

OMC system assigns default alarm levels for different alarms. User can redefine alarm levels according to actual requirements. The redefined alarm level is validated immediately after the modification.

Alarm statistics

OMC system predefines various alarm statistics templates. User can perform statistics and analysis for history alarms based on these statistics templates. The statistics and analysis result is displayed in table form or chart form.

Test Management

Through test management module, maintenance personnel check whether system hardware works normally, quickly locate fault and perform troubleshooting.



According to test methods, the diagnostic test is divided into two types:

Routine test

Instant test

During routine maintenance, potential fault can be located and avoided through routine test. When fault occurs, maintenance personnel can quickly locate the fault through instant test, guaranteeing normal and stable running of the system.

Users with relevant rights can perform operations to set routine test items, start/pause test, delete test item, and initiate instant test at the client interface. User can also query or delete the routine test result and instant test result.

Security Management

Security management module guarantees users with different rights to have different rights of system resource usage, ensuring normal and stable running of the system.

Security management module performs the following functions:

Manages security policies

Security policies are used to set user account rules, view system operation rights, and set security events, etc.

Manages roles

Roles are used to define user rights, IP address range used by a role, and whether locking a role. Establishing and allocating roles are foundation of security management.

Manages users

User management includes creating user, modifying user, deleting user, copying user, updating password, querying user login information, setting login IP address range for system administrator.

Manages department

Department management is used to manage administration which a user belongs to.

In practical applications, departments can be divided based on network management functions.

Log Management

Log management module is an effective tool for system administrator to trace system running status, locating system faults, and tracing user operations. It helps to review history operations and understands system working status.



Log management performs the following functions:

Queries logs

User can query all saved system log information through log management, and query specified log information.

Maintains logs

Large amount of log information accumulates during OMC system running. System administrator can periodically clear and maintain log information, or set automatic log clearing and maintenance, to release storage space at server.

Log maintenance includes log backup and log deletion.

NE log query

This function enables user to query all saved NE log information. NE log information can also be queried according to specific conditions.

Policy Management

Through policy management module, system administrator can set timed task or periodic task.

Policies supported by OMC system include:

Periodic policy

Timed policy

Policy management tasks supported by OMC system include:

Configuration synchronization

Executing batch processing file at command line interface

Moreover, policy management module performs functions including creating policy, modifying policy, deleting policy, query policy, and executing policy.

Command Line Interface

Command line interface is a tool for operating personnel to input single MML command or batch processing MML command to perform management for NM objects.

User performs operations such as alarm management, security management and NE configuration management at command line interface.

User can use the command line interface at OMC client, or login to Telnet to use the command line interface.



Report Management

Report management module provides unified report export function. It enables system administrator to customize report task and export report data, facilitating monitoring OMC system running. Alarm management, configuration management, and performance management all customize report and export report data through report management module.

Report management module performs the following functions:

Customizes appropriate report/chart template.

Extracts required data from specified database.

Accumulates and calculates these data and exports report/chart, facilitating user to understand system data and perform analysis and decision on system data.

Software Version Management

Software version management module supports displaying and querying all NEs’ software version information in OMC system. It performs the following functions:

Displays version information

It displays information of the current software version, including user ID, version number, version packet type, integrity ID, number of version files.

Displays version packet file information

It displays information in list form: the time of various operations on the current software version, sub-network and managed NEs the version belongs to.

Version warehousing

Through version warehousing, version files are loaded from client to server and NE, meanwhile, the version information is registered at server.

Version download

Through version download, version files are directly downloaded to the board from NE’s main control board. The downloaded version must be the one that has been warehoused.

Version activation

After downloading version, only those version files that have been activated and downloaded to the board can be validated.



System Management

System management module provides a unified maintenance and management platform for OMC system. User performs monitoring and maintenance operations for application server and database server on this platform.

System maintenance module performs the following functions:

Implements equipment maintenance, displays equipment information such as host machine name, IP address, and operating system information, and saves equipment location information.

Maintains application server, supports querying server performance, configuring server performance monitoring parameters, configuring directory monitoring parameters, and displaying OMC system versions.

Maintains database server, supports viewing database resource, database table set operations, configuring database monitoring parameters, and database backup.

Northbound Interface Access Functions

OMC system provides support for upper-level NMC at OSF. OMC and NMC are connected through many interfaces, including:

CORBA northbound interface

Database northbound interface

SNMP northbound interface

Socket northbound access interface

CORBA Northbound Access

Common Object Request Broker Architecture (CORBA) is a standard for network interconnection, providing an open distributed calculating environment. OMC interacts with NMC through CORBA interface.

The CORBA northbound interface in OMC system performs the following functions:

Entry point Integration Reference Point (IRP)

Communication surveillance IRP

Notification IRP

File transfer IRP



Alarm IRP

Basic configuration management IRP

Kernel configuration management IRP

Bulk configuration IRP

Performance management IRP

Database Northbound Access

OMC exchanges data with NMC through database interface. NMC provides requirements for data range of management objects and performance counters. Based on such requirements, OMC provides database view of configuration object and database view of performance object, and ensures timed view update.

The database northbound interface in OMC system performs the following functions:

Database interface configuration

Performance database interface

SNMP Northbound Access

OMC interacts with NMC through SNMP interface.

The SNMP northbound interface in OMC system performs the following functions:

Alarm report

Alarm synchronization

Socket Northbound Access

OMC interacts with NMC through Socket interface. NMC obtains alarm information through Socket interface.

The Socket northbound interface performs the following functions:

Alarm report

Alarm synchronization


A p p e n d i x A

Abbreviations

Abbreviation Full Name

3GPP 3rd Generation Partnership Project

C

CORBA Common Object Request Broker Architecture

D

DDN Digital Data Network

E

EMF Element Mediator Function

EMS Element Management System

F

FM Fault Management

G

GSM Global System for Mobile Communication

GUI Graphical User Interface

I

IRP Integration Reference Point

ITU-T International Telecommunication Union - Telecommunication Standardization Sector

K

KPI Key Performance Index

M

MIF Management Information Function

MINOS Mobile Integrated Network Operation System

MML Man Machine Language

MO Management Object

MTBF Mean Time Between Failure

N



Abbreviation Full Name

NAF Network Management Access Function

NE Network Element

NEF Network Element Function

NMC Network Management Center

NMF Network Management Function

O

OMC Operations & Maintenance Center

OMCR Operations & Maintenance Center – Radio

OMM Operation Maintenance Module

OSF Operation System Function

P

PAL Platform Application Layer

PFL Platform Framework Layer

PI Performance Index

PM Performance Management

PSL Platform Support Layer

Q

QoS Quality of Service

R

RAID Redundant Access Independent Disk

RNC Radio Network Controller

RNS Radio Network Subsystem

S

SM Security Management

SNMP Simple Network Management Protocol

T

TD-SCDMA Time Division Synchronous CDMA

TMN Telecommunication Management Network

W

WAN Wide Area Network

WCDMA Wide-band Code Division Multiple Access

WSF Work Station Function


A p p e n d i x B

Figures

Figure 1 – TMN Logical Hierarchical Structure .........................2

Figure 2 – OMC Systrm Distributed Application Architecture......4

Figure 3 – Connections Relationship between OMC System and NEs ..................................................................................6

Figure 4 – Basic Server Configuration....................................9

Figure 5 – Dual-Server Hot Backup Configuration Solution...... 10

Figure 6 – OMC Software Hierarchical Model......................... 18

Figure 7 – Java GUI Operation Framework ........................... 20

Figure 8 – Web Operation Framework.................................. 20

Figure 9 – OMC System Networking Architecture................... 24

Figure 10 – OMC Non-Cascaded Networking Mode Solution (LAN Structure) ....................................................................... 26

Figure 11 – Centralized Non-Cascaded Remote Networking (DDN Private Line Mode)............................................................ 28

Figure 12 –Centralized Non-Cascaded Remote Networking (E1 Transmission Mode).......................................................... 30

Figure 13 – Non-Cascaded Combined Networking (DDN Mode) 32

Figure 14 – Local Cascaded Networking ............................... 33

Figure 15 – Remote Cascaded Networking............................ 34

Figure 16 – Hybrid Networking ........................................... 35


Tables

Table 1 – Manual Summary ..................................................i

Table 2 – Typographical Conventions..................................... ii

Table 3 – Mouse Operation Conventions ............................... iii

Table 4 – OMC System Performance Indices ...........................7

Table 5 – Typical UNIX Server Hardware Configuration .......... 11

Table 6 – Typical DELL Server Hardware Configuration........... 12

Table 7 – Typical HP Server Hardware Configuration.............. 12

Table 8 – Server Software Configuration .............................. 13

Table 9 – Client Hardware Configuration .............................. 13

Table 10 – Client Software Configuration ............................. 14

Table 11 – Equipments in Non-Cascaded Local Networking ..... 26

Table 12 – Equipment in Non-Cascaded Remote Networking (DDN Private Line Mode) ................................................... 28

Table 13 – Equipment in Non-Cascaded Remote Networking (E1 Transmission Mode).......................................................... 30


Index

3GPP...................................5 Alarm Management .............40 Application service ................8 Background..........................6 Basic Server Configuration .....9 Business management layer ...2 Centralized Cascaded

Networking.....................32 client/server architecture .......4 Command Line Interface ......43 Common Object Request Broker

Architecture (CORBA).........3 Communication Interface .....14 Configuration Management ...39 Database service...................8 DDN private line mode.........27 Dual-Server Hot Backup

Configuration ....................9 E1 transmission mode..........27 Foreground ..........................6 GSM....................................5 GUI.....................................5 hierarchical model ...............17 hierarchical structure.............2 Hybrid Networking ..............34 Interface Modules Framework21 ITU-T ..............................1, 5 J2EE framework..................17 Java GUI Operation Framework

....................................19 Local client.........................24 Log Management ................42 Migration client ...................25 MINOS ................................3 MML commands ....................5 Mobile Integrated Network

Operating System..............3 NE ......................................1 NE management layer ...........2 NE proxy ....................... 5, 38 NetNumen™M32 (V1.00)

Integrated Network Operation System..............1

Network Element ..............1, 5 Network Management (NM) ....5

Network management layer ...2 Network Management System 1 NMS ...................................1 Non-Cascaded Networking ... 25 Northbound Interface Access

Functions ....................... 45 OMC ...................................1 OMC system.........................3 OMC System Architecture..... 23 Operation and Maintenance

Center ......................... 1, 3 PC Server .......................... 12 Performance Management.... 39 Physical Interface ............... 14 Platform Application Layer (PAL)

.................................... 17 Platform Framework Layer (PFL)

.................................... 17 Platform Support Layer (PSL)17 Policy Management ............. 43 primary server .....................9 Remote client..................... 24 Report Management ............ 44 Security Management.......... 42 Server Hardware Configuration

Calculation Formula......... 10 Service management layer.....2 Software Model .................. 17 Software Version Management

.................................... 44 standby server .....................9 System Management........... 45 TD-SCDMA...........................5 Telecommunication

Management Network ........1 Test Management ............... 41 TMN....................................1 Topology Management......... 37 topology map.......................5 transmission bandwidth ....... 27 UNIX Server....................... 11 WCDMA...............................5 Web Operation Framework ... 20 Web service .........................8 Wide Area Network (WAN) ... 34

Sjzl20072647-NetNumen M32 (V1[1].00) Technical Manual

Documents

Transcript of Sjzl20072647-NetNumen M32 (V1[1].00) Technical Manual