CN101197723B

CN101197723B - Network management intermediate part

Info

Publication number: CN101197723B
Application number: CN2008100559852A
Authority: CN
Inventors: 鄢军; 苏静; 关君; 霍东风
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2008-01-03
Filing date: 2008-01-03
Publication date: 2010-08-18
Anticipated expiration: 2028-01-03
Also published as: CN101197723A

Abstract

The invention provides a network management middleware comprising a communication module, a protocol module, and an event processing module, which are connected in order. Both the communication module and the protocol module carry out communication through a general protocol and a general interface. As general features like the general protocol, the general interface, etc. capable of effectively screening differences of sublayer communication are applied during the setting process, the network management middleware with obvious normativeness and generality can be applicable to different operating systems, thereby effectively saving cost and maintenance charge. In addition, as the communication module, the protocol module and the event processing module, which are all related with network management, are integrated in a network management middleware, interactions between a user terminal and a network management server such as registration, setting/acquiring parameters, restarting, upgrading, diagnosis can be realized as long as using the interface provided by the network management middleware, thereby meeting the requirements of rapidly developing a network management agent.

Description

A kind of webmaster middleware

Technical field

The present invention relates to the webmaster field, be specifically related to a kind of webmaster middleware.

Background technology

When carrying out network service, need realize the function of OAMAgent usually for user terminal, to guarantee the proper communication between user terminal and the NM server.At present, in order to realize described network management function, need carry out protocol processes and communication process to the Content of Communication between user terminal and the NM server.At different user terminal operations platforms, the requirement and the process of carrying out protocol processes and communication process are all different, therefore need special communication entity to carry out protocol processes and communication process; And, the not enough standard of the process of protocol processes and communication process and general.

By the above as can be known, can realize that at present the communication entity of OAMAgent function does not have standardization and versatility, therefore can't be common to different user terminals.This causes realizing that the communication entity of OAMAgent function is more loaded down with trivial details when operation and maintenance, is unfavorable for the reduction of cost.

Summary of the invention

In view of this, main purpose of the present invention is to provide a kind of webmaster middleware, to improve the standardization and the versatility of the communication entity that can realize the OAMAgent function.

For achieving the above object, technical scheme of the present invention is achieved in that

A kind of webmaster middleware comprises the communication module, protocol module, the event processing module that link to each other successively; Described communication module and protocol module are all used puppy parc, general-purpose interface communicates;

Wherein, described communication module is used local socket interface and is realized intercommunication as general-purpose interface, and supports described protocol module and outside communication interaction; Described protocol module is used for the information that will receive and dispatch is comprised parsing in interior protocol processes, and uses the Tr069 agreement with communication module and carry out PERCOM peripheral communication as puppy parc, and supports the communication interaction between communication module and the event processing module; Described event processing module is used for inside is generated or handles from the incident of described protocol module, and the feedback processing result.

In the such scheme, this webmaster middleware further links to each other with user terminal, NM server.Wherein, this webmaster middleware is arranged at described subscriber terminal side or described NM server side.The mode that this webmaster middleware is arranged at subscriber terminal side is: described webmaster middleware closely links to each other with described user terminal or is arranged at described user terminal inside.

As seen, webmaster middleware provided by the present invention has been used generic features such as puppy parc, general-purpose interface in setting up procedure, the difference of the effective shielding of these generic features lower floor communication; Therefore, the webmaster middleware can be applied to different operating system, has tangible standardization and versatility, can effectively save cost and maintenance cost.And communication module that will be relevant with network management, protocol module, event processing module unification are combined in the webmaster middleware; Make as long as the interface that uses this webmaster middleware to provide, just can realize between user terminal and the NM server alternately, as: register, be provided with/get parms, restart, upgrading, diagnosis etc., thereby can satisfy the needs of quick exploitation OAMAgent.

Description of drawings

Fig. 1 is the network site schematic diagram of webmaster middleware of the present invention;

