Sjzl20062296-ZXG10-BSS (V2 (1) .97) Network Management Techni

ZXG10-BSS
Base Station Subsystem
Network Management Technical Manual

Version 2.97
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: doc@zte.com.cn
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. The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support or training are subject to change without notice.
Revision History Date 12/21/2006 01/31/2007 Revision No. R1.0 R1.1 Serial No. sjzl20062296 sjzl20062296 Purpose First edition Reviewed and updated
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 Product Version ZXG10-BSS (V2.97) Base Station Subsystem Network Management Technical Manual V2.97 Document Revision Number R1.1
Equipment Installation Date Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance) Good Your evaluation of this documentation Fair Average Poor Bad N/A
Accessibility: (Contents, Index, Headings, Numbering, Glossary) Good Fair Average Poor Bad N/A
Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content) Good Fair Average Poor Bad N/A Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Improve the Contents Improve the organization Include more figures Your suggestions for improvement of this documentation Add more examples Add more detail 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 Postcode Telephone Company Address E-mail Make it more concise/brief Add more step-by-step procedures/tutorials Add more troubleshooting information Make it less technical Add more/better quick reference aids Improve the index
This page is intentionally blank.
Contents
About this Manual .......................................................... vii
Purpose ............................................................................. vii Intended Audience .............................................................. vii Prerequisite Skill and Knowledge ........................................... vii What is in this Manual .........................................................viii Related Documentation........................................................viii Conventions ........................................................................ ix How to Get in Touch.............................................................. x
Chapter 1.......................................................................... 1 Network Management System Structure........................ 1

System Introduction.............................................................. 1 System Background .............................................................. 1 Standards Complied .............................................................. 4 System Features................................................................... 5
Chapter 2.......................................................................... 7 Software Structure .......................................................... 7

Software Module Structure ..................................................... 7 Software Modules ................................................................. 8
Chapter 3........................................................................ 11 Hardware Structure ....................................................... 11

Introduction ....................................................................... 11 OMCR Hardware Structure.................................................... 11
Chapter 4........................................................................ 15 Technical Specification .................................................. 15

System Specifications .......................................................... 15 Performance Specifications................................................... 15 Power Supply Requirement................................................... 16
Ambient Conditions ............................................................. 16 Reliability Indices ................................................................ 17
Chapter 5........................................................................19 Interfaces and Protocols ...............................................19

Interfaces .......................................................................... 19 Protocols............................................................................ 21
Chapter 6........................................................................25 System Functions...........................................................25

System Functions ................................................................ 25 Main Interface Function........................................................ 25 User Management Function................................................... 26 Operation Log Functions ....................................................... 26 Configuration Management Functions ..................................... 27 Fault Management............................................................... 33 Performance Management Functions ...................................... 36 Other Functions .................................................................. 38
Chapter 7........................................................................41 Networking Modes and System Configurations............41

Networking Modes ............................................................... 41 System Configuration .......................................................... 44 Running Environment .......................................................... 45 Server Configuration............................................................ 48
Appendix A .....................................................................55 Abbreviations .................................................................55 Appendix B .....................................................................57 Figures............................................................................57 Tables .............................................................................59 Index ..............................................................................61
About this Manual

Developed independently by ZTE CORPORATION, the ZXG10 is a GSM based system, consisting of a ZXG10-MSS (Mobile Switching Subsystem) and a ZXG10-BSS (Base Station Subsystem). BSS includes ZXG10-BSC (Base Station Controller) and ZXG10-BTS (Base Transceiver Station), where both act together to provide and manage GSM radio transmissions.
Purpose
Goal of this manual is to provide complete information about ZXG10-Base Station Subsystem Networking Management System:

Software structure Hardware structure Technical specifications Interfaces and protocols System functions Networking mode and systems configuration
Intended Audience
This document is intended for network maintenance technicians and engineers.
Prerequisite Skill and Knowledge

To use this document effectively, users should have a general understanding of networking and networking interfaces. Familiarity with the following is helpful:

The ZXG10 system and its various components Interfaces on the network Operating procedures
Confidential and Proprietary Information of ZTE CORPORATION
vii
ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual
What is in this Manual

This manual contains following sections as shown in Table 1.
TABLE 1 M ANUAL SUMMARY
Section Chapter 1, Network Management System Structure Chapter 2, Software Structure Chapter 3, Hardware Structure Chapter 4, Technical Specifications Chapter 5, Interfaces and Protocols Chapter 6, System Functions Chapter 7, Networking modes and System Configurations Appendix A, Abbreviations Appendix B, Figures and Tables Index
Summary Provides basic information about ZXG10-OMCR system. Describes the different software modules involved in ZXG10-OMCR system. Describes about the ZXG10-OMCR system hardware structure. Describes about the technical specifications of ZXG10-OMCR system. Describes about the interfaces and protocols used in ZXG10-OMCR system. Describes about the major functions of ZXG10-OMCR System Describes about the ZXG10-OMCR networking modes and different configuration schemes. Lists all the abbreviations used in the manual. Lists all the figures and tables appeared in the manual. Lists the important words appeared in the manual.
Related Documentation
This document set contains the following manuals:
ZXG10-BSC (V2.97) Base Station Controller Documentation Guide ZXG10-BSC (V2.97) Base Station Controller Technical Manual (Fundamentals) ZXG10-BSC (V2.97) Base Station Controller Technical Manual (Equipment) ZXG10-BSC Manual (V2.97) Base Station Controller Hardware
viii
About this Manual -
ZXG10-BSC (V2.97) Installation Manual
Base
Station
Controller
Hardware
ZXG10-BSC (V2.97) Base Station Controller Debugging Manual ZXG10-BSC (V2.97) Base Station Controller Maintenance Manual (Routine Maintenance) ZXG10-BSC (V2.97) Base Station Controller Maintenance Manual (Troubleshooting) ZXG10-BSC (V2.97) Base Station Controller Maintenance Manual (Emergency Maintenance) ZXG10-BSS (V2.97) Base Station Subsystem Command Manual - Volume I ZXG10-BSS (V2.97) Base Station Subsystem Command Manual - Volume II ZXG10-BSS (V2.97) Base Station Subsystem Operation Manual ZXG10-BSS (V2.97) Base Station Subsystem Operation Manual (Configuration Management) ZXG10-BSS (V2.97) Base Station Subsystem Operation Manual (Radio Parameters) ZXG10-BSS (V2.97) Base Station Subsystem Operation Manual (Performance Counters) - Volume I ZXG10-BSS (V2.97) Base Station Subsystem Operation Manual (Performance Counters) - Volume II ZXG10-BSS (V2.97) Installation Manual Base Station Subsystem Software
Conventions
Typographical Conventions ZTE documents employ the following typographical conventions, as shown in Table 2.
TABLE 2 TYPOGRAPHIC AL CONVENTIONS
Typeface Italics Quotes Bold
Meaning References to other Manuals and documents. Links on screens. Menus, menu options, function names, input fields, radio button names, check boxes, dropdown lists, dialog box names, window names. Keys on the keyboard and buttons on screens and company name. Text that you type, program code, files and directory names, and function names.
CAPS Constant width
ix
Typeface [] {} |
Meaning 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.
Mouse Operation Conventions
TABLE 3 MOUSE OPERATION CONVENTIONS
Typeface Click Double-click Right-click Drag
Meaning Refers to clicking the primary mouse button (usually the left mouse button) once. Refers to quickly clicking the primary mouse button (usually the left mouse button) twice. Refers to clicking the secondary mouse button (usually the right mouse button) once. 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. Customer Support If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at support@zte.com.cn. 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 doc@zte.com.cn; 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.
Documentation Support
Chapter
Network Management System Structure

This chapter describes about:

System Introduction System Background Standards Complied System Features
System Introduction
Network management system is an important component of ZXG10-BSS subsystem. ZXG10-OMCR is the operation and maintenance center in the ZTE BSS system. ZXG10-OMCR system conforms to the ITU-T standards and system is designed on the basis of Telecom Management Network (TMN) of ITU-T. TMN refers to the standards and specification of the Open System Interconnections (OSI) of the ISO model. OSI provides functions, information and physical modules which describes the system interconnection. TMN stipulates the management system and the mechanism structure to realize the specific management systems like configuration, performance and fault management. TMN uses Managed Object (MO) to get the information about managed resources. Operation and maintenance centre locates at the Network Element (NE) management layer in TMN system structure.
System Background
This section explains following:

