CN102480373B - Method and device for managing interface content version of network management system - Google Patents

Abstract

The invention discloses a method for managing interface content version of a network management system. The method comprises the steps as follows: building an interface content version information base in a managed unit, maintaining the interface content version information in the interface content version information base when the managed unit is initialized or altered, adding the interface content version information to an interface interaction message by the managed unit, inquiring the interface content version information of the managed unit through an inquiry interface by a manage unit, and analyzing and comparing the interface content version information resolved from the interface interaction message. The invention also discloses a device for managing interface content version of the network management system. A version information maintenance module in the device is used for maintaining the interface content version information in the interface content version information base. Therefore, different interface content version information can be managed by unified management mechanism by the method and the device of the invention.

Description

Method and device for managing interface content version of network management system

technical field

The invention relates to management technology of interface content versions in the field of wireless network management, in particular to a management method and device for network management system interface content versions.

Background technique

For the management requirements in the network management field, there are currently a series of standards formulated by the 3GPP organization, namely the SA5 32 series. Among these standards, there is a complete version management scheme for the integrated reference point (IRP, Integrated Reference Point) of the management interface function, which is embodied in the 3GPP TS 32.312 standard, which specifies three access interfaces of IRP, namely: getIRPVersion (M), getOperationProfile(O), getNotificationProfile(O). Through the first access interface getIRPVersion(M), the user of the IRP manager as the integration reference point can know the current version number of the IRP, through the second access interface getOperationProfile(O) and the third access interface getNotificationProfile (O), the IRP manager can learn which management operations and notification functions are supported on this version, and then perform corresponding management operations. As shown in Figure 1a, it is a schematic diagram of management based on these three access interfaces, and the processing process includes: 1) Obtaining the function IRP version number through getIRPVersion(M); 2) Through getOperationProfile(O) and according to the obtained function IRP version number Query function details; 3) Query notification details through getNotificationProfile(O) and according to the obtained function IRP version number.

However, with the upgrading of the network and the expansion of the network management scale, the existing version management mechanism can no longer meet the needs of users. It is mainly reflected in the lack of effective means to manage the interface content version, because in a complex network environment with multiple managed unit versions, when the IRP Manager interacts with the managed unit agent (IRP Agent) through the interface, in most cases, although the interface The function has not changed, but the interface interaction content needs to be compatible with different versions of managed units, which requires a unified management mechanism that can manage different interface content version information and combine it with the interface function version.

