WO2008052389A1

WO2008052389A1 - A method and system for realizing universal interfaces in the network management system

Info

Publication number: WO2008052389A1
Application number: PCT/CN2006/002935
Authority: WO
Inventors: Qingfei Nian
Original assignee: Zte Corporation
Priority date: 2006-11-02
Filing date: 2006-11-02
Publication date: 2008-05-08
Also published as: CN101529807B; CN101529807A

Abstract

A network management system for interacting data in the telecommunication management network (TMN) or the like networks and the method for realizing universal interfaces thereof are disclosed. The present invention includes define of the universal architecture for the data massages, configuration of the specific data massage information and configuration of the function interface module of the system. By transforming the data massages to universal architecture, the present invention could accomplish analyze of the data message and realize good compatibility, and therefore overcome the disadvantage of lacking university, not easy to expand and the disadvantage that the coupling between the interfaces and the application is too compact in the current interfaces processing technology, enhance the interfaces expand ability of the network management system, and save the cost of developing and maintenance of the network management.

Description

Universal interface implementation method and system thereof for network management system

The present invention relates to an interface of a network management system, and more particularly to an interface implementation method and system for a network management system in the field of telecommunications. Background technique

With the development of telecommunication networks, telecom network management systems are increasingly valued by telecom operators and equipment manufacturers. Telecom operators and equipment manufacturers monitor and manage telecommunication equipment through centralized telecommunication network management.

In the Telecommunications Management Network (TMN) specification, the telecommunications network management is divided into a workstation management function (MF), an operating system function (OSF), a network element function (NEF), and a Q interface adaptation function (QAF), each of which functions. It is composed of a plurality of sub-function modules, which are connected between the workstation function (WFS) and the operating system function (OSF) defined by the Telecommunication Management Network (TMN), between different telecommunication management networks or non-telecom management. The interface (X) between the network and the operating system function (OSF), the interface between the operating system function (OSF) and the network element function (NEF) (Q3) or the operating system function (OSF) and the Q interface adaptation function ( The interface (Qx) between QAFs interacts. Each sub-function module must define and organize the interface in order to interact with other functions.

In the existing network management system, the implementation of the interface between systems or within the system is pre-defined or agreed within the application. The parameter types and parameters of the interface are fixed. When the interface changes, the interface needs to be recompiled (internal convention) The way it is not needed) and the upgrade of the application, this change may introduce new problems and increase the complexity of system maintenance. At present, there are also some interface extension methods, such as the method of using a derived interface or an object. The implementation principle is to replace the original interface with a new derived interface. Since the derived interface inherits the original interface, the old and new interfaces can directly communicate with each other, but this method The starting point is to expand on the existing specific interface, without the loose coupling of the interface and the application, and has certain dependence on the specific implementation technology, so it cannot be universally applied and fundamentally solved. Summary of the invention

The technical problem to be solved by the present invention is to provide a general interface implementation method and system for the network management system, which can enhance the interface expansion capability of the network management system, and can save development and maintenance costs of the network management system.

To achieve the above objective, the present invention provides a method for implementing a common interface of a network management system, including the following steps:

(a) The packet transmitted by the interface operation is defined as a general operation interface structure, and the operation information to be filled in the structure includes an operation identifier and an operation parameter, and the operation parameter is embodied in the form of a list, including a parameter name and a parameter value item. Parameter values can be of any data type;

At the same time, the operation information is configured and saved in the system, and the operation identifier used by the operation interface and the parameter name of the operation parameter are defined in the operation information;

(b) The sending side function interface fills in the operation information according to the defined common operation interface structure, and generates a message to be sent to the receiving side function interface;

(C) After receiving the message, the receiving side function interface determines whether the function module is the processing module of the operation, and if yes, performs step (d), otherwise sends to the function interface of the function module that processes the operation, and then performs the step (d);

(d) The function interface that receives the packet parses the packet, and determines whether the operation identifier and the name of some or all of the operation parameters have matching items in the configured operation information. If yes, execute the next step, otherwise , returning an error message to the sending side function interface, and ending;

(e) The function interface parses the parameter value of the parameter that matches the success, and performs subsequent processing.

