CN100375443C - A method for accessing a mobile communication service management system to a network element management system - Google Patents

Abstract

The invention discloses a method for a mobile communication service management system to access a network element management system, comprising the following steps: providing a CORBA naming service and setting a naming rule of an entry integration reference point; publishing a naming context object reference of the CORBA naming service; and other The integration reference point registers the corresponding object reference with the entry integration reference point, so that the entry integration reference point obtains the object reference in the management domain, and the other integration reference points and the entry integration reference point are CORBA objects; the entry integration reference point is based on the naming rules and naming context object references Register the corresponding registered name and the object reference in the management domain in the naming tree of the naming service; and the business management system obtains the object references of other integration reference points according to the corresponding name and the object reference in the management domain. The present invention avoids manual transmission of a large number of EPIRPs, and only needs equipment vendors to deploy their own interface objects according to operator's naming rules and notified naming service context object references to complete this process automatically.

Description

A method for accessing a mobile communication service management system to a network element management system

technical field

The present invention relates to a method for accessing a network element management system such as a network management system and a resource management system in a third-generation mobile communication system, and in particular to a method for solving the difficulty of initial access in the past to provide a certain degree of automatic configuration capability A method for the service management system to access the network element management system.

Background technique

In the management system of telecom operators, the performance analysis platform, resource management system, bureau data management system, and performance management, configuration management, fault management and other systems required for daily operation and maintenance need to be connected to the network element management system to obtain various information , including network element alarms, current operating status data (KPI, Key Process Indicator), network element configuration data, etc., and create configuration objects, create performance collection tasks, and create performance threshold monitors through the network element management system.

As shown in Figure 1, for operators, often a set of management systems need to access not only the network element management system of one type of equipment, but for 3G systems, there will be more than one type of WCDMA/TD-SCDMA/CDMA2000 equipment OMC (Operation and Maintenance Center), and each type of network element management system is often divided into OMC-R (Operation and Maintenance Center for Radio Access Network) and OMC-S (Operation and Maintenance Center for Core Network) according to the radio access network and core network. maintenance center), as shown in FIG. 1 , even some operators need a management system to access the management system 100 of 2G equipment at the same time. Therefore, how to simplify the process of connecting the management system to the network element management system and improve the degree of automation and intelligence is of great significance.

In the second-generation mobile communication system and other communication systems, due to the lack of standardization of the interface between the network element management system and the upper-layer management system, the access of the upper-layer management system is extremely complicated and there are huge differences in the access methods of different equipment vendors. question. In the third generation mobile communication system, there is no unified solution on how to access this interface. As a result, network element equipment vendors dominate the way in which the service management system accesses the network element management system, and there are various access methods provided by various equipment vendors, which makes it difficult for operators to plan in a unified manner, and also leads In the process of accessing the upper management system of the network element management system, adaptation of various access methods is required, which increases the difficulty of development and debugging.

At present, the interface provided by the network element management system is N interface, which is divided into several interfaces according to the management function domain: basicCmIRP (IRP: Integrated Reference Point, basic configuration management function reference point), alarmIRP (alarm management reference point), PmIRP (performance Management Reference Point), NoticficationIRP (Notification Management Reference Point), FTIRP (File Transfer Reference Point), kemelCmIRP (Configuration Notification Management Reference Point), EPIRP (EntryPoint Integrated Reference Point: Entry Reference Point), etc., respectively complete configuration management and alarm management , performance management, notification report management, file transfer management, etc.

At present, there are three types of protocols for interfaces: CORBA, CMIP, and SNMP, but most equipment manufacturers and operators use CORBA interfaces. When the CORBA protocol is adopted, the interface needs to be implemented as a CORBA object by the network element management system. When the network management system or resource management system accesses the network element management system for any operation, it first needs to obtain the interoperable object reference (IOR: Interoperable Object Reference) of the CORBA object. Object Reference) for subsequent operations. The object reference contains all the information of the location server program and the service object, and acts as a handle. According to the OMG (Object Management Group) specification, the object reference IOR in the form of a standardized string can be used to identify the unique target object. What is encapsulated in the IOR is the specific information of the object reference, including information such as the host computer where the CORBA object is located, the port number, and the keyword of the CORBA object. Three parts, RepositoryID201 is used to describe the unique location of the interface in the interface library, Transport Address 202 contains the description of the transmission protocol and the specific physical transmission address, Object Key 203 is the unique identifier of the CORBA object on the ORB where it is located, and generally includes the POA mark POAId and object mark ObjectId two parts.