Position and functions of OMCR in PLMN systems OMCR main functions
OMCR relationship with foreground
OMC in PLMN
Objects controlled and monitored by OMCR in base station subsystem, which includes BSCs, number of BTSs and Transcoders. Figure 1 shows OMCR position in PLMN system.
FIGURE 1 OMCR POSITION IN PLMN SYSTEM
NMC NML
OMC
EML
BSS
NEL
Where NMC=Network Management Centre, OMC=Operation Maintenance Center, BSS=Base Station Subsystem. OMCR major functions are:

To perform effective configuration management of BSS To handle the faults those occur during the BSS operation To analyze the statistics of BSS performance and make necessary system adjustments To provide the Network Management Center (NMC) access to the upper layer equipment
OMCR provides standard interfaces to the upper layer equipment to accept management operations from the NMC and report operation results and events. OMCR also provides standard or non standard interface to lower layer equipments to implement management operation on BSS and get the information reported by BSS.
OMCR Main Functions

The main four functions of OMCR are:
Configuration Management

Physical resources configuration ATM and IPOA configuration No 7 signaling configuration
UChapter UTU1UT - Network Management System Structure -

Radio resource configuration Version management Data synchronization Dynamic data management Alarm management Diagnosis test Measurement task management Alarm monitoring management QoS task management Performance report management Security Management Database configuration and monitoring management Log management CBC management Centralized help system and online help Support the upper layer NMC interface
Fault Management

Performance Management

System Management

OMCR Relationship with Background

OMCR controls and manages the BSS system. ZXG10-OMCR follows client and server model. Server takes care of the database and all the operations. Client works as interface between user and server. Figure 2 shows the relationship between client, server and BSS system.
FIGURE 2 OMCR ARCHITECTURE
Operation Terminal
Operation Terminal
Operation Terminal
Application Server
TCP/IP,X.25,DNN
BSS
BSS
BSS
Standards Complied
Overview ZXG10-OMCR is technically advanced telecommunication network management system complying with the industrial standards. It references the ITU-T TMN series specifications and complies with People Republic of China telecom industry related specifications. ZTE takes care of the local Network Maintenance standards also. ZXG10-OMCR complies with following standards:
Standards
M.3010 Principles for a Telecommunications Management Network ITU-T Geneva May 2000. M.3020 TMN Interface Geneva July 1995. Specification Methodology ITU-T
M.3100 Maintenance Telecommunications Management Network Generic Network Information Model ITU-T Geneva, July 1995. M.3200 TMN Management Services and Telecommunication Managed Areas: Overview. M.3300 TMN Management Capability Presented at the F Interface. M.3400 TMN Management Function. X.733 Information Technology Open Systems Interconnection System Management: Alarm Reporting Function ITU-T Geneva 1992. X.734 Information Technology Open Systems Interconnection System Management: Event Report Management Function ITU-T Geneva 1992.

UChapter UTU1UT - Network Management System Structure -
X.735 Information Technology Open Systems Interconnection System Management: Log Control Function ITU-T Geneva 1992. TIA/EIA, Wireless Network Management. X.711 Information technology Open Systems Interconnection Common management information protocol: Specification 1997. Functional Architecture of Telecommunication Management Network (TMN) (YD9601998). General Design Principles for Telecommunication Management Network (TMN) (YD/T 8521996). Logical Hierarchical Architecture of Telecommunication Management Network (TMN) (YD9351997). Management Functions of Telecommunication Management Network (TMN) (YD9591998).

System Features
ZXG10-OMCR system has the following features:
The OMC employs the client and server structure. Server is responsible for carrying out all the applications. Client works as interface between user and server. Server can run on UNIX platform as well as WINDOWS platform. It supports multiple databases such as ORACLE and DB2, thus helping to improve the system performance. Modular structure of the system software improves the system scalability. Different modules are able to run on different server depending on the requirement, to enhance the processing capacity of the ZXG10-OMCR system. Overall system structure is designed in compliance with the TMN system structure as described in ITU-T. System is scalable and can meet the expansion requirements of the GSM mobile communication system for maintenance and management functions. Supports cascading networks of multiple levels. System functions are organized by taking the managed objects as the core, which enables micro level management. System provides NMC management interfaces such as Q3 and CORBA. Entire system supports Graphic User Interface (GUI), Character User Interface (CUI) and Man Machine Language (MML) commands. System topology map helps to monitor the system status directly.

System alarms can be viewed on topology map and rack view in real time. System supports assignment of different video and audio prompts for different class of alarms.
Chapter
Software Structure

Software Module Structure Software Modules and Their Functions
Software Module Structure

ZXG10-OMCR system has client and server structure. Server has four application entities. Figure 3 shows the relation between four application entities and local O&M clients Work Station Function (WSF) and BSS Management Function (BMF) which runs on the MP.
FIGURE 3 SOFTW ARE MODULE STRUCTURE
Management Support Function (MSF) MSF is system communication part, which has Message Communication Function (MCF) and Database Interface Function (DIF). MCF and DIF are responsible for interconnection of different system entities.
NMC management Access Function (NAF) NAF provides the interface for access of NMC management. Local Management Function (LMF) LMF provides interface for the access of Work Station Function (WSF) management application and acts as an administrator, achieving the operating system functions as stipulated in TMN.
Local management Access Function (LAF) LAF provides the agent function specified in TMN to maintain Managed objects Instances Tree (MIT) and transmit information between BSS and OMC.
Software Modules
Different types of software modules are:

MSF Module NAF Module LMF Module LAF Module WSF Module BMF Module
Functions of each module are explained below: MSF Module MSF performs system public functions such as MCF and DIF. It has following functions:

Database Access System Process Running Monitoring Inter Module Communication System Resource Utilization Monitoring
NAF Module LMF Module
NAF provides the Q3 interface for the NMC access. For more information about the Q3 interface refer Interfaces and protocols. LMF main function is to manage the BSS system. It receives the analyzed user operation requests and implements the operation through the different application processing functions according to the operation conditions. User operation requests are classified as operation on MIT and operation not on MIT. Operation on MIT means operation on current managed objects. Operation not on MIT means the system security management and system performance data history management. LMF provides the following functions:

Command Distribution Function (CDF) Command Log management Function (CLF) Session Service Function (SSF) Operation Output Function (OOF) Management Application Function (MAF) MAF performs following sub functions:
Configuration Management Function (CMF)
UChapter UTU2UT - Software Structure -

Performance Management Function (PMF) Fault Management Function (FMF) Security Management Function (SMF)
LMF supports two interfaces. One is interface F between LMF and WSF and other one is interface Q between LMF and LAF. Q interface carries two kind of information in it. One is operation request for the MIT and returned responses and other message is alarm notice after LAF receives an alarm from Network Element (NE). LAF Module LAF supports the realization of administrative operations. It manages the system by managing the MIT, its application kernel is MIT. Nodes in the MIT represent the different manageable resources in the network. The information contained in such nodes describes the managed objects. LAF has two interfaces, one with BMF and another with LMF. WSF Module WSF is an application located in the client workstation, providing the functions of interfaces F and G specified in the TMN. Information exchange between LMF and WSF of the server uses F interface. Character and graphic user interface modes uses G interface. As server implements all the applications, WSF is required to analyze all the user commands and results returned by the server. To achieve these functions WSF provides appropriate communication management mechanism. Therefore, WSF has User Interface Support Function (UISF), Network Communication Function (NCF), Command Resolution Function (CRF), MMI Kernel Function (MKF), and Window Administration Function (WAF). BMF Module BMF is the application located in the BSC Main Processor (MP) and serves as an agent for background application. As an agent, it translates the MO related operation commands from OMCR into operation on MP database and operation on various types of physical boards. To support Local Monitoring Terminal (LMT) in the BSC, BMF also should be able to receive the LMT commands. These commands are divided into two types. They are inquiry and control. If a control command changes the state or attribute of the resources corresponding to a MO, BMF should notify the OMCR about the changes in the form of event report. BMF also has the access authentication to prevent access and management of invalid host. BMF interface serves externally as LAF and internally as MP database system.
This page is intentionally blank
10
Chapter
Hardware Structure
This chapter describes the ZXG10-OMCR hardware structure.
Introduction
ZXG10-OMCR system follows client/server structure. Among them, server employs the SUN series server or workstation or FUJITSU machine or the PC server. Database is Oracle8.0.5 or Oracle8.1.7 or DB28.1.2 (10user). Client employs Windows NT or Windows2000 workstation. For interconnection with TMN, ZXG10-OMCR provides Q3 interface or DB access. BSC manages and implements BTS functions and local BSC communicates with the server through the LAN. Remote BSC accesses ZXG10-OMCR server in remote networking mode.
OMCR Hardware Structure

Hardware in ZXG10-OMCR system is divided into sever, client, and network as shown in Figure 4.
11
FIGURE 4 HARDW ARE STRUCTURE