Further, the foregoing interface implementation method may further have the following features:

The function function of the transmitting side in the step (b) is to send a message to another function interface inside the system, or to a function interface sent to another system.

The operation parameter list of the general operation interface structure defined in the step (a) further includes a parameter The number type item; the parameter type of the operation parameter is defined in the operation information configured in the system; in the step (d), the function interface determines whether the operation parameter has a matching item in the configured operation information, and is also filled in. Whether the parameter type of the operation parameter is consistent with the configured parameter type. If the parameter name and the parameter type are the same, the two match. Otherwise, they do not match.

In the general operation interface structure defined in the step (a), the defined operation parameter list includes an entry parameter list, an exit parameter list, and a return value parameter list; the operation information configured in the system is also divided into an entry parameter, an exit parameter, and Return value parameters, and define the parameter names and parameter types of each operation parameter included in the three types of parameters.

In the step (a), the operation processing information is further configured in the system, including the module name and the operation identifier, and each module may correspond to multiple operations;

In the step (c), the receiving side function interface finds the corresponding processing module according to the operation identifier parsed from the message to the configured operation processing information, and then sends the message or performs local processing.

The operation operation information is further included in the general operation interface structure defined in the step (a); accordingly, the operation version information is also defined in the operation information configured in the system;

After the function interface of the step (d) parses the operation version information from the message, it also finds whether there is a matching item in the configured operation version information, and if yes, performs step (e), otherwise, an error message is returned. End.

The step (a) further configures version compatibility information in the system, and defines a compatibility relationship between the versions;

The step (d) is considered to match if the operation version in the message is the same as or compatible with the configured operation version. Further, the foregoing interface implementation method may further have the following features:

The step (a) further configures type information in the system, and defines a custom parameter type name supported by the interface language and a corresponding system internal type or internal structure;

The step (e) function interface analyzes the custom parameter according to the type information of the configuration.

The operation parameter defined by the general operation interface structure defined in the step (a) further includes the type version information; at the same time, the type version information corresponding to the custom parameter type is also defined in the type information also configured in the system;

The function interface of the step (d) parses the type version information of the operation parameter from the message, and finds whether the version information of the operation parameter is the same or compatible in the configured type information. If yes, the operation parameter is considered to be Matches the item, otherwise, the action parameter is considered to have no matching item.

The system has a functional interface with one or more functional modules responsible for processing, and a functional interface of a functional module responsible for distributing operations, and the function of distributing the first to the receiving system when the system issues an operation between the systems. The functional interface of the module, which then determines the processing module of the operation for distribution.

The network management system with a universal operation interface provided by the present invention includes a storage module and a plurality of functional modules, wherein the functional modules have functional interfaces that can communicate with each other, and the storage module stores the configured operation information. The operation identifier used in the operation interface and the parameter name and parameter type of the operation parameter are defined in the operation information;

The message transmitted by the function interface is defined as a general operation interface structure, and the operation information to be filled in the structure includes an operation identifier and an operation parameter, and the parameter is represented in the form of a list, including a parameter name, a parameter type, and a parameter value. Item, the parameter value can adopt any data type; the sending unit is configured to fill in the operation according to the general operation interface structure when transmitting Information, the generated message is sent to the function interface on the receiving side;

The receiving unit, the processing module for determining the operation, distributing or forwarding the operations processed by the other function modules, parsing the message processed by the function module, determining the operation identifier and the name and type of the at least one operation parameter are configured Whether there is a matching item in the operation information, and if yes, parsing the parameter value of the parameter that matches the success, otherwise returning the error message.

Further, the above network management system can also have the following features:

The storage module further stores operation processing information, including a module name and an operation identifier, and each module may correspond to multiple operations;

The receiving unit of the function interface finds a corresponding processing module according to the operation identifier parsed from the message to the operation processing information, and then processes the ^=艮 text locally, or distributes or forwards the message to the corresponding Processing module.

In the general operation interface structure defined by the function interface, the operation parameter adopts a structure of an entry parameter list, an exit parameter list, and a return value parameter list, and at least three fields of a parameter name, a parameter type, and a parameter value are defined in each list;