How to obtain the object references of all these objects is a problem, and from the above description, it can be seen that an object reference contains the IP address of the computer where it is located, the TCP port number it is listening to, the keyword of the object, etc., and the specific interface object Deployment-related information, which is easily changed due to computer restarts or changes in object deployment methods. At present, the commonly used way to obtain these object references is to serialize it to a file or directly transfer the IOR string to the caller (operator business management system) through Email or disk copy. Now an EPIRP is proposed in the specification, and the management system can query other object references from this object, but there is still no way for the management system to obtain the object reference of the EPIRP.

Contents of the invention

The purpose of the present invention is to provide a method for accessing a mobile communication service management system to a network element management system. By using this method, various service management systems of operators can conveniently obtain object references of each interface to access network element management. system, and can automatically complete the re-connection process when the network element management system is restarted or the interface changes.

In order to achieve the above object, the present invention provides a method for a mobile communication service management system to access a network element management system, which is used in a third-generation mobile communication system. The interface provided by the network element management system is an N interface, and the N The interface is divided into entry integration reference points and other integration reference points according to functional domains, including the following steps:

Step a, the business management system provides CORBA naming service;

Step b, the service management system announces the naming context object reference of the CORBA naming service to the network element management system entering the management scope;

Step c, the other integration reference points register corresponding object references with the entry integration reference point, so that the entry integration reference point obtains object references in the management domain, and the other integration reference points and the entry integration reference point are CORBA object;

Step d, the entry integration reference point registers the corresponding registration name on the naming tree of the naming service according to the naming rules provided by the mobile communication system and the naming context object reference, and references the object in the management domain bound to the corresponding named tree; and

In step e, the business management system obtains the object references of the other integration reference points according to the registered names.

The above-mentioned method for accessing the network element management system by the mobile communication service management system is characterized in that, after the step e, the steps further include:

Step f, updating the corresponding object reference registered in the entry integration reference point after the object state of the other integration reference point changes, so that the entry integration reference point obtains the object reference in the second management domain;

In step g, the entry integration reference point reports the object reference in the second management domain to the service management system.

The above-mentioned method for accessing the network element management system by the mobile communication service management system is characterized in that, in the step c, the other integration reference points send information to the entry through the internal interface of the entry integration reference point or information file exchange mode The integration reference point registers the corresponding object reference.

The above-mentioned method for accessing the network element management system of the mobile communication service management system is characterized in that, in the step b, the service management system publishes the name of the CORBA naming service to the network element management system through an open listening port Context object reference.

The above-mentioned method for accessing the network element management system by the mobile communication service management system is characterized in that the other integration reference points include basic configuration management function reference points, alarm management reference points, performance management reference points, notification management reference points, file Transport reference point and configuration notification management reference point.

In order to better achieve the above object, the present invention also provides a method for the mobile communication service management system to access the network element management system, which is used in the third generation mobile communication system, and the interface provided by the network element management system is an N interface , the N interface is divided into entry integration reference points and other integration reference points according to functional domains, which includes the following steps:

Step a, the business management system provides CORBA naming service;

Step b, the service management system publishes the naming context object reference of the CORBA naming service to the network element management system that enters its management scope;

Step c, the entry integration reference point registers the corresponding registered name on the naming tree of the naming service according to the naming rule and the naming context object reference;

In step d, the other integration reference points directly register their object references under the entry integration reference points corresponding to the naming tree, and the other integration reference points and the entry integration reference points are CORBA objects; and

In step e, the service management system obtains the object references of the other integration reference points according to the registered names.

The above-mentioned method for accessing the network element management system by the mobile communication service management system, wherein, after the step e, further includes the steps:

Step f, updating the corresponding object reference registered in the entry integration reference point after the object state of the other integration reference point changes, so that the entry integration reference point obtains the object reference in the second management domain;

In step g, the entry integration reference point reports the object reference in the second management domain to the service management system.

The above-mentioned method for accessing the network element management system by the mobile communication service management system, wherein, in the step b, the service management system publishes the naming context object of the CORBA naming service to the network element management system through an open listening port quote.

The method for accessing the network element management system by the mobile communication service management system above, wherein the other integration reference points include basic configuration management function reference points, alarm management reference points, performance management reference points, notification management reference points, and file transfer reference points Point and configuration notification management reference point.

The method for accessing the mobile communication service management system of the present invention to the network element management system registers object references of other integrated reference points in the EPIRP by using the naming service, and then the EPIRP is correspondingly registered in the Naming Service, and the operator's service management system queries the name The tree discovers the new EPIRP and gets its object reference. This avoids the need to manually transmit a large number of EPIRPs, and only needs the device manufacturer to deploy its own interface objects according to the operator's naming rules and the object reference of the notified naming service context, and the process can be completely automated.

