Management method and device for interface content version of network management system
Technical Field
The invention relates to a management technology of interface content versions in the field of wireless network management, in particular to a management method and a device of interface content versions of a network management system.
Background
For the management requirement in the field of network management, there are a series of standards, namely the SA 532 series, established by the 3GPP organization. In these standards, there is a perfect version management scheme for an Integrated Reference Point (IRP) for managing interface functions, which is specifically embodied in the 3GPP TS 32.312 standard, where the standard specifies three access interfaces of the IRP, that is: getIRPVersion (M), getOperationProfile (O), getNotification Profile (O). Through the first access interface getirpversion (m), a user of an administrator (IRP manager) as an integration reference point can know the current version number of the IRP, and through the second access interface getoperationprofile (o) and the third access interface getnotifiationprofile (o), the IRP manager can know which management operations and notification functions are supported on the version, so as to perform corresponding management operations. As shown in fig. 1a, a schematic diagram of management according to the three access interfaces is shown, and the processing procedure includes: 1) acquiring a function IRP version number through getIRPVersion (M); 2) inquiring function details according to the acquired function IRP version number through getOperationProfile (O); 3) the notification details are queried by getNotification Profile (O) and according to the already obtained function IRP version number.
However, as the network is updated and upgraded, and the network management scale is enlarged, the existing version management mechanism cannot meet the user requirements. The method is mainly embodied in the lack of an effective means for managing interface content versions, because in a complex network environment with multiple managed unit versions, when an IRP Manager interacts with an managed unit Agent (IRP Agent) through an interface, in most cases, although the interface function is not changed, managed units compatible with different versions are required in interface interaction content, so that a uniform management mechanism is required to manage different interface content version information and can be combined with the interface function versions.
For example, the alarm message reports to the interface, which parameters are included in the alarm message, and these standards related to the interface function are relatively stable, but the specific contents of the message parameters, such as the alarm code, the processing suggestion, etc., are constantly changed with the requirements of device upgrade and management, the alarm code and the related information concerned by the manager may have content differences on different network element versions, and the manager not only needs to know which fields are reported in the current alarm message (this is defined in the interface function IRP, and the differences of more and less parameters are distinguished on the interface function version), but also needs to know the content meaning of the alarm message fields, and analyze and manage the content version.
As another example, the performance management interface is how to issue the measurement task and how to report the measurement file, these interface interaction mechanisms are relatively stable, the IRP versions of different interface functions are not very different, but the interface information content corresponding to the IRP is: network element measurement types and specific counters are constantly developed and changed, and at present, no unified way is available for acquiring the version of a performance content object through an integrated reference point (PM IRP) of a performance management function.
As for the configuration management interface, there is also a problem of the NRM resource model version corresponding to the interface content, although there is a management method of getnrmverson, the management interface is not perfect, the version number of the Network Resource Management (NRM) system corresponding to a specific configuration object cannot be known, and there is no inquiry interface that can obtain the detailed information of the configuration object supported by the NRM system version through the version number of the NRM system.
In summary, in a complex network environment with multiple managed unit versions, the existing version management mechanism cannot meet the user requirements, which is mainly reflected in the lack of an effective means for managing different interface content version information, and a unified management mechanism is urgently needed to manage different interface content version information.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and an apparatus for managing interface content versions in a network management system, which can manage different interface content version information by using a uniform management mechanism.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a management method for network management system interface content version includes:
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.
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 comprises: 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.
Wherein, the managed unit is an Element Management System (EMS) or an element (NE); the management unit is a Network Management System (NMS) or EMS.
A management device for content versions of network management system interfaces, the device comprising: 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, receiving the interface interaction information sent by the version information processing module and analyzing and comparing the interface content version information analyzed from the interface interaction information.
The version information processing module is further used for feeding 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.
Wherein the managed unit is EMS or NE; the management unit is NMS or EMS.
The invention establishes an interface content version information base in a managed unit, and maintains the interface content version information in the interface content version information base when the managed unit is initialized or changed; the managed unit adds the interface content version information into 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. The invention can uniformly maintain the interface content version information of the managed unit and can lead the management unit to flexibly use the interface content version information of the managed unit.
Drawings
FIG. 1a is a schematic diagram of a version management flow of an existing interface function IRP;
FIG. 1b is a flow chart illustrating the interface content version management method of the present invention;
FIG. 1c is a schematic diagram of the structure of the interface content version management device according to the present invention;
FIG. 2 is a schematic diagram of an example of interface content version maintenance of the present invention;
FIG. 3 is a flow chart illustrating an example of querying the interface content version one via the interface according to the present invention;
FIG. 4 is a flowchart illustrating an example of adding interface content version to interface interaction content according to the present invention.
Detailed Description
The basic idea of the invention is: establishing an interface content version information base in a managed unit, and maintaining interface content version information in the interface content version information base when the managed unit is initialized or changed; the managed unit adds the interface content version information into 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.
The invention is further described with reference to the following examples with reference to the accompanying drawings.
A management method for network management system interface content version mainly comprises the following contents:
firstly, an interface content version information base is established in a managed unit, and when the managed unit is initialized or changed, the interface content version information in the interface content version information base is actively maintained.
Here, the interface content version information in the interface content version information base can also be maintained through a version information maintenance module which is established for maintaining the interface content version information. The version information maintenance module is positioned at the managed unit side.
And secondly, adding interface content version information into the interface interaction message by the managed unit.
Here, the interface contents version information includes, but is 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.
Thirdly, the management unit may query the managed unit for the interface content version information through a query interface (e.g., three specific query interfaces in embodiment 1 below), and perform analysis and comparison with the interface content version information parsed from the interface interaction message.
Here, the managed element may be an Element Management System (EMS) or an NE (network element); the management unit may be a Network Management System (NMS) or an EMS.
A management device for network management system interface content version mainly comprises the following contents:
and 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.
And 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.
And 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, receiving the interface interaction information sent by the version information processing module and analyzing and comparing the interface content version information analyzed from the interface interaction information.
In summary, by adopting the invention, the interface content version information of the managed unit can be maintained uniformly. Furthermore, because the interface content version information may exist in a subclass manner, that is, different objects correspond to different interface content version information, at this time, when the interface content version information exists in a subclass manner, the interface content version information may be referred to as interface content object version information, and respectively correspond to different objects, and are located in different interface content object instances. Therefore, the invention can also uniformly maintain the version information and the attribute of the interface content object in the network; inquiring interface content version information and detail information thereof; and obtaining corresponding interface content version information from the interface content object instance.
The invention is illustrated below.
Example 1: as shown in fig. 1b, the present embodiment comprises the following steps:
step 101, the management unit queries the managed unit and obtains the interface content version number.
Step 102, according to the interface content version number, the management unit inquires and obtains the interface content version information from the managed unit.
Step 103, the management unit receives the interface interaction message containing the interface content version information from the managed unit, and analyzes and compares the interface interaction message with the interface content version information obtained by inquiry.
Specifically, the management unit interacts with the managed unit mainly through the following three types of interfaces:
firstly, the method comprises the following steps: the management unit obtains the interface content version number through a first type query interface (version number query interface). The query may take the following form:
mode 1, using the version number of the function IRP as an input parameter, querying the content version associated with the function IRP version, or defining getContentVersion in the base class of the IRP, and all the interface function IRPs implement the mode.
And 2, by using the content version type as an input parameter, inquiring all content versions supported by the managed unit under the type.
And in the mode 3, the input parameter is null, and all content versions supported by the managed unit are inquired and acquired.
And 4, inquiring which content versions the content version object is supported by according to the content version object.
Secondly, the management unit acquires the detailed content of the interface content version information through a second type of query interface (version detail query interface), namely the detailed information of the interface content version information. The query may take the following form:
and in the mode 1, all detailed information of the content version information corresponding to the version number is inquired according to the interface content version number.
And thirdly, the managed unit feeds back interface feedback content containing the content version information to the managed unit through a third type interface (also called a content version information feedback interface).
Here, the interface feedback content may be as follows:
1) the managed unit sends a notification message to the management unit;
2) the managed unit synchronously returns an operation response to the management unit;
3) a file generated by the managed element.
Example 2: as shown in FIG. 1c, an embodiment of the present invention comprises: the system comprises a version information maintenance module, a version information processing module and a version information query and analysis module. The version information maintenance module is positioned at the managed unit side and is responsible for maintaining the interface content version information and providing query; the version information processing module is located at the managed unit side and is responsible for adding the interface content version information into the interface feedback content (specifically, interface interaction messages). The version information query and analysis module is positioned at the management unit side and is 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 by query.
Example 3: as shown in fig. 2, which is a schematic diagram of an example of the interface content version maintenance of the present invention, the content version information may be maintained in the following manner:
the version information maintenance module contains an interface content version information base, each interface content version object registers (register) self detailed information with the interface content version information base during initialization, and when the version is no longer used in the managed unit due to upgrade or other reasons, the interface content version object logs out (detach) self version number with the interface content version information base. After the registration and the logout actions are completed, the interface content version information base sends out a change message of the content version. The change message includes the content version number and the change operation.
The above-described registration and deregistration actions occur in the following situations:
situation one, a new interface content version object is added into a managed unit;
case two, the old interface content version object exits the managed element;
and thirdly, upgrading the interface content version, and simultaneously adding and quitting the version.
Example 4: the interface content version information model may employ field definitions as in table 1 below (ContentVersion IOC).
TABLE 1
Example 5: fig. 3 is a schematic flow chart illustrating an example of querying an interface content version through an interface according to the present invention, where the embodiment includes the following steps:
step 201, firstly, the management unit sends a request to the managed unit through an existing standard interface, such as a getirpverson interface of a functional IRP or a getIRPOutline interface of an EPIRP.
Step 202, obtaining the version number of the current managed element function IRP from the request response.
Step 203, inquiring the associated content version number through the function IRP version number, wherein the associated relationship is embodied in the IRP information of the interface to which the content version information belongs.
Step 204, obtaining the queried content version number from the request response.
And step 205, querying the detail information of the content version through the acquired content version number.
Step 206, obtaining the detail information of the content version of the query from the request response.
Example 6: fig. 4 is a schematic flow chart illustrating an example of adding an interface content version to interface interactive content according to the present invention, where for a specific interface content object example, a content version identifier needs to be added to clearly indicate a content version to which the example belongs, where the content version identifier is needed to correspond to content version management needs, and reference is made to several specific examples:
example one: as for the message, specifically for the alarm message and the alarm object, the original field domain _ name already contains the version number of the interface IRP, so the version number of the content object is further expanded and added on this field. The alarm information object alarmninformation (3GPP 32.3115.3.1.2) has a new content version attribute added.
Example two: regarding the object, specifically for the configuration object, the resource model version number attribute is uniformly added in the top IOC: top (3GPP 32.6226.1.3.8.2). For the configuration file, the file version fileFormatVersion field in the file header is extended to add the content version information. For the configuration message, the content version information is extended in the domain _ name as in the alert message.
Example three: for a file, specifically for a performance data file, version information is extended and added on a fileFormatVersion field in a file header. For the performance message, content version information is extended in the domain _ name as in the alarm message. A content version attribute is added to the performance measurement type object MeasuredAttribute (3GPP 32.4126.3.5).
In summary, there are three main ways to add content version information to the interface feedback content (specifically, the interface interaction message):
the method comprises the steps that firstly, content version information content is added to a file version field of an interface generation file;
in the second mode, the content version information content is added in the message domain field of the interface message;
and thirdly, adding a content version information field in the interface interaction object attribute.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.