The operation information saved by the storage module is also divided into an entry parameter, an exit parameter, and a return value parameter, and respectively defines a parameter name and a parameter type of each operation parameter included in the three types of parameters.

The operation version information is also saved in the storage module;

The operation interface information is also included in the general operation interface structure defined by the function interface, and the receiving unit of the function interface further parses out the operation version information from the message, and finds whether there is a matching item in the configured operation version information. If so, continue to parse other information, otherwise an error message is returned.

Version compatibility information is also saved in the storage module, and compatibility between versions is defined. Department

If the receiving unit of the function interface determines that the operation version in the message is the same as or compatible with the configured operation version, it is considered that the two match.

The storage module further stores type information, where the name of the custom parameter type supported by the interface language and the corresponding internal type or internal structure of the system are defined;

The receiving unit of the function interface parses the custom parameter in the packet according to the type information of the configuration.

With the method of the present invention, compared with the prior art, the advantages are:

1) making the existing interface processing more versatile, and the interfaces implemented by different technologies can adopt the method provided by the present invention;

2) The interface is flexible. You can add, modify, or delete interfaces through configuration files. You can increase or decrease the number of parameters on the interface and change the type of parameters through the configuration file.

3) The interface processing is more flexible. The module that processes the interface can be configured to make the application and the interface loosely coupled, which facilitates the upgrade and debugging of the network management system. Drawing fan

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a schematic view showing the implementation of the method of the first embodiment of the present invention.

2 is a schematic view showing the implementation of the method of the second embodiment of the present invention. Preferred embodiment of the invention

The implementation method of the present invention will be further described below with reference to the accompanying drawings and specific embodiments. The implementation of the interface between the internal modules and the interface between the external modules implements two embodiments. The telecommunication management network (TMN) specifies the workstation function (WFS). The interface between the foreground and operating system functions (OSF), the interface (F), the different telecommunication management networks, or the interface (X) between the non-telecom management network and the operating system function (OSF) can be used. First embodiment

FIG. 1 is a schematic diagram of an implementation of an interface between internal modules of a background system in this embodiment, and related functional modules are also shown. As shown in the figure, the system includes a plurality of background function modules and a storage module. For the background function module, only the operation interface portion, that is, the background function interface 1 to the background function interface n are shown. The background system described above may be a back-end system of the telecommunications network management, but is not limited thereto.

The background function interface 1 is mainly used for the distribution of operation data, and other background function interfaces can also realize the operation data forwarding between internal modules. The storage module stores the necessary configuration information, including type information, operation information, operation processing information, and version compatibility information. The back-end function module can read the required configuration information from the storage module to complete the analysis of the data. In this embodiment, the background function module may also be replaced with a foreground function module, which is applicable to the internal function modules. The method of this embodiment first defines a general interface operation structure to transmit messages and required configuration information, including the following contents:

The message transmitted by the function interface is defined as a general operation interface structure according to the specific interface language used, so that it can transmit various operation information. The message between the internal module and the external module is the message with the above-mentioned general operation interface structure, but the same or different interface definition language can be used. For example, the ASN.1 definition can be used between the internal modules, and the external module can use the IDL. The interface definition language can also be in the same language.

The operation interface structure definition in this embodiment includes an operation name, an operation version, an entry parameter list, an exit parameter list, and a return value parameter list; each list has the same format, and includes a parameter name, a parameter type, a type version, and a parameter. The value is 4 fields, and the parameter value field can be represented by any type.

The configuration information includes operation processing information, operation information, version compatibility information, and type information, and can be saved in a file manner. among them:

The configured operational processing information is used to define the operations that the internal modules of the system can handle, including the module name and operation name. Each module can correspond to multiple operations. The configured operation information defines the operation name, operation version, and operation parameters used by the operation interface of the interaction information between the internal modules of the system. The operation parameters are divided into an entry parameter, an exit parameter, and a return value parameter, and parameters of each parameter are defined. Name and parameter type.

The compatibility between the operational version and the type version is defined in the configured version compatibility information.