The present invention will be described in detail below in conjunction with the accompanying drawings and embodiments.

Description of drawings

Fig. 1 is the structural diagram of EMS (network element management system) and network element managed by NMS;

Fig. 2 is a composition structure chart of CORBA object reference;

Fig. 3 is the name tree structure in the naming service of the operator's business management system;

Fig. 4 is a processing flowchart of the method of the present invention.

Detailed ways

In order to achieve the purpose of the invention, the invention provides the following implementation methods, as follows:

First of all, within a network element management system, the IRP objects of each functional domain, namely basicCmIRP, alarmIRP, PmIRP, NoticficationIRP, FTIRP, and kemelCmIRP objects, need to register their own object references with EPIRP, so as to achieve EPIRP to obtain object references in the management domain .

The operator provides the CORBA naming service and sets the naming rules of the EPIRP of each equipment manufacturer. The equipment manufacturer's EPIRP registers its own name and object reference on the operator's naming service according to the rules. The operator's business management system queries the naming tree Discover the new EPIRP and get its object reference. This avoids the need to manually transmit a large number of EPIRPs, and only needs the device manufacturer to deploy its own interface objects according to the operator's naming rules and the object reference of the notified naming service context, and the process can be completely automated. Equipment vendors can even use the above two information as deployment configuration input alone, and let their EPIRP interface object dynamically load these two configuration input information to complete automatic processing.

The operator's service management system obtains the IOR of other IRP objects in the network element management system through the EPIRP.

When the state of an IRP object within a network element management system domain changes, it actively updates its registration information in the EPIRP, and the EPIRP notifies the operator of the state change of the service management system object according to the change of the registration information.

In order to facilitate the description of the interface, the scene used in the present invention is exemplified as follows with the IDL (Interface Definition Language) of CORBA.

//File "NMSNameServiceConstDefs.idl"

//The IRP document version number is "NMSNameService V1.0"

#ifndef_NMSNAMESERVICECONSTDEFS_IDL_

#define_NMSNAMESERVICECONSTDEFS_IDL_

module NMSNameServiceConstDefs

{

interface CompanyNameValue

{

const string cl="ZTE";

const string c2 = "NOKIA";

const string c3 = "MOTO";

};

interface NetworkNameValue

{

const string w1 = "WCDMA";

const string w2 = "TD-SCDMA";

const string w3 = "CDMA2000";

const string w4 = "GSM";

};

interface ElementTypeValue

{

const string et1 = "WCDMA";

const string et2 = "TD-SCDMA";

const string et3 = "CDMA2000";

const string et4 = "GSM";

};

interface ElementNameValue

{

const string en1 = "RNC";

cons strng en2 = "NODEB";

const string en3 = "BSC";

const string en4 = "BTS";

};

interface ElementIDValue

{

const string ei1 = "1";

const string ei2 = "2";

const string ei3 = "3";

};

};

#endif//_NMSNAMESERVICECONSTDEFS_IDL_

FIG. 4 is a detailed flow chart of an embodiment of the method of the present invention. For convenience of description, basicCmIRP, alarmIRP, PmIRP, NoticficationIRP, FTIRP, and kemelCmIRP in the present invention are named as other integration reference points.

As shown in Figure 4, a CORBA naming service is deployed in the environment in the operator's management system, and the object reference can be queried according to the name through the naming service, which includes the following steps:

Step 110: the operator's service management system NMS is started, and the CORBA naming service is started;

