01-02 M2000 System Architecture

2 M2000 System Architecture

About This Chapter

This part describes the overall architecture, hardware architecture, software architecture, typicalconfiguration and interfaces of the M2000.

The M2000 system works in client/server mode.

The M2000 software consists of the client software, server software, and NE mediation software.The software is mutually independent. The client software runs on the client, and the serversoftware and mediation software run on the server.

The M2000 server uses a PC server or an ATCA server.

The hardware of an M2000 client refers to a PC. An M2000 system can have multiple clientsand one server.

Besides the server and the client, the M2000 system may also include the following networkingdevices based on requirements:

l Router

l Switch

l Timeslot cross-multiplexer

2.1 Physical Structure of the M2000A typical M2000 system consists of server(s), client(s), alarm box(es) and other networkingdevices.

2.2 Software Architecture of the M2000This part describes the software architecture of the M2000 and the functional modules of eachpart.

2.3 M2000 Typical ConfigurationThis part describes the typical configuration of the M2000 server, the client and the commonnetworking devices.

2.4 M2000 Operating ScenarioThis part describes the operating scenarios for system.

2.5 M2000 Interfaces

M2000Product Description 2 M2000 System Architecture

Issue 01 (2007-08-14) Huawei Technologies Proprietary 2-1

M2000 interfaces are classified into three types: the northbound interfaces, the southboundinterfaces and the internal interfaces. This part describes their functions.

2 M2000 System ArchitectureM2000

Product Description

2-2 Huawei Technologies Proprietary Issue 01 (2007-08-14)

2.1 Physical Structure of the M2000A typical M2000 system consists of server(s), client(s), alarm box(es) and other networkingdevices.

Using a dial-up server, you can operate and maintain the M2000 system through the PublicSwitched Telephone Network (PSTN). An M2000 system can have multiple clients, and canhave one server.

Physical Structure of the M2000 System (PC Server)Figure 2-1 shows the physical structure of the M2000 system that uses a PC server as the M2000server.

Figure 2-1 Typical configuration of the M2000 system that uses a PC server

Physical Structure of the M2000 System (ATCA Server)Figure 2-2 shows the physical structure of the M2000 system that uses an ATCA server as theM2000 server.



Figure 2-2 Typical configuration of the M2000 system that uses an ATCA server

As shown in Figure 2-2, client access is omitted since it is the same as in Figure 2-1.

Physical Structure of the M2000 System with Other NMSs (ATCA Server)Figure 2-3 shows the physical structure of the M2000 when ATCA servers are installed on theM2000 and other network managers.


Product Description


Figure 2-3 Typical configuration of the M2000 system when ATCA servers are installed onmultiple network managers


Physical Structure of the M2000 System That Supports the IMS (ATCA Server)When the ATCA server is configured for the M2000 to support the IMS, the physical structureof the M2000 system is shown in Figure 2-4.



Figure 2-4 Typical configuration of the M2000 system that is configured with the ATCA serverto support the IMS


2.2 Software Architecture of the M2000This part describes the software architecture of the M2000 and the functional modules of eachpart.

OverviewThe M2000 software consists of three sub-systems:

l Server software

l Client software

l NE mediation software

The NE mediation software varies according to the version of the NE. The NE mediationsoftware accesses the NE of the corresponding version and adapts it for the network.

Figure 2-5 shows the M2000 software architecture.


Product Description


Figure 2-5 M2000 software architecture

M2000 Server SoftwareFigure 2-6 shows the composition of the M2000 server software.

Figure 2-6 Component modules of the M2000 server software

The M2000 server software consists of many function modules. Through the CORBA softwarebus, these modules communicate with each other and with the corresponding modules of theM2000 client software.

The M2000 server provides the interface for the NMS through the NM interface module. Itprovides interfaces for the mediation software of various NEs through the mediation commonmodule. Some modules access the M2000 server database through the database interface.

Table 2-1 describes these modules and their functions.



Table 2-1 Modules of the M2000 server software and their functions

Module Function

NMS interface module(NBI)

Provides the northbound interface for the NMS

Fault managementmodule (FM)

Manages alarms. The fault management involves:l Collecting alarms

l Querying alarms

l Processing alarms

Security managementmodule (SEM)

Manages the system security. The system security involves:l Managing user authorities

l Managing user groups

Topologymanagement module(TM)

Manages the topology. The topology management involves:l Managing topology objects

l Managing the topology view

System managementmodule (SYM)

Manages the system. The system management involves:l Managing the system license

l Initializing the system

l Installing and uninstalling the software

l Managing scheduled system tasks

Configurationmanagement module(CM)

Manages the configuration. The configuration managementinvolves:l Querying the configuration data

l Configuring NEs

l Displaying NE and link reports

l Configuring NEs in batches

l Area-based privilege management of multi-area network andsoftswitch dual-homing management

Performancemanagement module(PM)

Manages the performance. The performance management involves:l Collecting the NE performance data

l Monitoring the performance in real time

l Generating the threshold alarm

Log managementmodule (LM)

Manages logs. These logs can be as follows:l System logs

l Operation logs

l Security logs

l NE operation logs

l NE security logs


Product Description


Module Function

Signaling trace module(ST)

Traces signaling at various interfaces of the NE.

Device panel module(DP)

Provides the device panel for:l Querying the status of NE devices

l Operating on the devices

Mediation module Provides interfaces for the mediation software of various NEs.

M2000 Client SoftwareThe M2000 client software provides the graphic user interface (GUI) for operating andmaintaining the managed NEs.

Each module of the M2000 server software, except the mediation common module and the NMSinterface module, corresponds to a module on GUI.

You can start the NE LMT directly from the M2000 client.

NE Mediation SoftwareThe M2000 mediation module software consists of a series of mediation software. Each pieceof mediation software corresponds to one or more NE versions.

The mediation software provides the interface files and mediation files the NE needs to accessthe M2000 system.

2.3 M2000 Typical ConfigurationThis part describes the typical configuration of the M2000 server, the client and the commonnetworking devices.

The M2000 server may be:

l PC Server

l ATCA

The selection of the computer for an M2000 server depends on the number of NEs in the network.

Typical Server Configuration of the SystemTable 2-2 lists the typical server configuration of an M2000 system.

Table 2-2 Typical server configuration of the system

Items PC Server ATCA

Number of CPUs 2 2

Main frequency of the CPU(GHz) 1.6 2.13



Items PC Server ATCA

Memory (GB) 8 8

Hard disk (GB) 2 x 146 2 x 146

Accessories DVD/Ethernet adapter/English documentation KVM

Operating systemSuSE Linux EnterpriseServer 10/Englishdocumentation

SuSE Linux EnterpriseServer 10/Englishdocumentation

Database DB2 V8.2 DB2 V8.2

Application software M2000 server applicationsoftware

M2000 server applicationsoftware

Common Networking Devices

Table 2-3 lists the common networking devices used in the M2000 system.

Table 2-3 Common networking devices

Item Configuration

Router M2000 side: Quidway AR46-20NE side: Quidway AR28-13 and Quidway AR28-10

Switch and hub Quidway S2016HI, Quidway S3928EI, and 16-portHub

Timeslot cross multiplexer Mercury3600

Typical M2000 Client Configuration

The M2000 client runs on Windows 2000.

Table 2-4 lists the recommended PC configuration.

Table 2-4 Recommended PC configuration for the M2000 client

Item Configuration

CPU P4/2.8 GHz or higher

Memory 512 MB

Hard disk 80 GB

Accessories CDROM/Floppy Drive/Ethernet Adapter/Sound Card/17" LCD Display

Operating system Windows 2000 professional SP02 (or a later version)


Product Description


Item Configuration

Application software M2000 client application software

2.4 M2000 Operating ScenarioThis part describes the operating scenarios for system.

Operating Scenario

Figure 2-7 shows the operating scenario.

Figure 2-7 M2000 operating scenario

2.5 M2000 InterfacesM2000 interfaces are classified into three types: the northbound interfaces, the southboundinterfaces and the internal interfaces. This part describes their functions.

Northbound Interfaces

The M2000 supports the following Itf-N network management interfaces:

l CORBA interfaceIt complies with the 3GPP R6 protocol.

l File interfaceThe NMS retrieves from the M2000 the alarm, performance, and configuration data savedto text files.

l Alarm streaming interfaceThe M2000 sends the processed NE alarms in the form of character stream to the NMS.



l SNMP interfaceThe M2000 sends the processed alarms in the form of text to the NMS through the SNMPalarm interface.

l MML transparent transmission interfaceThe MML transparent transmission interface serves as a proxy for transferring MMLcommands between the NMS and NEs. Through this interface, the NMS can operate andmaintain the associated NEs using MML commands.

Southbound InterfacesThe M2000 manages mobile NEs through the Human Machine Language (MML) interfaces orbinary interfaces.

In addition, the files such as NE log files and performance result files are transported using theFTP protocol between the M2000 and managed NEs.

Internal InterfacesThe server software, client software, and mediation software in the M2000 system communicatewith each other through the CORBA interface.


Product Description


Documents

01-02 M2000 System Architecture