The configured type information defines the custom parameter type name supported by the interface language, the corresponding system internal type or internal structure, and the type version. The function interface can further parse the custom parameters according to this configuration. This definition is mainly to avoid parsing errors caused by changes in internal types or internal structure definitions. There is no version incompatibility or type change problem for the types provided by the interface language itself, so no definition is needed.

The operation name is used as an operation identifier. In the present invention, the operation identifier can also be replaced with a command code or other flag.

The functional interface can be further divided into:

a sending unit, configured to fill in the operation information according to the general operation interface and the structure, and generate a function interface that is sent to the receiving side;

The receiving unit is configured to find a corresponding processing module according to the operation identifier parsed from the message to the configured operation processing information, and then process the packet locally, or distribute or forward the message to the corresponding processing module. For the operation processed by this function module, parse the message and determine whether the operation identifier, the operation version (optional), and at least one operation parameter have matching items in the configured operation information (the operation version matching refers to the same or compatible, operation) Parameter matching means that the parameter name and parameter type are the same, the type version is the same or compatible. If yes, the parameter value of the matching operation parameter is parsed. Otherwise, the error information is returned to the sending side. In addition, the type information can be reported according to the configuration. The custom parameters in the text are parsed.

The flow of the operation of the background function interface 1 to the background function interface n is taken as an example, that is, the background function interface 1 is the operation sending side, and the background function interface n is the operation receiving side, to explain the interface dynamic analysis and scheduling in the specific operation process. And processing methods, but other background functions are connected The following process can also be implemented between the ports, and the process includes the following steps:

Step 101: The background function interface 1 fills in operation information according to the defined common operation interface structure, including an operation name and an operation version, and an entry parameter list, an exit parameter list, and a return value list, and each list includes a parameter name, a type, a version, and Value 4 items;

Step 102, the background function interface 1 finds the corresponding processing module as the background function interface _n according to the filled operation name to the configured operation processing information, and sends the data of the operation information to the background function interface n;

The transmission can be either a distribution or a forwarding.

Step 103: After obtaining the operation data, the background function interface n parses out the operation name and the operation version to find the operation information in the configuration, and if it matches the operation with the same operation name and the same version or compatibility, the next step is performed, otherwise the transmission is performed. The side returns the corresponding error message and ends;

According to the configured version compatibility information, it can be determined whether the currently used operation version is compatible with the operation version in the operation information. The same is true for the judgment of the type version below. If the operation name is different or the version is incompatible and forced to resolve, it may cause the system to crash.

Step 104: The background function interface II parses the entry parameter, the exit parameter, and the return parameter in the operation information, and performs matching on each parameter obtained according to the configured operation information and type information to determine whether the match name is the same and the type version is the same. Or compatible parameters, if any, go to the next step, otherwise, return the corresponding error message to the sending side, and end;

Note that if there are parameters with different names and different version versions or incompatible parameters, the receiver can only parse the matched parameters and not process the other parameters. It is also possible to require all matches to proceed down, otherwise an error message is returned.

Step 105: The background function interface n parses the parameter values with the same name and the same version or compatibility, and performs subsequent processing.

In the above process, on the transmitting side, the parameter name, the parameter type, the type version, the parameter value, and the like are filled in the packet (such as an ASN packet) according to the general operation interface structure defined by the operator. On the receiving side, the application layer analyzes the configuration information locally by the receiver. The message does not parse the incompatible or unrecognized message and returns the corresponding error message. The packet structure of this processing method is flat, the interface changes do not need to be recompiled, the number of parameters can be increased or decreased, and the parameter type is variable. Since the parsing of the entire packet is controlled by the application layer, it does not occur due to The problem of system crash caused by different definitions of the message structure.

It should be noted that the above embodiment is merely an example, and the present invention is not limited to some specific configurations and definitions.

For example, if the parameter types are all types defined by the system, you can also configure the above type information without using the configured operation information to determine whether the operation parameters can be resolved.

For another example, the operation processing information does not have to be written in a file, and in another embodiment, it can be directly written in the program, and the program judges the branch judgment to determine the distributed module, which is also feasible.

For another example, the operation version information may also be configured in the operation processing information, so that the distributed function interface first determines whether the operation version in the operation is the same as or compatible with the current configuration. If yes, redistribute, otherwise, the operation error message can be directly returned.