Fig. 2 is the structural representation of the webmaster middleware of one embodiment of the invention;

Fig. 3 is the setting and the event handling flow chart of the webmaster middleware of one embodiment of the invention.

Embodiment

Below in conjunction with accompanying drawing the technology of the present invention is described in detail.

Referring to Fig. 1, Fig. 1 is the network site schematic diagram of webmaster middleware of the present invention.Among Fig. 1, the webmaster middleware is connected between user terminal and the NM server; And the webmaster middleware is positioned at subscriber terminal side (closely link to each other with user terminal or be positioned at user terminal inside).In concrete the application, the webmaster middleware can carry out protocol processes and communication process, can also handle from outside or inner incident.

In order to make the webmaster middleware can operate as normal, need carry out as shown in Figure 2 setting to the webmaster middleware.Referring to Fig. 2, Fig. 2 is the structural representation of the webmaster middleware of one embodiment of the invention.Among Fig. 2, the webmaster middleware comprises communication module, protocol module, the event processing module that links to each other successively; Wherein, communication module links to each other with subscriber terminal side, NM server side.

When practical application, need to be provided with communication module, protocol module, event processing module in advance, mutual can carry out between each module that guarantees to finish setting, and finally finish event handling.

At communication module, need to carry out module initialization at intercommunication and PERCOM peripheral communication respectively.Wherein, at intercommunication: realize that with the mode of local socket intercommunication is (because most of operating platforms are all supported the socket interface, so therefore can be extensive use of the socket mode, and the difference between need not overanxious different operating platform.During specific implementation, need to set up good local UDP socket, and good local address and the port of binding, can define an interfaces special afterwards and be used for sending local message to other port, as: int SendMsg (int iSock, Int iPort, void*ptMsg); Parameter wherein is respectively: the socket of foundation, the receiving port of opposite end will send the pointer of data.

After finishing module initialization at intercommunication, just can use communication module to handle the intercommunication of webmaster middleware.

At PERCOM peripheral communication: needed information when needing to communicate by letter between initialization and the NM server.As: according to the regulation of Tr069 agreement, adopt the http agreement when communicating by letter, so want initialization http protocol stack with NM server.Needed information when certainly, also wanting to communicate by letter between initialization and the user terminal.

At protocol module, need default network management protocol, initialization Inform message (being used for), initialization Service-Port (being used to receive the request that NM server is initiatively initiated) to the NM server reporting message.

During default network management protocol, the file of depositing the MIB storehouse can be deposited in the protocol module, so as follow-up to the file in the MIB storehouse read, webmaster operation such as analysis.(form of stipulating in the parameter format in the Mib storehouse and the standard network management protocol is identical, and the MIB storehouse can be stored with the form of .xml) satisfies the present universal standard because MIB storehouse parameter organizational form, so has versatility.The interface shape that is used to read the MIB storehouse is: Int InitTr069 (char*pFile), input parameter wherein are the filenames that will read.

During initialization Inform message, can import the grand form of expression BOOT in the Inform message into, make Inform message when being sent out, can add the BOOT event flag with parameter.This be because: according to Tr069 agreement regulation, user terminal will send Inform message to NM server when starting, and carries the BOOT incident in this Inform message.The applied functional form of initialization Inform message can for: intInitInformMsg (int iEevent, void*ptPara).

During the initialization Service-Port, can be with the interface shape of Service-Port: intInitTr069Server (int iPort); The port of input parameter wherein for binding.The purpose of initialization Service-Port is to receive the active connection message from NM server.In actual applications, the webmaster middleware both can be positioned at subscriber terminal side, can be positioned at the NM server side again.

As seen, protocol module and communication module are based on that the Tr069 agreement communicates.

At event processing module, can provide the mode of interface with call back function out, to guarantee that call back function can be called automatically by protocol stack after finishing registration.When realizing, can define a structure type earlier, comprise an integer and a void pointer type in the structure type, they are respectively applied for expression parameter object ID and pairing call back function pointer, define the structure array of an overall situation afterwards in inside.With the above-mentioned basis that is defined as, event processing module just can call corresponding call back function according to the parameter object ID that obtains.

The interface shape that is provided is: int RegCallBackFun (int iObjID, void*), wherein, first parameter of function is by reading the ID of the resulting parameter object of .xml file, second parameter is for handling the concrete function of this parameter object, the just call back function of being registered.By described interface, just call back function can be registered in the event processing module.

After finishing above-mentioned the setting, event processing module just can be handled the incident of inner definition, as: intercommunication incident etc. between timer (when detecting timer event, triggering relevant timer event), process; Can also handle socket incident (when detecting the incident that comprises the socket socket, call relevant call back function and carry out event handling), send request to handle from the request of NM server or to NM server at the outside.

Need to prove: can call the webmaster middleware in the mode of a thread,, also can use the webmaster middleware, with the realization event processing procedure in the mode of single process with the realization event processing procedure.

After finishing above-mentioned the setting, when concrete the application, communication module can supported protocol module and outside communication interaction; Protocol module then protocol processes such as resolves to the information that will receive and dispatch, and supports the communication interaction between communication module and the event processing module; Event processing module can generate or handle from the incident of protocol module inside, and the feedback processing result.

By at the description of Fig. 2 as seen, the setting of webmaster middleware and event handling flow process can be represented with the form of Fig. 3.Referring to Fig. 3, Fig. 3 is the setting and the event handling flow chart of the webmaster middleware of one embodiment of the invention, and this flow process may further comprise the steps:

Step 301: carry out the initialization of Tr069 protocol stack, this initialization procedure comprises: default network management protocol, initialization Inform message, initialization Service-Port.

Step 302: the communication module initialization, this initialization procedure comprises: carry out initialization, carry out initialization at PERCOM peripheral communication at intercommunication.

Step 303: registered callbacks function.

Step 304: processing events.

Step 305: judge whether the mistake that takes place because of processing events, if having, process ends; Otherwise, return step 304.

By the above as seen, webmaster middleware provided by the present invention has been used generic features such as puppy parc, general-purpose interface in setting up procedure, the difference of the effective shielding of these generic features lower floor communication; Therefore, the webmaster middleware can be applied to different operating system, has tangible standardization and versatility, can effectively save cost and maintenance cost.And communication module that will be relevant with network management, protocol module, event processing module unification are combined in the webmaster middleware; Make as long as the interface that uses this webmaster middleware to provide, just can realize between user terminal and the NM server alternately, as: register, be provided with/get parms, restart, upgrading, diagnosis etc., thereby can satisfy the needs of quick exploitation OAMAgent.

Claims

1. a webmaster middleware is characterized in that, this webmaster middleware comprises communication module, protocol module, the event processing module that links to each other successively; Described communication module and protocol module are all used puppy parc, general-purpose interface communicates;

Wherein, described communication module is used local socket interface and is realized intercommunication as general-purpose interface, and supports described protocol module and outside communication interaction;

Described protocol module is used for the information that will receive and dispatch is comprised parsing in interior protocol processes, and uses the Tr069 agreement with communication module and carry out PERCOM peripheral communication as puppy parc, and supports the communication interaction between communication module and the event processing module;

Described event processing module is used for inside is generated or handles from the incident of described protocol module, and the feedback processing result.

2. webmaster middleware according to claim 1 is characterized in that, this webmaster middleware further links to each other with user terminal, NM server.

3. webmaster middleware according to claim 2 is characterized in that, this webmaster middleware is arranged at described subscriber terminal side or described NM server side.

4. webmaster middleware according to claim 3 is characterized in that, the mode that this webmaster middleware is arranged at subscriber terminal side is:

Described webmaster middleware closely links to each other with described user terminal or is arranged at described user terminal inside.