Step 120: When an equipment vendor's network element management system EMS enters the management scope of the operator's service management system, the operator announces the naming context object reference of the CORBA naming service to the equipment vendor, and the publishing method can be NMS (Network Management System, Network The management system (that is, the system used by the operator to manage the telecommunications network) server opens a listening port, such as a TCP10000 port. After the network element management system enters the network, it actively establishes a link and sends authentication information to this port. After authorization, the IOR of the CORBA naming service context object will be sent and saved by EPIRP;

Step 130: After the CORBA objects of other integrated reference points (basicCmIRP, alarmIRP, PmIRP, NoticficationIRP, FTIRP, kemelCmIRP) in EMS are activated, query the EPIRP storage information in step 120 to obtain the object reference of EPIRP, and actively register yourself with EPIRP The registration method can use the internal interface provided by EPIRP to complete the registration, or use information file exchange, or use the naming service to directly register to the naming tree with the name of the IRP, but in order to avoid conflicts among multiple equipment vendors If there is a naming conflict, it must be bound under its corresponding EPIRP. The naming tree structure can be shown in Figure 3. The top layer 31 is the root node, and the first layer 32 below is the abbreviation of the equipment manufacturer (such as ZTE/Lucent/Nokia, etc. ), the second layer 33 is the network type managed by the network element management system (such as WCDMA/TD-SCDMMCDMA2000, etc., even GSM can be added), and the third layer 34 is the EPIRP in the network element management system, and the name is "network element Type-network element ID-geographic location description", the fourth layer 35 is other integration reference points corresponding to EPIRP;

Step 140: After receiving the information in step 120, each network element management system EMS automatically registers the name of the EPIRP to the corresponding position on the naming tree. The name of the EPIRP can be automatically generated according to the rules specified by the operator. As shown in Figure 3, a ZTE RNC network element management system 34 can be named "RNC-02-BJ", then the name of this EPIRP can be defined as root/ZTE/WCDMA/RNC-02-BJ starting from the root node ;

Step 150: After obtaining the context object reference of the CORBA naming service and its own EPIRP name, the network element management system EMS automatically binds its own object reference to the operator's naming tree;

Step 160: Since the name of the EPIRP is standardized, the management system can discover the EPIRP through the name, and obtain its object reference through the name; the operator's network management system NMS traverses the naming tree, and finds that there is a newly added network element management system EMS The EPIRP completes the registration, and its object reference is queried through the name of the new EPIRP;

Step 170: The operator's network management system NMS queries the object references of basicCmIRP, alarmIRP, PmIRP, NoticficationIRP, FTIRP, and kemelCmIRP through EPIRP;

Step 180: determine whether the CORBA object of xxxIRP (one of basicCmIRP, alarmIRP, PmIRP, NotiicficationIRP, FTIRP, kemelCmIRP) stops running, restarts (such as the restart caused by upgrading) and other state changes;

Step 190: The xxxIRP object whose status has changed updates its own IOR registration information to EPIRP, in a manner similar to that described in step (130).

Step 200: The EPIRP reports an object change message to the operator's service management system, notifying it that an object reference of a certain IRP has changed, or that the activation state of a certain object has changed, thereby generating a new object reference.

Of course, the present invention can also have other various embodiments, and those skilled in the art can make various corresponding changes and deformations according to the present invention without departing from the spirit and essence of the present invention, but these corresponding Changes and deformations should belong to the scope of protection of the appended claims of the present invention.

Claims (5)

1. the method for an access network element managing system for mobile communication service managing system, be used for 3-G (Generation Three mobile communication system), the interface that described Element management system provides is the N interface, described N interface is divided into inlet integrated reference point and other integrated reference point by functional domain, it is characterized in that, may further comprise the steps:

Step a, described business management system provides CORBA name service;

Step b, described business management system is announced the naming context object reference of described CORBA name service to the described Element management system that enters its range of management;

Step c, described other integrated reference point is registered corresponding object reference to described inlet integrated reference point, makes described inlet integrated reference point obtain object reference in the management domain, and described other integrated reference point and described inlet integrated reference point are the CORBA object;

Steps d, described inlet integrated reference point is registered name accordingly according to the naming rule that provides and the registration on the naming tree of described name service of described naming context object reference of described business management system, and object reference in the described management domain is tied on the corresponding naming tree; And

Step e, described business management system is obtained the object reference of described other integrated reference point according to described registration name.

2. the method for access network element managing system for mobile communication service managing system according to claim 1 is characterized in that, also comprises step after the described step e:

Upgrade its object reference after step f, the Obj State of described other integrated reference point change, make described inlet integrated reference point obtain object reference in second management domain in the correspondence of described inlet integrated reference point registration;

Step g, described inlet integrated reference point is object reference in described business management system reports described second management domain.

3. the method for access network element managing system for mobile communication service managing system according to claim 1 and 2, it is characterized in that, among the described step c, described other integrated reference point is registered corresponding object reference by described inlet integrated reference point internal interface or message file exchanged form to described inlet integrated reference point.

4. the method for access network element managing system for mobile communication service managing system according to claim 1 and 2, it is characterized in that, among the described step b, described business management system is announced the naming context object reference of described CORBA name service to described Element management system by open listening port.

5. the method for access network element managing system for mobile communication service managing system according to claim 1 and 2, it is characterized in that described other integrated reference point comprises basic configuration management function reference point, alarm management reference point, performance management reference point, notice management reference point, file transfer reference point and configuration notification management reference point.

Images