As another example, for some system languages, the return value parameter is incorporated into the exit parameter, in which case the return value parameter can be omitted. However, some of the entry parameters and the exit parameters are combined into one class. For the present invention, it is not important to classify the operation parameters, as long as the operation parameter names and types used by the operation interface are defined, and correspondingly, in the general operation interface. The structure also does not limit the number and type of parameter lists defined.

In addition, for some systems, the above operation version and type version information may not be set. In this case, only operations and parameters having the same name and the same version may be parsed, and 'the basic function of the present invention may be implemented. For systems that do not consider upgrading the parameter type, the parameter type may not be added to the list of operating parameters.

Second embodiment

2 is an interface implementation of an external interface between a foreground system and a background system in this embodiment. A schematic diagram of the implementation of the method. The structure of the foreground system and the configured information are the same as those of the first embodiment. The back-end system and the foreground system have similar functional structures, including the front-end function interface 1 to the front-end function interface 1, and the front-end function interface is connected to the foreground device of the telecommunication network management system. , is responsible for information interaction with the background function interface, and has an external communication connection between the front function interface 1 and the background function interface 1.

In this embodiment, the operation sending side and the operation receiving side are the foreground function interface or the background function interface, and the dynamic analysis, scheduling, and processing methods of the foreground function interface are the same as the background function interface. The following takes the foreground function interface 1 to send the operation to the background as an example, and the specific implementation steps of the method in this embodiment are described with reference to FIG. 2:

First, the front-end function interface 1 fills in the operation information according to the defined common operation interface structure, including the operation name, the operation version, the entry parameter list, the exit parameter list, and the return value list, and then generates a message according to the filled information to the background function interface 1 The operation data is sent. The processing after the background function interface 1 receives the operation data is the same as the step 102 105 of the first embodiment, and belongs to the interface implementation between the internal modules, and is not repeated here.

In some cases, there is not necessarily a functional interface dedicated to distribution within the system. The background function interface 1 in Figure 2 may also be the functional interface of the functional module to handle the operation, and thus it is not necessary to distribute it. However, if it is not the function interface of the function module that handles the operation, it needs to be forwarded to the corresponding function interface according to the configured processing module.

In order to more intuitively understand the effects of the present invention, the advantages of the present invention will be described below by comparing the configuration in a conventional manner with the configuration of the present invention in a configuration example.

Traditional treatment method:

Assume that the original operation of creating a network element (NE) is defined as follows:

CreateNE-T: := SEQUENCE {

userLabel GraphicString, - user ID

deviceType GraphicString, - device type

ipAddress GraphicString, -IP address createTime GeneralizedTime—Generate time

NE-T:: = SEQUENCE {

Neld INTEGER, — network element identifier

userLabel GraphicString, user tag

deviceType GraphicString, --device type

ipAddress GraphicString, -IP address

createTime GeneralizedTime -- create time

}

among them:

Entry parameters: CreateNE-T

Export parameters: NE-T

Return parameters: Error-T

GraphicString, GraphicString ₅ GeneralizedTime and other types are ASN types. If you want to change the original structure during system upgrade, such as modifying CreateNE-T as follows:

CreateNE-T: " SEQUENCE {

—userLabel GraphicString, -This change may directly cause a system crash (reduced fields)

deviceType INTEGER, - This change will directly cause the system to crash (type change)

ipAddress GraphicString,

createTime GeneralizedTime ,

Coordination [0]GraphicString OPTIONAL - This change will cause some system crashes, related to the build environment (add fields) }

The above changes directly lead to compatibility issues, other modules will not be able to use the new message structure. Because the traditional method requires the structure to be fixed, the extension of the structure is strict, and its essence is the parsing process of the interface compiler control interface, which directly limits the extension of the interface. According to the method provided by the present invention, it is assumed that the ASN structure is used to define a common interface, and the ASN.1 compiled in the application is in the following form:

GeneralOperationlnterface-T: :=SEQUENCE {

operationName GraphicString, — operation name

Version GraphicString, --operation version

inputParam ParamList-T, - entry parameter list

outputParam ParamList-T, --export parameter list

returnParam ParamList-T - list of return values

}