For example, the alarm message reporting interface, which parameters are included in the alarm message, these standards related to interface functions are relatively stable, but the specific content of message parameters such as alarm codes, handling suggestions, etc. are constantly changing with equipment upgrades and management requirements. The alarm code and related information concerned by the manager may have content differences in different network element versions. The manager not only needs to know which fields are reported in the current alarm message (this is defined in the interface function IRP, the difference between more and less parameters is determined by It is more necessary to understand the meaning of the content of the alarm message field, analyze and manage the content version.

Another example is the performance management interface, how to deliver measurement tasks, and how to report measurement files. The interaction mechanism of these interfaces is relatively stable, and the IRP versions of different interface functions are not very different, but the interface information content corresponding to the IRP: network element measurement Types and specific counters are constantly evolving and changing, and there is currently no uniform way to obtain the version of the performance content object through the integration reference point (PM IRP) of the performance management function.

Another example is the configuration management interface, which also has the problem of the NRM resource model version corresponding to the interface content. Although there is a management method of getNRMVersion, the management interface is not perfect, and it is impossible to know the network resource management (NRM) corresponding to a specific configuration object. The version number of the system, and there is no query interface. The detailed information of the configuration objects supported by the NRM system version can be obtained through the version number of the NRM system.

To sum up, in a complex network environment with multiple versions of managed units, the existing version management mechanism can no longer meet the needs of users, mainly reflected in the lack of effective means to manage version information of different interface content. At present, there is an urgent need to A unified management mechanism can manage different interface content version information.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method and device for managing interface content versions of a network management system, which can manage different interface content version information with a unified management mechanism.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A method for managing interface content versions of a network management system, the method comprising:

Establish an interface content version information library in the managed unit, and maintain the interface content version information in the interface content version information library when the managed unit is initialized or changed;

The managed unit adds interface content version information to the interface interaction message;

The management unit queries the managed unit for interface content version information through the query interface, and analyzes and compares it with the interface content version information parsed from the interface interaction message.

Wherein, the interface content version information at least includes: interface content version number, interface content version type, interface content compatible version number, detailed content of interface content version information, and associated interface function version information.

Wherein, the type of the query interface at least includes: an interface for obtaining the version number of the interface content, and an interface for obtaining the detailed content of the interface content version information;

The interface interaction message feeds back the interface feedback content including the interface content version information to the management unit through the feedback interface.

Wherein, the managed unit is a network element management system (EMS) or a network element (NE); the management unit is a network management system (NMS) or EMS.

A device for managing version content of a network management system interface, the device comprising: a version information maintenance module, a version information processing module, and a version information query and analysis module; wherein,

The version information maintenance module is located on the side of the managed unit and is used to maintain the interface content version information in the interface content version information library;

The version information processing module is located on the side of the managed unit and is used to add the interface content version information to the interface interaction message;

The version information query and analysis module is located on the side of the management unit, and is used to query the version information of the interface content from the version information maintenance module through the query interface, receive the interface interaction message sent by the version information processing module, and analyze the interface interaction message from the interface interaction message. Analyze and compare interface content version information.

Wherein, the version information processing module is further configured to feed back the interface feedback content including the interface content version information to the management unit through the feedback interface;

The type of the query interface at least includes: an interface for obtaining the version number of the interface content, and an interface for obtaining detailed content of the version information of the interface content.

Wherein, the managed unit is EMS or NE; the management unit is NMS or EMS.

The present invention establishes an interface content version information library in the managed unit, and maintains the interface content version information in the interface content version information library when the managed unit is initialized or changed; the managed unit adds the interface content version information in the interface interaction message; The management unit queries the managed unit for interface content version information through the query interface, and analyzes and compares it with the interface content version information parsed from the interface interaction message. By adopting the invention, the version information of the interface content of the managed unit can be uniformly maintained, and the management unit can flexibly use the version information of the interface content of the managed unit.

Description of drawings

Figure 1a is a schematic diagram of the version management process of the existing interface function IRP;

Fig. 1b is a schematic flow chart of the interface content version management method of the present invention;

Figure 1c is a schematic diagram of the composition and structure of the interface content version management device of the present invention;

Fig. 2 is a schematic diagram of an example of interface content version maintenance in the present invention;

Fig. 3 is a schematic flow diagram of an example of the present invention querying the interface content version through the interface;

Fig. 4 is a schematic flowchart of an example of adding an interface content version to interface interaction content in the present invention.

Detailed ways

The basic idea of the present invention is: establish the interface content version information database in the managed unit, when the managed unit initializes or changes, maintain the interface content version information in the interface content version information database; the managed unit adds the interface content version information in the interface interaction message Interface content version information; the management unit queries the managed unit for the interface content version information through the query interface, and analyzes and compares it with the interface content version information parsed from the interface interaction message.

The present invention will be further described below with reference to the accompanying drawings and embodiments.

A method for managing interface content versions of a network management system, mainly including the following contents:

1. Establish an interface content version information base in the managed unit, and actively maintain the interface content version information in the interface content version information base when the managed unit is initialized or changed.

Here, the interface content version information in the interface content version information database can also be maintained through the established version information maintenance module for maintaining the interface content version information. The version information maintenance module is located on the side of the managed unit.

2. The managed unit adds interface content version information to the interface interaction message.

Here, the interface content version information includes but not limited to the following items: interface content version number, interface content version type, interface content compatible version number, detailed content of interface content version information, and associated interface function version information.

3. The management unit can query the interface content version information from the managed unit through the query interface (such as the three specific query interfaces in the following embodiment 1), and analyze and compare it with the interface content version information parsed from the interface interaction message .

Here, the managed unit may be a network element management system (EMS) or NE (network element); the management unit may be a network management system (NMS) or EMS.

A device for managing version content of a network management system interface mainly includes the following contents:

The version information maintenance module is located at the managed unit side and is used for maintaining the interface content version information in the interface content version information database.

The version information processing module is located on the side of the managed unit, and is used for adding the interface content version information into the interface interaction message.

The version information query and analysis module is located on the side of the management unit, and is used to query the version information of the interface content from the version information maintenance module through the query interface, receive the interface interaction message sent by the version information processing module, and analyze the interface content from the interface interaction message Version information for analysis and comparison.

To sum up, by adopting the present invention, the interface content version information of managed units can be maintained uniformly. Furthermore, since the interface content version information can exist in the form of subclasses, that is, different objects correspond to different interface content version information, at this time, when the interface content version information exists in the form of subclasses, it can be called interface content object version information , respectively corresponding to different objects, located in different interface content object instances. Therefore, by adopting the present invention, it is also possible to uniformly maintain the interface content object version information and its attributes in the network; query the interface content version information and its detailed information; obtain the corresponding interface content version information from the interface content object instance.

The present invention is described with examples below.

Embodiment 1: As shown in Figure 1b, this embodiment comprises the following steps:

Step 101, the management unit inquires from the managed unit and obtains the version number of the interface content.

Step 102, according to the version number of the interface content, the management unit queries the managed unit to obtain the version information of the interface content.

Step 103, the management unit receives the interface interaction message including the interface content version information from the managed unit, and analyzes and compares it with the interface content version information obtained from the query.

Specifically, the management unit mainly interacts with the managed unit through the following three types of interfaces:

One: The management unit obtains the version number of the interface content through the first type of query interface (version number query interface). Queries can be made in the following ways:

Method 1. Use the version number of the function IRP as an input parameter to query the content version associated with the function IRP version, or define getContentVersion in the base class of the IRP. All interface function IRPs must implement this method.

Method 2. Using the content version type as an input parameter, query all content versions supported by the managed unit under this type.

Method 3. The input parameter is empty, and the query obtains all content versions supported by the managed unit.

Method 4. Query which content versions support the content version object according to the content version object.

2. The management unit obtains the detailed content of the interface content version information through the second type of query interface (version details query interface), that is, the specific details of the interface content version information. Queries can be made in the following ways:

Method 1. According to the interface content version number, query all the detailed information of the content version information corresponding to the version number.

3. The managed unit feeds back the interface feedback content including the content version information to the managed unit through the third type interface (also called the content version information feedback interface).

Here, the interface feedback content can be as follows:

1) Notification message sent by the managed unit to the management unit;

2) The managed unit synchronously returns the operation response to the management unit;

3) Files generated by managed units.

Embodiment 2: As shown in Figure 1c, an example of a device of the present invention includes: a version information maintenance module, a version information processing module, and a version information query and analysis module. Among them, the version information maintenance module is located on the side of the managed unit, responsible for maintaining the version information of the interface content and providing query; the version information processing module is located on the side of the managed unit, and is responsible for adding the interface content version to the interface feedback content (specifically, it can be an interface interaction message) information. The version information query and analysis module is located on the side of the management unit, responsible for querying the interface content version information, and analyzing and comparing the interface content version information in the interface feedback content with the interface content version information obtained from the query.

Embodiment 3: As shown in Figure 2, it is a schematic diagram of an example of interface content version maintenance in the present invention, and the maintenance of content version information can be in the following manner:

The version information maintenance module contains an interface content version information library. Each interface content version object registers its own detailed information with the interface content version information library when it is initialized. When the version is no longer being used due to upgrade or other reasons When used in a management unit, the interface content version object deregisters (detach) its own version number from the interface content version repository. After the registration and deregistration actions are completed, the interface content version repository will send out a content version change message. The change message includes the content version number and the change action.

The above registration and deregistration actions occur in the following situations:

Scenario 1: A new interface content version object is added to the managed unit;

Scenario 2: The old interface content version object exits the managed unit;

Scenario 3: The version of the interface content is upgraded, and there are new versions and exits at the same time.

Embodiment 4: The interface content version information model can be defined by the fields in the following Table 1 (ContentVersion IOC).

Table 1

Embodiment 5: As shown in Figure 3, it is a schematic flow diagram of an example of the present invention querying the interface content version through the interface. This embodiment includes the following steps:

Step 201. First, the management unit sends a request to the managed unit through an existing standard interface, such as the getIRPVersion interface of the functional IRP or the getIRPOutline interface of the EPIRP.

Step 202, obtain the version number of the function IRP of the current managed unit from the request response.

Step 203, query the associated content version number through the function IRP version number, and this association relationship is reflected in the interface IRP information of the content version information.

Step 204, obtain the queried content version number from the request response.

Step 205, query the detailed information of the content version according to the acquired content version number.

Step 206, obtain detailed information of the content version queried from the request response.

Embodiment 6: As shown in Figure 4, it is a schematic flow diagram of an example of adding an interface content version to the interface interactive content of the present invention. For a specific interface content object instance, if there is a need for corresponding content version management, it is necessary to add a content version identifier to clarify Indicate the content version to which the instance belongs, refer to several specific examples:

Example 1: As far as messages are concerned, specifically for alarm messages and alarm objects, the original field domain_name already contains the version number of the interface IRP, so this field is extended to add the version number of the content object. The new content version attribute in the alarm information object AlarmInformation (3GPP 32.311 5.3.1.2).

Example 2: As far as the object is concerned, specifically for the configuration object, the attribute of the resource model version number is uniformly added in the top IOC: Top(3GPP 32.622 6.1.3.8.2). For configuration files, the content version information is added to the fileFormatVersion field in the file header. For the configuration message, like the alarm message, the content version information is expanded in the domain_name.

Example 3: For files, specifically for performance data files, the fileFormatVersion field in the file header is extended to add version information. For performance messages, like alarm messages, the content version information is expanded in domain_name. Add the content version attribute to the performance measurement type object MeasuredAttribute (3GPP 32.4126.3.5).

To sum up, there are three main ways to add content version information to the interface feedback content (specifically, the above-mentioned interface interaction messages):

Method 1: Add content version information to the file version field of the interface generated file;

Method 2: Add content version information to the message domain field of the interface message;

Method 3: Add a content version information field in the interface interaction object properties.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (7)

1. A management method for content version of network management system interface is characterized in that the method comprises:

establishing an interface content version information base in a managed unit, and maintaining the interface content version information in the interface content version information base when the managed unit is initialized or changed;

the managed unit adds interface content version information in the interface interaction message;

the management unit inquires the interface content version information from the managed unit through the inquiry interface and analyzes and compares the interface content version information with the interface content version information analyzed from the interface interaction message.

2. The method of claim 1, wherein the interface content version information comprises at least: interface content version number, interface content version type, interface content compatible version number, detailed content of interface content version information, and associated interface function version information.

3. The method of claim 1, wherein the type of the query interface comprises at least: the interface is used for acquiring the version number of the interface content and acquiring the detailed content of the version information of the interface content;

and the interface interaction message feeds back the interface feedback content containing the interface content version information to the management unit through a feedback interface.

4. The method according to any one of claims 1 to 3, wherein the managed element is a network element management system or a network element; the management unit is a network management system or a network element management system.

5. A management device for content versions of network management system interfaces is characterized in that the device comprises: the system comprises a version information maintenance module, a version information processing module and a version information query and analysis module; wherein,

the version information maintenance module is positioned at the managed unit side and used for maintaining the interface content version information in the interface content version information base;

the version information processing module is positioned at the managed unit side and used for adding the interface content version information into the interface interaction message;

the version information inquiry and analysis module is positioned at the management unit side and used for inquiring the interface content version information from the version information maintenance module through the inquiry interface and analyzing and comparing the interface content version information analyzed from the interface interaction message sent by the version information processing module.

6. The apparatus of claim 5, wherein the version information processing module is further configured to feed back interface feedback content containing the interface content version information to the management unit through a feedback interface;

the types of the query interface at least include: the interface is used for acquiring the version number of the interface content and acquiring the detail content of the version information of the interface content.

7. The apparatus of claim 5 or 6, wherein the managed element is a network element management system or a network element; the management unit is a network management system or a network element management system.