Upper-level NMC
Router Remote client
Server
Server
X.25 Frame relay/DDN
Router
Router
Router Local BSC X.25 Frame relay/DDN Return client Local client
Remote BSC
Server
Server manages and implements all the OMCR system function. Server is the OMCR system kernel. ZXG10-OMCR client communicates with server and exchanges the information with BSS system via server. In view of importance of the server in the system, the server should be configured in accordance with ZXG10-OMCR system actual requirements. This will make server to work in optimum level.
Client
Client serves as front-end device for the user. User can control the BSS system using MMI program running on the client. There can be multiple clients in one system. Different types of clients are as follows:
Local Client Client located in the same LAN as the server. Remote Client Client located in remote without a BSC. A remote client can manage multiple BSCs.
Return Client Client located in remote LAN with a BSC.
12
UChapter UTU3 - Hardware Structure -
Network
Network includes hubs, routers and transmission equipments, which connects the clients, server and BSCs in the network. Remote LANs uses transmission equipments in addition with these equipments.
13
14
Chapter
Technical Specification

System Specifications Performance Specifications Power Supply Requirements Ambient Conditions Reliability Indices
System Specifications
ZXG10-OMCR system is distributed system and it is cascaded through domains. Theoretically, it has no limit on number of terminals that can be connected and the number of users that can be supported. The following are the default configuration values.

Number of servers: 3 Maximum number of terminals: 128 Maximum number of users: 128 Maximum number of BSCs that can be managed: 6 Maximum number of TRXs that can be managed: 4000
Performance Specifications
Following are the main performance specifications of the ZXG10OMCR system.
Alarm processing capability: Inserts 15 current alarms within one second. Access speed of client to a server: Less than one second.
15
Report processing capability: In case of 500 cells system, it shows daily report within a minute, monthly report within two minutes, quarterly report within 5 minutes and annual report within 15 minutes. Database storage capacity: Database is capable of storing three months performance measurement data and alarm data. Performance data transmission capability between foreground and background: Transmits the performance data between foreground and background within 15 minutes
Reporting data to upper level NMC: It reports to NMC after 10 minutes of event occurrence.
Power Supply Requirement

Input power supply for the ZXG10-OMCR system should be 220 V and 50 Hz. Power must be supplied through an Uninterrupted Power Supply (UPS) or an inverter (to convert 220 V AV to 48 V DC). High care should be taken about the power supply because power fluctuation to the server will damage the data in the server. The voltage wave form distortion for the backup generator should not be more than 5% to 10%.
Ambient Conditions
Test value of working temperature and humidity in an equipment room refers to value measured 1.5 m above floor and 0.4 m away from cabinet. The standard working conditions are:
For long term:

Temperature: 15 C to 25 C Humidity: 30% to 70% Temperature: 0 C to 45 C Humidity: 20% to 90%
For Short term:

Short term working condition means that continuous operating duration is not more than 48 hours and annually accumulated operating duration is less than 15 days.
16
UChapter UTU4 - Technical Specification -
Reliability Indices
In terms of reliability, unless there is any malignant attack or virus attack the Mean Time Between Failures (MTBF) is more than three months. To achieve good recovery speed, system should be restored with in hour of failure. System takes four hours to run normally after the startup.
17
18
Chapter
Interfaces and Protocols

This chapter describes about external interfaces and protocols used in ZXG10-OMCR system.
Interfaces
ZXG10-OMCR has three external interfaces, they are:
OAM Interface: Interface with the BSC of managed objects, which is a message interface based on TCP/IP protocol. Q3 Interface: Interface with which OMCR interacts with upper level NMC. DB Interface: Interface with which OMCR interacts with upper level NMS.
OAM Interface
ZXG10-OMCR maintains the ZXG10-BSS system by agent process running on foreground (BSS) and background operation and maintenance system. Agent processes are responsible for security, configuration, performance, fault, and other BSS related auxiliary function managements. OMC uses client and server model and TCP/IP protocol. It connects BSS through LAN, as shown in Figure 5.
19
FIGURE 5 CONNECTION BETWEEN BSS AND OMCR
OMCR consists of BSS OAM module and background OAM module. Background means the WSF and EM, they manage functions specified in the TMN and called as OMC. In the design of local OAM and unified NM OMC, the BSS should support the interfaces defined by OMC and BSS uniformly.
Q3 Interface
OMC supports upper level NMC using LMF and interacts with NMC using Q3 interface. Features
Q3 interface conforms to the NMC-OMC specification for TDMA of China mobile.
interface
It uses GDMO and ASN.1 standards to define common information module and standardized information structure irrelative to protocol at the Q3 protocol stack. It creates source programs through OC/XOC compiling tool provided by Vertel platform to construct the Management Information Base (MIB) at NMC and NAF side.
Function
NAF module realizes the Q3 interface in ZXG10-OMCR system. The upper level NMC access the OMCR through Q3 interface. Following are the two NAF related interfaces:
IOMC interface is provided for NMC, through which NMC accesses the OMCR. IOKF interface is provided for NAF, through which NMC accesses the OMCR Kernel Functions (OKF).
DB interface
OMC uses database (DB) interface to access central NMS, thus facilitating central NMC to collect, process and present data (mainly the parameters of network configuration, performance, and fault) from the OMC. Central NMC extracts the Network Management (NM) data from OMCR interim as required using DB interface. The OMCR is only required to give the DB instance name and user name of the
20
UChapter UTU5UT - Interfaces and Protocols -
interim DB. The user should have authorization to view all tables of interim DB. Features Function NMS DB interface is easy to realize and fast to develop. TNMS DB interface is located on the DB server of the OMCR system. Concept of interim DB gives access to NM data to the central NMS. Interim DB provides authority restricted views and tables for the access of upper level NMS.
CORBA Interface
OMCR system provides support for upper level NMC at LMF side, and the inter-operation between OMCR and NMC is implemented through CORBA interface. Through CORBA interface configuration, alarm, and performance statistics functions are performed. Features CORBA, the main-stream northbound interface protocol, is supported by most communication vendors. CORBA realizes the service primitives of network management system through calling methods among objects and self-provided powerful services. Therefore, comparing with fixed service primitives, the semantics is more flexible and rich. CORBA uses IDL (Interface Definition Language) to describe the managed objects. IDL, same as GDMO, is an object-oriented description language. CORBA in OMC CORBA interface is implemented in NAF module of OMC. NMC accesses OMCR through the interface. NAF, which locates between OMCR and NMS, functions as mediation adaptor and realizes adaptive conversion and transmission of information. All commands issued by NMS are adaptively converted to commands recognized by OMCR and executed in OMCR. The returning information of the command is converted by NAF to the form recognized by NMS and then transferred to NMS. All notifications to be reported to NMS by OMCR are monitored and collected by NAF. These notifications are converted to the form recognized by NMS, such as structuring the event notification and transferring to NMS.
Protocols
This topic explains the protocols used by ZXG10-OMCR system for its external interfaces.
21
TCP/IP Protocol
Transmission Control Protocol/Internet Protocol (TCP/IP) is the basic communication protocol of the internet. TCP/IP is a two layered protocol. The higher layer, TCP manages assembling of a message or file into smaller packets in transmitting side. In the receiving side it collects all the packets and reassembles the packets into original message. Lower layer, IP handles the address part of the each packet so that it reaches its destination. It can be used to interconnect different operating systems like UNIX, Windows 2000, Windows NT, and Netware. TCP/IP is a hierarchical protocol it includes many protocols to form TCP/IP protocol group. Figure 6 shows the TCP/IP protocol stack structure.
FIGURE 6 TCP/IP PROTOCOL STACK
TCP/IP protocol has the following layers: Layer1 Layer 1 is the physical layer, which includes network standards such as Ethernet and token ring. IP provides function for translation of different network physical addresses. Layer 2 contains four protocols: IP, ICMP, ARP, and RARP. Layer2 connects multiple networks to one internet. Through which it transmits datagram, provides reliable connectionless packet transmission service and implements conversion logical addresses and physical address. Layer 3 contains two protocols; TCP and UDP based on IP, it provides connection oriented service and enables the transmitter to distinguish between the receivers. This will help transmitters to transmit datagram to right destination. Layer 4 defines main protocols used by different models such as FTP, Telnet, DNS, and SMTP. It offers remote access service to enable a user to perform file related operations and mail transmission on a local or remote computer.
Layer2
Layer3
Layer4
22
UChapter UTU5UT - Interfaces and Protocols -
Q3 Protocol
Q3 is standardized management protocol which provides routing facilities within the network. Q3 comprises seven layer OSI stack with selected protocols forming protocol suite for TMN interfaces. Q3 protocol standard for layer 1 to layer 3 is Q.811, called as lower layer protocol stack. Q3 protocol standard for layer 4 to layer 7 is Q.812, called as upper layer protocol stack. Q.811 and Q.812 are applicable to any of Q3 interface. The two main protocols of upper layer are CMIP and FTAM of which CMIP manages event processes and FTAM manages file transmission and access management. Figure 7 shows the Q3 protocol stack. In addition to management information and management information base, Q3 interface also includes G.774 and M.3100 standards. M.3100 is NE oriented common information model and G.774 SDH management information model.
FIGURE 7 Q3 PROTOCOL STACK
23
24
Chapter
System Functions
This chapter describes about the ZXG10-OMCR system main functions and their implementation procedures. They are as follows:

System Functions Main Interface User Management Operation Log Configuration Management Fault Management Performance Management
System Functions
OMCR provides system installation functions, they are:
Bear equipment installation wizard: Helps to complete the OMCR installation for the bear equipment. Client Installation Wizard: Helps to complete the client installation in OMCR system.
Server Installation Wizard: Helps to complete the installation of server in UNIX environment.
Main Interface Function

System main interface is graphical user interface, which is used to maintain and manage the BSS system. Following steps describes the procedure to use main interface:
25
User login: Enables the authorized user to login to the system and obtains the information about the user after successful login. Main Interface Function: User can enter to main interface after successful login. The main interface provides graphical interface and displays system basic configuration information in topology. Through main interface, user can enter desired module interface such as configuration management, alarm management and performance management. Exit from the system: To exit from the OMCR, click Exit on the main interface menu bar.
User Management Function

User management is responsible for allocating user authorization rights to different resources and management views. The user management has four major sub functions, they are as follows: Authorization Authorization is responsible for user and user group creation, modification, deletion. It allocates the different type of rights and roles to different users and user group, depending upon the requirement. This function checks the authorization of each user after the successful login to the system. This function manages the user data and their authorization levels. Network Transmission Security: This function encrypts and decrypts the information between server and client. The security management level classifies into user level, MO level, and transmission security. The user level check is done during the login; operation level checks are done for each operation. The transmission security checks the communication between the server and client.
Authentication Data Management Network Transmission Security
Operation Log Functions

Operation log records all operations initialized by a client and performed on a server. Operation log includes the information about the user, operation content, and time of operation. The operation log interface on the client provides the log view for tracing the modification on system parameters and the operation commands executed during the selected time span. Table 4 shows the different operation log functions. Procedure to see the operation log:
26 Confidential and Proprietary Information of ZTE CORPORATION
UChapter UTU6 - System Functions -
1. Login to ZXG10-OMCR system. 2. Select Security Management in the main interface panel. 3. Click Operation Log.
TABLE 4 OPERATION LOG FUNCTIONS
Category
Functions View all log information: View all the log information in the current database. Filter events: Set log query condition. User may filter log information shown on the interface to display the records that match the conditions. Refresh: Refresh to display the current log information in real time. Query specific information: User can query the required information by using the command codes.
Log view
Log operation
Responsible for operation of saving a log, opening a log and deleting a log.
Configuration Management Functions

Configuration management is one of the four main functions of the NMS. It helps the user to create, modify, monitor, and delete the NE and its parameters. For GSM network, configuration management has following functions:

MSC configuration Physical resource configuration Radio resource configuration Software loading and version management Dynamic data management
Refer Table 5 for detailed explanation about configuration management functions.

TABLE 5 CONFIGURATION M AN AGEMENT FUNCTION
Category MSC configuration Physical resource configuration
Functions Create, delete and query the Mobile Switching Center (MSC) data. Add and delete the MSC. Create, delete and query the GsmEquipment data. Create, delete and query the BSCEquipment data.
27
Category
Functions Add, query and delete racks of a Base Station Controller (BSC). Add, query and delete shelves of a BSC. Add, query and delete modules of a BSC. Add, query and delete the composite unit Munit of a BSC. Add, query and delete units of a BSC. Add, query and delete boards of a BSC. Add, query and delete PECMTs of a BSC. Add, query and delete the PC2MLINK of a BSC. Add, query and delete the NSCOM of a BSC. Add, query and delete the Mport of a BSC. Add, query and delete MPMPTs of a BSC. Add, query and delete the Bus485 of a BSC MONI board. Add, query and delete the LapdBch of a BSC Lapd board. Add, query and delete LapdTs of a BSC. Add, query and delete the FSCOM of a BSC. Add, query and delete the Dsp of a BSC DRT unit. Add, query and delete the Dsp of a BSC SDRT unit. Add, query and delete the Btrunk of a BSC. Add, query and delete the AtsCom of a BSC. Add, query and delete the ATrunk of a BSC. Add, query, modify and delete a BSC. Add, query and delete the BPCM of a BSC. Add, query and delete the TnetHW of a BSC. Add, query and delete the InternalHW of a BSC. Add, query and delete PCM lines at A interface of a BSC. Add, query and delete the SMPCM of a BSC. Add, query and delete PCM lines at Abis interface of a BSC. Add, query and delete the HDLCBch of a BSC control-layer board. Add, query and delete the HDLCBch of the BSC composite unit. Add, query and delete the Bus485 of the BSC composite unit. Add, query and delete the TsCom of a BSC.
28
Category
Functions Add, query and delete the TCPOOL of a BSC. Add, query, modify and delete the GIUCOM of a BSC. Add, query and delete a network service entity (NSE). Add, query, modify and delete a virtual circuit NSVC. Add, query, modify and delete the GTRUNK of a BSC. Add, query, modify and delete the BRCH of a BSC. Add, query and delete the PCM at GB port. Add, query and delete a BRPCFG. Add, query and delete a FRPCFG. Add and delete a BSC site. Add, query and delete a DropCom. Add, query and delete a BTS panel. Add, query and delete a BTS frame. Add, query and delete a BTS rack. Add and delete a BiePcm. Add and delete a BieDropPcm. Add and delete a BieCom. Add, modify and delete a CDU panel. Add and delete a dynamic HR secondary timeslot. Add and delete DTRU panel, Dual-carrier mode supported Combined rack supported Add and delete a TRUMulHyc. Add, query and delete a transparent channel (TICBIPP-BOSN-BIPP-TIC). Add, query and delete a transparent channel (TICBIPP-BOSN-TCPP-AIPP-TIC). Add, query and delete a transparent channel (BIETIC-BIPP-BOSN-BIPP-TIC-BIE at the BTS side). Add, query and delete a transparent channel (BIETIC-BIPP-BOSN-TCPP-AIPP-TIC at the BTS side). Add, query and delete a transparent channel at the GB port. Add, query and delete a PEU board. Add, query and delete a SPAU board. Add, query and delete a STRU board.
29
Category
Functions Add, query and delete a PCOM board. Add, query, modify and delete a CBCOP. Add , query , modify and delete Ring network. Add, query, modify and delete an X25. Add, query, modify and delete a radio BSC. Add, query, modify and delete a radio base station. Add, query, modify and delete a cell. Add, query, modify and delete a transceiver. Add, query, modify and delete a channel. Add, query, modify and delete a carrier frequency. Add, query, modify and delete a power control.
Radio resource configuration
Add, query, modify and delete a handoff control. Add, modify and delete TDD external cell. Supports Network Assisted Cell Change (NACC) Edit the related cells. Edit external cells. Edit the 3G-related cells. Edit 3G external cells. Enabling TFO and noise suppression Enabling Extended uplink TBF Create, delete, query and modify the software storing.
Software version configuration
Create, delete, query, modify and load Class 1 software. Create, delete, query, modify and load the board software and query the, version of the board software running currently. Acquire the foreground MP clock Set the foreground MP clock by taking the OMCR clock as the reference State synchronization upon recovery of the disconnected BSC module: After disconnection from the background server, the BSC will synchronize all the state information (including the active/standby state and the management state) with the background server upon its recovery. BCCH switching: When the BCCH carrier frequency of a cell is fault or unavailable, switch the good non-BCCH carrier frequency to be the BCCH carrier frequency through forced BCCH switching or the BCCH switching initiated by the foreground automatically.
Dynamic data management and other configuration information
30
Category
Functions Query, block and unblock dynamic attributes, which include the administration state (AD), the operation state (OP), the available state (AV) and the spying state (SPY). Obtain the number of module traffic instances. Obtain the configuration information and state of N7 signaling link. Obtain the current resource information of a module, that is, user can query the statistic information about channels under the module. Obtain the current resource information of a cell, that is, user can query the statistic information about channels under the cell. Query the BRP board corresponding to a specific cell. Obtain all the cells configured under the BrpGroup, that is, user can query the correspondingly configured cells by the BRPGROUP. Setting of channel state spying: Set to spy the ongoing status of all the channels of a transceiver. Cancel the channel state spying. Forced release at A interface: Release the timeslot resources at A interface by force for otherwise using. Query the connection relationship between the Abis interface and A interface according to channels at the Abis interface. Intelligent Power OFF Abnormity detection at A-interface View the foreground IP address. Mark the TRU where the BCCH resides. Confirmation of the important operations for the dynamic data management: Confirm such operations as blocking some important operated objects like BSC, cells, transceiver and channels, and the global reset. Query and setting of the foreground switch parameters: Query and set some important parameters in the foreground R_OPTION table. Query and setting of the flow control bitmap: Query and set the foreground flow control parameters. Query the flow control level. End the flow control. R4 protocol is supported
31
Configuration management has four types depending upon its location in the system. They are:

Client configuration management LMF configuration management LAF configuration management MF configuration management
Client Configuration Management
Client configuration management helps users to configure the physical equipment, No 7 signaling, radio resources, software loading and software version modification. ZXG10-BSS system configuration should follow the following order: 1. Physical equipment configuration 2. No 7 signaling configuration 3. Radio resource configuration 4. Software configuration This sequence to be followed to maintain the relativity and validity between the MOs and this is ensured by relativity and validity on interfaces or servers. Client mainly checks whether the interface is compatible and range is valid. Server mainly checks validity and relativity between MOs.
LMF Configuration Management
Configuration commands received by LMF modules are classified in to two groups, they are:
Addition, deletion and modification of MOs. These commands are mainly used to complete the resolution function, implement conversion between interface F commands and CMIS commands.
Querying the MOs status, system related operations and commands related big events. LMF executes these commands by directly calling the various interfaces like DIF and LAF interfaces in it.
LAF Configuration Management
LAF module does following functions, management triggers any function on MO:

when
configuration
Check Data relativity and validity. Transform the CMIS primitive sent by the resolution process to the simple data structure. Send custom messages to the foreground. Write background database. command

MF Configuration Management
MF configuration management is dedicated to process the event report and data synchronization mode. When the reported messages are processed, it transforms the custom messages to CMIS messages. Configuration management event reports are mainly due to the status change of the MOs. MF is responsible for implementing
32
the synchronizing process between foreground and background upon recovery after disconnection.
Fault Management
Fault management is responsible for alarm management and diagnosis test. Fault management system collects, stores, and displays the alarm and notification messages generated by the equipments. Diagnosis test performs test of equipment boards, important chips, and communication links. Table 6 explains detailed fault management functions.
TABLE 6 FAULT M AN AGEMENT FUNCTIONS
Category
Functions Alarm management Alarm list display: Displays the current alarms in real time in the alarm main interface and the unconfirmed alarms in audible/visible form Alarm rack diagram display: Displays the alarm status of a rack diagram and a board dynamically and visually, updates the rack diagram based on event reporting and makes man-machine command operations. Notification display: It displays the notification messages on main interface. Setting alarm display modes: User can set the blink frequency of alarm indicators and the audio files of alarms at a certain level. Filtering alarm display: Filter alarm display by setting rules for filtering. Filtering alarms to be stored: Filter alarms to be stored by setting rules for filtering.
Alarm status monitoring
Alarm filtering
Setting, modification and deletion of alarm filtering rules: Create, modify and delete alarm filtering rules according to objects, alarm codes and alarm levels. Setting, modification and deletion of notification filtering rules: Create, modify and delete notification filtering rules according to objects and notification codes. Setting, modification and deletion of alarm reclassification rules: Create, modify and delete alarm reclassification rules according to objects, alarm codes and alarm levels. Alarm reclassification: Reclassify alarm levels.
Alarm reclassification
Confirming alarm notification
Alarm confirmation: Confirm the current alarms and then the alarm indicator on the interface of the alarm client does not blink any more.
33
Category
Functions Confirmation of restored alarms: Confirm the restored alarms and then the alarms disappear from the unconfirmed recovery interface. Notification confirmation: Confirm a notification and then the notification disappears from the interface of the alarm client. Alarm clearing: Delete the current alarms manually and then the alarms disappear from the interface of the alarm client. Alarm synchronization: Synchronize the current alarms from the foreground. Query of current alarms: Query the alarms not restored currently by levels, objects and alarm codes. Display the result on the interface or output it in the EXCEL form. Query of history alarms: Query the restored alarms (including the dump alarms) by time, levels, objects and alarm codes. Display the result on the interface or output it in the EXCEL form. Notification query: Query the created notifications by time, objects and notification codes. Display the result on the interface or output it in the EXCEL form.
Alarms querying
Query of immediate dump alarms: Query the important alarms that have been dumped immediately by time, levels, objects and alarm codes. Display the result on the interface or output it in the EXCEL form. Query of unconfirmed alarm recovery: Query the alarms that have not been confirmed to be restored by time, levels, objects and alarm codes. Display the result on the interface or output it in the EXCEL form. Alarm frequency statistics and analysis: Count the number of occurrence of alarms at the various levels within a certain period, which can be displayed by a chart. Display the result on the interface or output it in the EXCEL form. Periodic alarm dump: Set the dump period, dump startup time and alarm storage days to periodically dump alarms that are prior to the alarm storage days. Immediate alarm dump: Dump alarms to another database table. It can be queried in the immediate dump alarms. Setting, modification and deletion of alarm counting rules: Create, modify and delete alarm counting rules according to objects, alarm codes and alarm levels. Setting, modification and deletion of alarm suppression rules: Create, modify and delete alarm suppression rules according to objects, alarm codes and alarm levels.
Alarm dump
Correlation rules of alarms
34
Category
Functions Setting, modification and deletion of alarm conflation rules: Create, modify and delete alarm conflation rules according to objects, alarm codes and alarm levels. Query of alarm relativity: Query the relativity of alarms. The rules and secondary alarms of relativity can be displayed. Setting, modification and deletion of alarm short message forwarding rules: Create, modify and delete the alarm forwarding rules for the user according to objects, alarm codes, alarm levels and forwarding time span. Alarm knowledge base management: A user can query the alarm content and system solution by alarm codes and alarm objects, and modify the user solution. Customized alarm display: A user can customize the alarm display by objects, alarm codes and alarm levels, so that only the desired alarms can be shown. Setting, modification and deletion of customized alarm display: A user can set, modify and delete rules to customize display through objects, alarm codes and alarm levels. Setting of environment alarm parameters: Set the upper level and lower level of temperature and humidity alarms of each module and the period of infrared alarms. Setting, modification and deletion of trunk node template: Set the alarm levels and the alarm content for the trunk nodes 1 to 12 to form templates, which can be modified and deleted.
Customized alarm display
Trunk node alarm
Setting of trunk node on/off mode: Set the high and low level of trunk node alarms on a rack. Man-machine command operations of an alarm rack board: With the board man-machine commands, a user can perform such operations as query of board status, query of history alarms of a board, board reset and active/standby switchover. Diagnosis test Immediate test of units, composite units and links: Select the units, composite units and links to be tested and then create a immediate test task to test them immediately. Routine test of units, composite units and links: Select the units, composite units and links to be tested and the time point and period of the routine test, and then create a routine test task to test them periodically.
Immediate test
Routine test
35
Category
Functions Creation, suspension, restore and deletion of a routine test task: After creating of a routine test task, a user can suspend, restore and delete the task. E1 BER test at A interface: Test the BER on the E1 line at A interface. The PCM line to be tested, timeslot and test period are selective. E1 BER test at the Abis interface: Test the BER on the E1 line at the Abis interface. The PCM line to be tested, timeslot and test period are selective. E1 BER test at the Gb interface: Test the BER on the E1 line at the Gb interface. The PCM line to be tested, timeslot and test period are selective. E1 BER test at the Ater interface: Test the BER on the E1 line at the Ater interface. The PCM line to be tested, timeslot and test period are selective. Creation, startup, cancellation and deletion of an E1 BER test task: The PCM line, test modes, timeslot, self-loop modes, test duration and echo duration are selective when a task is created. Create E1 BER test tasks at A interface, the Abis interface, the Gb interface and the Ater interface respectively. Query of test results: Query test results according to test types, test objects, test modes, test results and test time span. Display the result on the interface or output it in the EXCEL form. Deletion of test results: Delete test results according to test types, test objects, test modes, test results and test time span.
E1 bit error rate (BER) test
Test result operation
Performance Management Functions

Performance management is responsible for monitor the system performance. Performance management has following subtasks:

Measurement task management Observation task management QoS alarm monitoring Alarm monitoring management job. Performance analysis and report generation.
Table 7 shows the performance management functions.
36
TABLE 7 PERFORM ANCE M ANAGEMENT FUNCTIONS
Category
Functions Measurement tasks creation: Create a new measurement task. Measurement tasks modification: Modify some parts of a created measurement task. Measurement tasks deletion: Delete a created measurement task. Measurement tasks suspension: Suspend a created measurement task. Measurement tasks resumption: Resume a suspended measurement task. Query of a counter of measurement tasks: With the counter query, the current value of a counter of a measured object of a certain measurement task that is collecting data can be observed instantly. Query of the history data of measurement tasks: Query the history data of a measurement task by objects or time. Observation tasks creation: Create a new observation task. Observation tasks modification: Modify some parts of a created observation task.
Measurement task
Observation task
Observation tasks deletion: Delete a created observation task. Observation tasks suspension: Suspend a created observation task. Observation tasks resumption: Resume a suspended observation task. Observe events QoS alarm threshold modification: Modify the alarm threshold by modifying the alarm monitoring.
Performance threshold
QoS tasks suspension: Suspend a started QoS task. QoS tasks resumption: Resume a suspended QoS task. Create : create new alarm monitoring job
Alarm monitoring job
Modify: Modify alarm monitoring job Delete : Delete alarm monitoring job Suspend : Suspend alarm monitoring job Resume : Resume alarm monitoring job
Performance report
Configuration report function: Complete the report functions configured by the CS and output them in EXCEL form.
37
Category
Functions GPRS configuration report function: Complete the report functions configured by the PS and output them in EXCEL form. Performance report function: Display collection and analysis of performance data via a report and output it in EXCEL form. Output a report in Excel. Graphic analysis for a report: Analyze report data in such graphic forms as line graph, table or pie graph. Performance report template: Provide a report template for a user to save the customized specifications or system specifications to form a report. Automation reports creation: With the function of creating a report automatically, if a user creates a report task, then a report can be made automatically.
Automation report
Automation reports modification: A created automation report task can be modified. Deletion of automation reports: A created automation report task can be deleted. Automation report log management: View the creation of an automation report by the report log management. Synchronization: Implement synchronization operation if the data in the measurement job, observation job and QoS management object on the equipment is inconsistent with that in the OMC due to any exception.
Others
Performance specification customization: Enable a user to custom specifications if the desired ones are not available in the default report. Scheduled performance data dump: Dump the performance data as scheduled to prevent the data in the database from increasing unlimitedly.
Other Functions
In addition to the above mentioned functions, the OMC provides some other tool functions for the convenience of user management and maintenance. These functions include:
Database configuration and monitoring: Monitor, query and modify the database table, table space and database process DIF.
38
Script tools: Include the SQL script tools and system script tools, which are used to maintain the database and system and resume the database backup.
39
This Page is intentionally blank.
40
Chapter
Networking Modes and System Configurations


Networking Modes System Configuration
Networking Modes
ZXG10-OMCR provides three solutions to the remote networking according to Layers 1 to 3 protocol stacks as provided in the Q.811 and GSM 12.01. According to the different connection modes between the OMCR and remote modules, there are three schemes. They are:

A interface mode X.25 mode DDN leased line mode
A Interface Mode
Connection A interface employs the existing 2 Mbps PCM link between the MSC and BSC as the link to transmit the NM information. In this mode, timeslots between the MSC and BSC are used to transmit the OMC information with a transmission rate of n x 64 kbps (where n=number of the occupied timeslots). For the large traffic cases, such as software downloading, database backup and file copy, system adopts multiplexing or utilizes the idle time slots. This mode is economically practical and makes full use of the resources available to realize the O&M functions. Figure 8 shows the interconnection between BSCs and OMCR through A interface.
41
FIGURE 8 NETWORK IN A INTERFACE MODE

OMCR Server C lient 1 C lient 2
LAN
Router L oc al BSC 1 Loc al BSC n Remote BSC 1 MSC
Remote BSC n
Features
In the A interface mode, it implements transmission of the OMC information through the existing MSC. Since the connection between MSC and BSC are reliable, transmission in the PCM mode is also reliable, which can save investment for users. This is achieved at the cost of loss of timeslots. If the entire system is configured in a large capacity, the data transmission rate will decrease subject to decrease of the number of available channels.
X.25 Mode
Connection In X.25 mode, a board (X.25 board) is installed in BSC rack. This board converts X.25 protocol into IP. The line interface is V.35, V.24, X.21 or X21bis. The router performs conversion between the LAN and X.25 networks to enable the OMCR host to connect to each BSS. In the X.25 mode, the transmission rate ranges from 9.6 kbps to 64 kbps. Generally, the transmission rate is 64 Kbps at the Operation and Maintenance Center (OMC) and 9.6 kbps at the BSC side of a remote module. That is, it employs 9.6 kbps X.25 interface between the BSC and PSPDN, and the 64 kbps X.25 interface between the OMC and PSPDN. Generally, the PSPDN connects with NMC by a router with the standard TMN Q3 interface. It transmits messages and orders that conform to the TMN standard over the links. Figure 9 shows the networking in X.25 mode.
42
UChapter UTU7 - Networking Modes and System Configurations -
FIGURE 9 NETWORKING IN X.25 MODE

OMCR Server C lient 1 C lient 2
LAN
Router Loc al BSC 1 Loc al BSC n X.2 5 /P SP D N Remote BSC 1
Sc heme 1 : BSC With X.2 5 P lug-inc ard
Router
Sc heme 2 :With a protoc ol c onvers ionrouter Remote BSC n
Features
This mode is more reliable. Due to the limitation of the transmission rate at the BSC side, the transmission rate in this mode is generally 9.6 Kbps, which is relatively low. However, it is stable and reliable.
DDN Leased Line Mode

Connection Digital Data Network (DDN) runs steadily and reliably, with a high transmission rate of 64 Kbps or higher. In this mode, the networking components are mainly the baseband MODEM and router, of which the models should be determined according to the type of a local DDN. Figure 10 shows networking in DDN leased line mode.
FIGURE 10 NETWORKING IN DDN LEASED LINE MODE
OMCR
Se rver
C lie nt 1
C lie nt 2
LAN
R outer Loca l BSC 1 Loca l BSC n DDN
DSU/C SU DSU/C SU
R oute r
R e m ote BSC n
43
Features
In this access mode, the remote module BSC can connect to the DDN leased line through the router and the DSU/CSU. The DDN mode provides a high, stable and reliable transmission rate.
System Configuration
Components
The Figure 11 shows system configuration Configuration structure is based on the OMCR system functions.
FIGURE 11 SYSTEM CONFIGURATION STRUCTURE
OMCR Works tation 1 . OMCR . Works tation n .
O MCR Server
Router and s witc h
P eripheral s (printer)
WE B s erver and firewall O M C R s ys tem
P ST N ,P SP D N ,D D N BSS s ys tem n U pper- level N M C BSS s ys tem 1 . . .
Following are the description of the components: OMCR Server As the core of the OMCR system, it serves to achieve all the management functions of the OMCR system. All the OMCR workstations communicate with the server and exchange information with the BSS system via the server. In view of the importance of the server in the system, the server must be configured in accordance with the actual requirements of the OMCR system. This helps the server to work in optimum performance level. OMCR Workstation This serves as a front-end device to be used by various users. The user performs BSS management work, monitors and manages the OMCR system itself via the man-machine interface program running at the workstations. There can be multiple workstations in the system.
44
Peripherals (For example: printer)
Printer is used to print out the various data in the system, such as output of the information about measurement reports and alarms. The printer used in this diagram is a network printer with multiple functions and strong processing capability, but is expensive. Stand alone printer or scanner also can be configured in place of network printer. This is used for the network connection between the OMCR system and the foreground BSS system or the upper-level NMC. LAN is backbone structure of the OMCR system. Various components of OMCR system connects with each other using LAN. LAN uses 100 M ETHERNET to increase the data rate in the network.
Router and Switch Local Area Network
Running Environment
Hardware Environment
The hardware environment for operation of the ZXG10-OMCR system consists of the server and clients. The following are the requirements on the hardware equipment. Server
Number of Carrier Frequencies/Carr ier Frequency Equivalent 0500/01000 5001500/1000 2800 15002500/2800 4700 25004000/4700 7400 Configuration of SUN Machine V240\V280-1 V440\V280-2 V490-1\V480 V490-2\V880 Configuration of Fujitsu Machine PP250-1 PP250-2 PP450 PP650 Reference Configuratio n 1BSC(2RRM) 2BSC(6RRM) 3BSC(10RRM) 4BSC(16RRM)
SUN Machine Type table 1

SUN Machine Type V240 Number of CPUs Two ULTRASPARC IIIis One ULTRASPARC III Four ULTRASPARC Memory Disk [RAID1]
2 GB
2*73 GB
V280-1 V440
1 GB 8 GB
2*73 GB 2*73 GB
45
SUN Machine Type
Number of CPUs IIIs Two ULTRASPARC IIIs Two URTRASPARC IVs Four ULTRASPARC IIIs Four URTRASPARC IVs Eight ULTRASPARC IIIs
Memory
Disk [RAID1]
V280-2
4 GB
2*73 GB
V490-1
8 GB
2*146 GB
V480
8 GB
2*73 GB
V490-2
16 GB
2*146 GB
V880
16 GB
2*73 GB
SUN Machine Type table 2
SUN Machine Type V240 V280-1 V440
Disk Chassis [RAID1]
Actual disk size 1*73 GB 1*73 GB
Description
E3310-jbod(5*73 GB) E3310-jbod(5*73 GB) E3310-jbod(5*73 GB) E3310-jbod(7*73 GB) Four URTRASPARC IVs E3310-jbod(9*73 GB)
3*73 GB
One of disks as Hotspare One of disks as Hotspare One of disks as Hotspare One of disks as Hotspare One of disks as Hotspare One of disks as Hotspare
the the the the the the the the the the the the
V280-2
3*73 GB
V490-1
4*73 GB
V480
4*73 GB
V490-2
5*73 GB
V880
5*73 GB
46
Fujitsu Machine Type table 1

Fujitsu Machine Type PP250-1 PP250-2 PP450 PP650 Number of CPUs One SPARC64 V Two SPARC65 Vs Four SPARC64 V Six SPARC64 GPs Memory 2 GB 4 GB 8 GB 12 GB Disk 2*73 GB 2*73 GB 2*146 GB 2*146 GB
Fujitsu Machine type table2

Fujitsu Machine Type PP250-1 PP250-2 PP450 PP650 Expand File Unit(5*73 GB) Expand File Unit(5*73 GB) Expand File Unit(7*73 GB) Disk Chassis [RAID1] Actual disk size 1*73 GB 3*73 GB 4*73 GB 5*73 GB One of the disks as the Hotspare One of the disks as the Hotspare One of the disks as the Hotspare Description
Other devices
Disk Chassis [RAID1] Actual Disk Size 1*73 GB Expand File Unit(5*73 GB) Expand File Unit(5*73 GB) Expand File Unit(7*73 GB) 3*73 GB 4*73 GB 5*73 GB One of the disks as the Hotspare One of the disks as the Hotspare One of the disks as the Hotspare Description
Client
Ordinary PC Processor Memory HardDisk Network Adaptor CD-ROM Floppy OS
2 sets P4 1 GHz 512 MB 100 GB 10 M/100 M adaptive 32x CD-ROM 1.44 MB Windows 2000
47
Software Environment
Following are the software and operating systems related to ZXG10-OMCR system:

Sun Solaris 5.8 Microsoft Windows 2000 Sun Visual Workshop 5.0 Forte C/C++ Inprise C++ Builder 4.0 Oracle 8.1.7 Enterprise Edition for Solaris/IBM DB2 8.1.2 WorkGroup Edition/IBM DB2 8.1.2 Enterprise Edition Oracle 8.1.7 Client for Windows 2000 Microsoft Excel 2000 for Windows 2000 (this is necessary for creating a report in EXCEL form) ACE development environment of Vertel Co

Server Configuration
Server Hardware
Logically, the server should contain two types of equipment:

Host Storage device
Host
Host functions to process data. The processing speed of the host determines the system performance largely, and the host is a low-layer physical platform for the OMCR system running. Storage device serves as the place for data storage. To store large data of OMCR system uses external and independent data storage devices with large-capacity and high-reliability. According to the general principles of data storage, there should be two kinds of storage device: on-line storage device and offline storage device. On-line storage devices are used to provide the various data to the applications necessary for proper running, while the off-line devices are intended for fault recovery and offline data processing. Combining the host and storage devices, the server is able to provide a complete processing environment in line with the specific application requirements.
Storage device
48
Server Configuration Schemes

ZXG10-OMCR has three kinds of server configuration schemes, they are:

Integrated server configuration Dual-computer configuration Domain cascading configuration
Integrated Server Configuration Scheme
As the basic configuration scheme, it uses only one server. Integrated server implements functions of communication service, application service and DB service at the same time. Figure 12 shows the integrated server configuration scheme. Integrated server configuration scheme employs RAID to fully guarantee that the key data in the system will not get lost. RAID helps to improve system MTBF. This scheme is applicable when the system load is low (with 14 BSCs or less than 4,000 carrier frequencies) or there is less importance on reliability. If there are more BSCs or carrier frequencies to be managed, or more requirements on reliability, it is recommended to adopt the domain cascading configuration or dual-computer configuration.
FIGURE 12 INTEGRATED SERVER CONFIGURATION SCHEME
Dual Computer Configuration Scheme
Dual computer configuration scheme contains two servers and a disk array. These two server shares the data through the disk array, this is the basic principle of this scheme. Dual computer configuration scheme is as shown in Figure 13.
49
FIGURE 13 DUAL COMPUTER CONFIGURATION SCHEME

N M s erver (A c tive)
Disk array chassis
N M s erver (Standby) N M c lient N M c lient
LAN
M anaged networks
Working Principle: For easy understanding, assume two server names as Isb1 and Isb2.
Preparations for software installation

Install the Solaris operating system, Oracle database and the OMCR software on the Isb1 and Isb2 independently and respectively. The OMCR data is installed in the 3310 disk array. Install both the Veritas Cluster Server (VCS) and the Oracle Agent software on the Isb1 and Isb2 respectively. Both OMCR and Oracle run on the Isb1. Both OMCR and Oracle run on the Isb2. OMCR runs on the Isb1 and the Oracle on the Isb2. OMCR runs on the Isb2 and the Oracle on the Isb1.

OMCR can run in any of the following four modes:

Description
The four running modes can automatically switch (the failover mode) in the exceptional cases (system breakdown, the abnormal Oracle process or the abnormal OMCR process) without any impact on the external interfaces (including the BSC and OMCR). If the OMCR software is used to switch the running server, the system will be available in about 20 minutes. If the Oracle software is used to switch the running server, the system will be available in at most three minutes. That is, in the worst cases (either software or hardware), the OMCR is
50
out of service for at most 20 minutes. All these switches can be done automatically without user interference. The working principle of the dual-computer system employs the VCS software that is applied most widely in the industry with the highest reliability. The VCS can monitor the availability of the Isb1 and Isb2 through the Heartbeat, and at the same time, monitor the availability of the Oracle instance and Oracle listener, as well as that of the OMCR application. It will flag on an unavailable instance upon finding it (software or hardware). If it is the hardware, switches the software running on it to another computer; if it is the software, stops it running on the current computer and makes it run on another computer automatically.
Provides unified external interfaces through the mechanism of the dynamic IP address (namely the floating IP technology). For example, no matter an Oracle instance runs on the Isb1 or on the Isb2, you can access it consistently, because you can designate an IP address like oracleIp, which is dynamically on the Isb1 or on the Isb2. If the Oracle instance runs on the Isb1, the oracleIp takes effect on the Isb1 through the UNIX command ifconfig, while the Isb2 has no such address. If the Oracle instance should be switched to the Isb2, the VCS will delete the oracleIp from the Isb1 automatically and start it on the Isb2, and then run the Oracle instance on the Isb2. Then, when an external user accesses the Oracle instance through the oracleIp, the access mode will not be affected by the switch of the Oracle instance on the Isb1 and Isb2. This mode is also applicable to the switch of the OMCR software.
Domain Cascading Configuration Scheme
Domain cascading configuration scheme contains two or more servers. This configuration has the following advantages:
It flexibly adapts to device networks with various sizes, scales and capacities Manages network with medium capacity by a server with low cost Smooth NMS upgrade to adapt network capacity expansion without decreasing NMS performance and QoS.
Generally, the domain cascading mode manages device networks with large size and capacity. Domain cascading mode structure is as shown in Figure 14.
51
FIGURE 14 DOM AIN CASCADING CONFIGURATION SCHEME

OMC-Server( s) Client Terminal Upper Domain
TCP/IP Hub/Switch Router
LAN Client Terminal OMC-Server( s)
WAN OMC-Server( s) Router Router Local BSC
LAN Hub/Switch Lower Domain Local BSC Client Terminal Hub
In this configuration mode, one or some BSCs in an area are operated and maintained by an OMC independently. Different OMCs are responsible for operation and maintenance in different areas. These OMCs are called lower OMCs. All the lower OMCs can be connected to the upper-level OMC in a centralized way, which is called the upper OMC. In terms of users, such upper OMC can operate and maintain the BSCs in all the areas. However, all these operation and maintenance are implemented by the upper OMC through the lower OMCs. In addition, such centralization can be implemented gradually as required and at multi-levels. For example, apart from connecting some lower-level OMCs, the upper OMC also manages local devices. And such multiple upper OMCs can connect to the upper OMC of a higher upper-level NMC. The domain cascading configuration scheme has the following advantages:
Multi-level cascading: Cascading between the OMCs can be more than two levels. Local management: Apart from managing the NEs connecting to the various lower OMCs through the various cascaded lower OMCs, the upper OMC can also directly manage the NEs connected to the upper OMC. That is, the upper OMC has all the management functions of a local OMC. This function provides operators with more networking selections. When the physical location of an operators NE is identical to that of the upper OMC. The local management can be
52
implemented through the upper OMC directly without adding lower OMCs by the operator, thus saving the cost on devices.
Instant operation function of a cascaded OMC: The operation orders sent by the upper OMC for the NEs administrated by the lower OMCs should be responded within a short time. The lower OMCs should process the operation orders sent by the upper OMC in the same way as it processes the orders sent locally. The management function of the cascaded OMC: The upper OMC should implement all the management functions to realize such functions as configuration, fault, performance and security for the NEs administrated by all the lower OMCs. However, a lower OMC can only implement such functions as configuration, fault, performance and security for the NEs administrated by this OMC. But lower OMC do not have right to manage the NEs administrated by the upper OMC or the other lower OMCs.
53
54
Appendix
Abbreviations
Abbreviation A ASN.1 ATM B BSS C C/S CDF CLF CN CUI D DTRU F FMF G GSM GUI I IMF ITU ITU-T L LAF LMF Local Access Function Local Management Function Integration Management Function International Telecommunication Union ITU Telecommunications Standardization Sector Global System for Mobile Communication Graphical User Interface Fault Management Function Dual-carrier Transceiver Unit Client/Server Command Distribution Function Command Log management Function Core Network Character User Interface Base Station Subsystem Abstract Syntax Notation One Asynchronous Transfer Mode Full Name
55
Abbreviation M MF MIB MIF MML MO MSF MTBF N NAF NE NMC O O&M OMC OMCR OOF P PMF Q QoS T TFO TMN S SMF SSF U UISF W WSF
Full Name
Mediation Function Management Information Base MO Instance Tree Man Machine Language Managed Object Management Support Function Mean Time Between Failures
NMC Access Function Network Element Network Management Center
Operation & Maintenance Operation Maintenance Center Operation Maintenance Center of RNC Object-Oriented Function
Performance Management Function
Quality of Service
Tandem Free Operation Telecommunication Management Network
Security Management Function Session Service Function
User Interface Support Function
WorkStation Function
56
Appendix
Figures
Figure 1 OMCR Position in PLMN System .............................2 Figure 2 OMCR Architecture...............................................4 Figure 3 SOFTWARE Module Structure ...............................7 Figure 4 Hardware Structure .......................................... 12 Figure 5 Connection between BSS and OMCR.................... 20 Figure 6 TCP/IP Protocol Stack......................................... 22 Figure 7 Q3 Protocol Stack .............................................. 23 Figure 8 Network in A Interface Mode .............................. 42 Figure 9 Networking in X.25 Mode .................................... 43 Figure 10 Networking in DDN Leased Line Mode ................. 43 Figure 11 System Configuration Structure ......................... 44 Figure 12 Integrated Server Configuration Scheme ............. 49 Figure 13 Dual Computer Configuration Scheme................. 50 Figure 14 Domain Cascading Configuration Scheme ............ 52
57
58
Tables
Table 1 Manual Summary ...............................................viii Table 2 Typographical Conventions.................................... ix Table 3 Mouse Operation Conventions ................................ x Table 4 Operation Log Functions ..................................... 27 Table 5 Configuration Management Function ..................... 27 Table 6 Fault Management Functions ................................ 33 Table 7 Performance Management Functions...................... 37
59
60
Index
A Interface Mode................. 37 Alarm processing capability .. 15 BMF Module..........................9 Client ................................ 12 Client Configuration Management................... 29 Configuration Scheme.......... 48 Database storage capacity.... 16 DB interface ....................... 20 DDN Leased Line Mode ........ 39 Domain Cascading Configuration Scheme ...... 50 Dual Computer Configuration Scheme ......................... 49 Hardware Environment ........ 41 Host.................................. 48 Integrated Server ............... 48 LAF .....................................8 LAF Configuration Management .................................... 30 LAF Module ..........................9 LMF.....................................7 LMF Configuration Management .................................... 30 LMF Module ..........................8 Local Area Network ............. 41 M.3010................................4 M.3020................................4 M.3100................................4 M.3200................................4 M.3300................................4 M.3400................................4 MF Configuration Management .................................... 30 MO ..................................... 1 MSF .................................... 7 MSF Module ......................... 8 MTBF ................................ 17 NAF .................................... 7 NAF Module ......................... 8 Network ............................ 13 OAM Interface .................... 19 OMC in PLMN ....................... 2 OMCR Main Functions ............ 2 OMCR Relationship with Background ...................... 3 OMCR Server ..................... 40 OMCR Workstation .............. 40 OSI .................................... 1 Q3 Interface ...................... 20 Q3 Protocol ........................ 22 Server............................... 12 Server Configuration Schemes .................................... 48 Server Hardware ................ 48 Software Environment ....43, 47 Standards............................ 4 Storage device ................... 48 TCP/IP Protocol .................. 21 WSF Module ......................... 9 X.25 Mode ......................... 38 X.711.................................. 5 X.733.................................. 4 X.734.................................. 4 X.735.................................. 5
61

Sjzl20062296-ZXG10-BSS (V2 (1) .97) Network Management Techni

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sjzl20062296-ZXG10-BSS (V2 (1) .97) Network Management Techni

Uploaded by

Copyright:

Available Formats

ZXG10-BSS

Base Station Subsystem

Network Management Technical Manual

ZTE CORPORATION Values Your Comments & Suggestions!

This page is intentionally blank.

Chapter 1.......................................................................... 1 Network Management System Structure........................ 1

Chapter 2.......................................................................... 7 Software Structure .......................................................... 7

Chapter 3........................................................................ 11 Hardware Structure ....................................................... 11

Chapter 4........................................................................ 15 Technical Specification .................................................. 15

Ambient Conditions ............................................................. 16 Reliability Indices ................................................................ 17

Chapter 5........................................................................19 Interfaces and Protocols ...............................................19

Chapter 6........................................................................25 System Functions...........................................................25

Chapter 7........................................................................41 Networking Modes and System Configurations............41

About this Manual

Prerequisite Skill and Knowledge

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual

What is in this Manual

Confidential and Proprietary Information of ZTE CORPORATION

About this Manual -

ZXG10-BSC (V2.97) Installation Manual

Typeface Italics Quotes Bold

CAPS Constant width

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual

Mouse Operation Conventions

TABLE 3 MOUSE OPERATION CONVENTIONS

Typeface Click Double-click Right-click Drag

How to Get in Touch

Confidential and Proprietary Information of ZTE CORPORATION

Network Management System Structure

System Introduction System Background Standards Complied System Features

Position and functions of OMCR in PLMN systems OMCR main functions

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual

OMCR relationship with foreground

OMCR Main Functions

Physical resources configuration ATM and IPOA configuration No 7 signaling configuration

Confidential and Proprietary Information of ZTE CORPORATION

UChapter UTU1UT - Network Management System Structure -

OMCR Relationship with Background

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual

FIGURE 2 OMCR ARCHITECTURE

Confidential and Proprietary Information of ZTE CORPORATION

UChapter UTU1UT - Network Management System Structure -

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual

Confidential and Proprietary Information of ZTE CORPORATION

Software Module Structure Software Modules and Their Functions

Software Module Structure

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual

NAF Module LMF Module

Configuration Management Function (CMF)

Confidential and Proprietary Information of ZTE CORPORATION

UChapter UTU2UT - Software Structure -

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10-BSC (V2.97) Base Station Subsystem Network Management Technical Manual

This page is intentionally blank

Confidential and Proprietary Information of ZTE CORPORATION

OMCR Hardware Structure