operationName is the operation name, version is the version, inputParam, outputParam, and returnParam are the ingress parameter, the exit parameter, and the return value parameter, respectively. The entry parameters, exit parameters, and return value parameters are all populated in the following list format:

Param-T: -SEQUENCE {

Name GraphicString, — name

typeName GraphicString, — type

Version GraphicString, — version

Value ANY - parameter value

}

ParamList-T: := SEQUENCE OF Param-T

All operations used in the application are represented by GeneralOperationlnterface-T. That is to say, this structure is used to construct a general operation data transmission channel, and the content of each operation is defined in the file of the configuration information. The definitions in the operational information definition file are as follows:

Operation name: "Create E"

Operation version: "V2.01R2"

Entry parameters: Parameter name Parameter type

[0]"UserLabel", "GraphicString"

[l]"DeviceType", "INTETER",

[2] "Coordination", "GraphicString"

[3]"CreateTime" ₅ "GeneralizedTime

[4]'ΊΡ Address", "NetAddress"

Export parameters:

[0]"ΝΕ-Τ" "NE-T"

Return value parameter:

[0]"ErrorInfo" "Error-T"

"NE-T" and "Error-T" are structures defined internally by the system, and the function modules can be parsed.

Type information profile definition:

Name Type Version

NetAddress, GraphicString, V1.0

NE-T, Internal, VI.0

Error-T, Internal, VI.0

Note: GraphicString, GraphicString, GeneralizedTime, etc. are of type ASN and do not need to be defined in the type definition file. The definition of the operation processing information configuration file: Module name, operation name

NEMgr CreateNE

DeleteNE

ModifyNE

QueryNE

EMSMgr CreateEMS

DeleteEMS

ModifyEMS

QueryEMS

The above NE refers to the network element, and the EMS refers to the network management system, which is only an example. An example of the actual message content passed in the system:

Operation name "CreateNE

Operation version "V2.01R2"

Entry parameter

Parameter name Parameter type Type version Parameter value [0]"UserLabel", "GraphicString", " , Main communication station network element" [l]"DeviceType", "INTETER", "", 2

[2] "Coordination""GraphicString",","x=100 ₃ =300"[3]"CreateTime" ₅ "GeneralizedTime", "20061010120010'[4]'ΊΡAddress","NetAddress","VI.0",

"IP=10.30.1.1, Mast=255.0.0.0"

Export parameters:

[0]"NE-T", "NE-T", 'VI.0", NE-T Return Value Parameters:

[0]"ErrorInfo", "Error-T" 'VI.0", "Duplicate

IP Address" On the sender side, the parameter name, parameter type, type version, parameter value, etc. are filled in the ASN message enemlOperationInterface-T according to the general operation interface structure defined by the operator.

On the receiving side, according to the definition of the operation definition file defined by the receiver, the packet is parsed one by one, and the incompatible or unrecognized message is not parsed, and the corresponding error information is returned.

The message structure of this processing method is flat, the interface changes do not need to be recompiled, the number of parameters can be increased and decreased, and the parameter type is variable. Since the resolution of the whole ^=艮 text is controlled by the application, it does not appear. The problem of system crash due to the different definition of the structure of the ^ text.

It can be seen that the present invention provides a network management system for data interaction in a network such as a Telecommunication Management Network (TMN) and a method for implementing the common interface thereof, including a general structure definition of a data packet and a specific packet information configuration. And the configuration of the function interface module of the system, through the general conversion processing process of the message structure, completes the parsing of the message, and can achieve good compatibility, overcomes the lack of common, difficult to expand, interface and application of the existing interface processing technology The shortcoming of coupling is too tight, the interface expansion capability of the network management system is enhanced, and the development and maintenance costs of the network management system can be saved.

The above description is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. All should be covered by the scope of the present invention. Industrial applicability

- The general interface processing method and system proposed by the present invention have universality, strong expansion capability, and no dependence on specific technologies, and can well solve the problem of interface expansion. The method and system for implementing the universal interface according to the present invention, when the interface needs to be upgraded for some reason, only the configuration information definition (type information, operation information, operation processing information) needs to be modified, and the corresponding foreground or The background function interface module has very good maintainability and can effectively reduce development and maintenance costs.

Claims

Claim

1. A general interface implementation method for a network management system, comprising the following steps:

(c) After receiving the message, the receiving side function interface determines whether the function module is the processing module of the operation, and if yes, performs step (d), otherwise sends to the function interface of the function module that processes the operation, and then performs the step (d) ;.

2. The interface implementation method according to claim 1, wherein:

The transmitting side function interface in the step (b) is another function interface that sends a message to the internal system, or a function interface that is sent to another system.

3. The interface implementation method according to claim 1, wherein:

The operation parameter list of the general operation interface structure defined in the step (a) further includes a parameter type item; the parameter type of the operation parameter is defined in the operation information configured in the system; in the step (d), the function interface judges If there is a matching item in the configured operation information, it is also necessary to compare whether the parameter type of the operation parameter is the same as the configured parameter type. If the parameter name and the parameter type are the same, the two match, otherwise, match.

4. The interface implementation method according to claim 1, wherein:

a list of operational parameters defined in the general operation interface structure defined in step (a) Including the entry parameter list, the exit parameter list, and the return value parameter list; the operation information configured in the system is also divided into an entry parameter, an exit parameter, and a return value parameter, and respectively define parameters of each operation parameter included in the three types of parameters. Name and parameter type.

5. The interface implementation method according to claim 1, wherein:

In the step, the operation processing information is also configured in the system, including the module name and the operation identifier, and each module may correspond to multiple operations;

In the step (c), the receiving side function interface finds a corresponding processing module according to the operation identifier parsed from the message to the configured operation processing information, and then sends the message or performs local processing.

6. The interface implementation method according to claim 1, wherein:

After the function interface of the step (d) parses the operation version information from the message, it also finds whether there is a matching item in the configured operation version information, and if yes, performs step (e), otherwise, returns an error message. End.

7. The interface implementation method according to claim 6, wherein:

The step (d) is considered to match if the operation version in the message is the same as or compatible with the configured operation version.

8. The interface implementation method according to claim 1, wherein:

9. The interface implementation method according to claim 8, wherein:

The operational parameters defined by the general operation interface structure defined in the step (a) further include a class Type version information; at the same time, the type information of the custom parameter type is also defined in the type information also configured in the system;

After the function interface of the step (d) parses out the type version information of the operation parameter from the message, it also finds whether the version information of the operation parameter is the same or compatible in the configured type information, and if yes, the operation parameter is considered to have Matches the item, otherwise, the action parameter is considered to have no matching item.

10. The interface implementation method according to claim 1, wherein:

11. The interface implementation method according to claim 1, wherein:

The operation identifier is an operation name or a command code.

12. A network management system having a universal operation interface, comprising a storage module and a plurality of functional modules, wherein the functional modules have functional interfaces that can communicate with each other, and are characterized by:

The storage module stores the configured operation information, where the operation identifier used by the operation interface and the parameter name and parameter type of the operation parameter are defined in the operation information;

The message transmitted by the function interface is defined as a general operation interface structure, and the operation information to be filled in the structure includes an operation identifier and an operation parameter, and the operation parameter is embodied in the form of a list, including a parameter name, a parameter type, and a parameter value item. The parameter value may be any data type; the sending unit is configured to fill in the operation information according to the general operation interface structure when transmitting, and generate a function interface for sending the message to the receiving side;

13. The network management system of claim 12, wherein: The storage module further stores operation processing information, including a module name and an operation identifier, and each module may correspond to multiple operations;

The receiving unit of the function interface finds a corresponding processing module according to the operation identifier parsed from the message to the operation processing information, and then processes the message locally, or distributes or forwards the message to the corresponding processing. Module.

14. The network management system of claim 12, wherein:

15. The network management system of claim 12, wherein:

The operation version information is also saved in the storage module;

16. The network management system of claim 15 wherein:

Version compatibility information is also stored in the storage module, and a compatibility relationship between the versions is defined;

17. The network management system of claim 12, wherein: