CN102843255B - Peer-to-peer based network management method and proxy selection server - Google Patents
Peer-to-peer based network management method and proxy selection server Download PDFInfo
- Publication number
- CN102843255B CN102843255B CN201110175545.2A CN201110175545A CN102843255B CN 102843255 B CN102843255 B CN 102843255B CN 201110175545 A CN201110175545 A CN 201110175545A CN 102843255 B CN102843255 B CN 102843255B
- Authority
- CN
- China
- Prior art keywords
- node
- oamagent
- server
- network manager
- ordinary
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0695—Management of faults, events, alarms or notifications the faulty arrangement being the maintenance, administration or management system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
Abstract
The invention discloses a peer-to-peer based network management method and a proxy selection server. The method comprises the following steps: when an ordinary node finds that a two-level network management server in a local area can not be directly accessed, sending a network management proxy node query message to the proxy selection server, enabling the proxy selection server to receive the message, returning a network management proxy node list to the ordinary node, using the ordinary node to select one network management proxy node from the list, and re-establishing the connection with the two-level network management server through the network management proxy node; or when the two-level network management server finds that the ordinary node in the local area can not be directly achieved, sending the network management proxy node query message to the proxy selection server, enabling the proxy selection server to receive the message, returning the network management proxy node list to the two-level network management server, using the two-level network management server to select one network management proxy node from the list, and re-establishing the connection with the ordinary node through the network management proxy node. According to the method disclosed by the invention, the network quality is improved.
Description
Technical field
The present invention relates to technical field of network management, be specifically related to the network management based on point-to-point (Peer to Peer) and agent selection server.
Background technology
At present, network management technology mainly contains three kinds: based on the legacy network administrative skill of Simple Network Management Protocol (SNMP, SimpleNetwork Management Protocol), the network management technology based on peer-to-peer network agreement and the mediaphone network management technology based on P2P.
Fig. 1 gives the existing mediaphone network management framework figure based on P2P, as shown in Figure 1, mediaphone network management system based on P2P mainly comprises: management function (MF, ManagementFunction) node and bookkeeping (MO, Management Operation) node, wherein:
MF node: the collection of management data and storage, forms a management peer-to-peer network with Peer.The data being responsible for collecting and storing comprise: configuration data, alarm data, performance data, tracking and testing data, MO node access information, administrator role (MR, Manager Role) binding relationship of node and MO node, MR node authority setting data namely, specify the specified right of the appointed function of managed element (NE, Network Element).
MO node: by a MF node access-in management peer-to-peer network.Keeper, by MO Node registers system, carries out bookkeeping in its administration authority.
MR: after logging in MO, carry out bookkeeping in its administration authority.
NE: comprise all network elements in mediaphone network, as controlled super node (SN-C, SuperNode-Core), index super node (SN-T, Super Node-Tracker), transit node (RN, Relay Node), gateway (GW, GateWay) etc.
Typical P2P network management relates to Four types: network operation class, node priority assignation class, node administration class, resource management class.
Network operation class comprises: the access of MO registration, NE registration, NE and MF is safeguarded.
Node priority assignation class: super keeper obtains NE list, arranges administrator role authority, searching and managing person's authority, common management administrator obtain NE list.
Node administration class: setting NE management role, NE report management data, searching and managing data.
Resource management class: setting Resource management tasks, the task process of resource active business, the task process of resource passive service, the migration of Resource management tasks in managed network.
For the mediaphone network management technology based on P2P, when great deal of nodes in network carries out fire compartment wall (FW, Fire Wall)/network address translation (NAT, Network Address Translation) process after or network quality is bad time, the unreachable phenomenon of network may be there is, reduce network quality; Meanwhile, the overload problem produced when user's access amount increases in the short time is not properly settled.
Summary of the invention
The invention provides the network management based on P2P and agent selection server, ordinary node, OAMAgent node, network manager service node, to improve network quality.
Technical scheme of the present invention is achieved in that
A kind of network management based on point-to-point P2P, the method is applied to and comprises: in the network management system of one-level NM server, secondary NM server, ordinary node, OAMAgent node, agent selection server, wherein, ordinary node, OAMAgent node in each secondary network manager service management this secondary webmaster region, agent selection server is superimposed upon on each secondary webmaster region, runs P2P agreement between the node in secondary webmaster region;
When ordinary node finds directly to access the secondary NM server of one's respective area, OAMAgent querying node message is sent to agent selection server, agent selection server receives this message, OAMAgent node listing is returned to this ordinary node, this ordinary node selects an OAMAgent node from this list, to be re-established be connected by this OAMAgent node with secondary NM server; Or,
When secondary NM server finds the ordinary node that cannot directly arrive in one's respective area, OAMAgent querying node message is sent to agent selection server, agent selection server receives this message, OAMAgent node listing is returned to this secondary NM server, this secondary NM server selects an OAMAgent node from this list, to be re-established be connected by this OAMAgent node with this ordinary node.
Described ordinary node re-establishes to be connected with secondary NM server by this OAMAgent node and comprises:
Ordinary node sends Agent Solicitation to this OAMAgent node, when receiving the proxy response message that this OAMAgent node returns, by the secondary NM server transmission connection request message of this OAMAgent node to one's respective area, when receiving the connection response message from secondary NM server that this OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
Described secondary NM server re-establishes to be connected with this ordinary node by this OAMAgent node and comprises:
Secondary NM server sends Agent Solicitation to this OAMAgent node, when receiving the proxy response message that this OAMAgent node returns, connection request message is sent to described ordinary node by this OAMAgent node, when receiving the connection response message from described ordinary node that this OAMAgent node forwards, determine to re-establish with described ordinary node to be connected.
Described method comprises further:
When agent selection server receives the exit message that ordinary node that the first OAMAgent node or the first OAMAgent node serve sends, select a new OAMAgent node, each ordinary node of serving to the first OAMAgent node sends this new OAMAgent nodal information, and each ordinary node is connected by this new OAMAgent node and secondary NM server.
Described each ordinary node is connected by this new OAMAgent node and secondary NM server and comprises:
Ordinary node sends Agent Solicitation to new OAMAgent node, when receiving the proxy response message that new OAMAgent node returns, connection request message is sent to secondary NM server by new OAMAgent node, when receiving the connection response message from secondary NM server that this new OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
Described method comprises further:
Ordinary node receives the denial of service message of NM server, sends network manager service node request message to agent selection server; Agent selection server receives this request message, select a node as network manager service node, network manager service solicitation message is sent to this network manager service node, when receiving the network manager service application response message that network manager service node returns, return this network manager service nodal information to this ordinary node; This ordinary node sends service request to this network manager service node.
This ordinary node described comprises further after this network manager service node sends service request:
This network manager service node receives this service request information, judges whether to give the process of secondary NM server, if so, this service request information is transmitted to the process of secondary NM server according to the urgency level of this service; Otherwise, in this service request information of processing locality.
Described method comprises further:
Agent selection server receives the exit message that ordinary node that the first network manager service node or the first network manager service node serve is sent, select a new network manager service node, each ordinary node of serving to the first network manager service node sends this new network manager service nodal information, and each ordinary node sends service request to this new network manager service node.
A kind of agent selection server, is positioned at each based on the secondary webmaster region of P2P, comprises:
OAMAgent sensor selection problem module: receive the OAMAgent querying node message that ordinary node is sent, OAMAgent node listing is returned to this ordinary node, so that this ordinary node selects an OAMAgent node to come to re-establish with the secondary NM server of one's respective area to be connected from this list, wherein, described OAMAgent querying node message is that ordinary node finds to send when directly cannot access secondary NM server; Or, receive the OAMAgent querying node message that secondary NM server is sent, OAMAgent node listing is returned to this secondary NM server, so that this secondary NM server selects an OAMAgent node to come to re-establish with the ordinary node in one's respective area to be connected from this list, wherein, described OAMAgent querying node message is that secondary NM server finds to send when directly cannot arrive ordinary node.
Described agent selection server comprises further:
OAMAgent node takes over processing module: receive the exit message that ordinary node that the first OAMAgent node or the first OAMAgent node serve is sent, select a new OAMAgent node, each ordinary node of serving to the first OAMAgent node sends this new OAMAgent nodal information, so that each ordinary node is connected by this new OAMAgent node and secondary NM server.
Described agent selection server comprises further:
Network manager service sensor selection problem module: receive the network manager service node request message that ordinary node is sent, select a node as network manager service node, network manager service solicitation message is sent to this network manager service node, when receiving the network manager service application response message that network manager service node returns, this network manager service nodal information is returned to ordinary node, so that this ordinary node sends service request to this network manager service node, wherein, described network manager service node request message is that described ordinary node sends service request information to NM server, send when being rejected service due to the overload of this NM server.
Described agent selection server comprises further:
Network manager service node takes over processing module: receive the exit message that ordinary node that the first network manager service node or the first network manager service node serve is sent, select a new network manager service node, each ordinary node of serving to the first network manager service node sends this new network manager service nodal information, so that each ordinary node sends service request to this new network manager service node.
A kind of ordinary node, is positioned at secondary webmaster region, comprises:
OAMAgent node application module: when finding that this node directly cannot access secondary NM server, OAMAgent querying node message is sent to agent selection server, when receiving the OAMAgent node listing that agent selection server returns, an OAMAgent node is selected from OAMAgent node listing, Agent Solicitation is sent to this OAMAgent node, when receiving the proxy response message that this OAMAgent node returns, by the secondary NM server transmission connection request message of this OAMAgent node to one's respective area, when receiving the connection response message from secondary NM server that this OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
Described ordinary node comprises further:
OAMAgent node takes over request module: when receiving the new OAMAgent nodal information that agent selection server is sent, Agent Solicitation is sent to new OAMAgent node, when receiving the proxy response message that new OAMAgent node returns, connection request message is sent to secondary NM server by new OAMAgent node, when receiving the connection response message from secondary NM server that new OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
Described OAMAgent node is taken over request module and is further used for, and when receiving the exit message that OAMAgent node is sent, returning exit response message to OAMAgent node.
Described OAMAgent node is taken over request module and is further used for, when sending information to OAMAgent node, but when not receiving the response message that OAMAgent node returns in default response time, send new OAMAgent node solicitation message to agent selection server.
Described ordinary node comprises further:
Network manager service node application module: when receiving the Service Reject message that secondary NM server returns, network manager service node request message is sent to agent selection server, the network manager service nodal information that Receiving Agent selects server to return, sends service request information to network manager service node.
Described ordinary node comprises further:
Network manager service node takes over request module: when receiving the new network manager service nodal information that agent selection server is sent, and sends Agent Solicitation to new network manager service node.
Described network manager service node is taken over request module and is further used for, and when receiving the exit message that network manager service node is sent, returning exit response message to network manager service node.
Described network manager service node is taken over request module and is further used for, when sending service request information to network manager service node, but when not receiving the service response message that network manager service node returns in default response time, send new network manager service node solicitation message to agent selection server.
A kind of OAMAgent node, is positioned at secondary webmaster region, comprises:
Proxy requests processing module: the Agent Solicitation that reception ordinary node or secondary NM server are sent, returns proxy response message;
Connection handling module: be transmitted to secondary NM server by from the connection request message of ordinary node or connection response message; Ordinary node is transmitted to by from the connection request message of secondary NM server or connection response message.
Described OAMAgent node comprises further:
Gracefulness exits module: when exitting network, and the ordinary node of serving to agent selection server and this node sends exit message.
A kind of network manager service node, is positioned at secondary webmaster region, comprises:
Network manager service application processing module: the network manager service solicitation message that Receiving Agent selects server to send, returns network manager service application response message;
Service processing module: receive the service request information that ordinary node is sent, judge whether to give the process of secondary NM server according to the urgency level of this service, if so, this service request information is transmitted to the process of secondary NM server; Otherwise, in this service request information of processing locality.
Described network manager service node comprises further:
Gracefulness exits module: when exitting network, and the ordinary node of serving to agent selection server and this node sends exit message.
Compared with prior art, in the present invention, time unreachable between node and NM server, re-establish connection by OAMAgent node, improve network quality;
In addition, in the embodiment of the present invention, when NM server overloads, fractional load can be shared on network manager service node.
Accompanying drawing explanation
Fig. 1 is the existing mediaphone network management framework figure based on P2P;
The network management framework schematic diagram based on P2P that Fig. 2 provides for the embodiment of the present invention;
The composition schematic diagram of the agent selection server that Fig. 3 provides for the embodiment of the present invention;
The composition schematic diagram of the ordinary node that Fig. 4 provides for the embodiment of the present invention;
The message flow chart of the node registering method that Fig. 5 provides for the embodiment of the present invention;
Fig. 6 for the embodiment of the present invention one provide not directly arrive between secondary NM server and ordinary node time, the message flow chart re-establishing the method for connection initiatively initiated by ordinary node;
Fig. 7 for the embodiment of the present invention two provide not directly arrive between secondary NM server and ordinary node time, the message flow chart of the method connected initiatively initiated by secondary NM server;
Fig. 8 for OAMAgent node graceful that the embodiment of the present invention one provides exit time, produce the message flow chart of the method for new OAMAgent node;
Fig. 9 for OAMAgent node ungraceful that the embodiment of the present invention two provides exit time, produce the message flow chart of the method for new OAMAgent node;
The message flow chart of NM server being carried out to the method for load balancing that Figure 10 provides for the embodiment of the present invention;
Figure 11 for network manager service node graceful that the embodiment of the present invention one provides exit time, produce the message flow chart of the method for new network manager service node;
Figure 12 for network manager service node ungraceful that the embodiment of the present invention two provides exit time, produce the message flow chart of the method for new network manager service node.
Embodiment
Below in conjunction with drawings and the specific embodiments, the present invention is further described in more detail.
The network management framework schematic diagram based on P2P that Fig. 2 provides for the embodiment of the present invention, as shown in Figure 2, it mainly comprises: one-level NM server, secondary NM server, ordinary node, agent selection server, OAMAgent node and network manager service node, wherein:
One-level NM server: manage all secondary NM servers.
Secondary NM server: manage all nodes in this secondary webmaster region, as: ordinary node, network agent node, network manager service node.
Here, the management area of each secondary NM server can be determined according to administrative scope, such as: each administrative region arranges a secondary NM server.
Ordinary node: register by completing with agent selection server interaction, the application of OAMAgent node, network manager service node application process; By directly completing service request procedure alternately with secondary NM server or by OAMAgent node and secondary NM server or direct and network manager service node.
Agent selection server: the OAMAgent querying node message sent according to ordinary node or secondary NM server, for ordinary node or secondary NM server provide OAMAgent node listing; When discovery OAMAgent node exits network, select a new OAMAgent node taken over, this new OAMAgent nodal information is supplied to each ordinary node of former OAMAgent node serve; According to the network manager service node request message that ordinary node is sent, select a network manager service node, and this network manager service nodal information is supplied to ordinary node; When discovery network manager service node exits network, select a new network manager service node taken over, this new network manager service nodal information is supplied to each ordinary node of former network manager service node serve.
OAMAgent node: help to connect between secondary NM server and ordinary node.
Network manager service node: when secondary NM server overloads, for the part ordinary node in secondary NM server region provides service.
It should be noted that, run P2P agreement between each node (comprising: ordinary node, OAMAgent node, network manager service node) in secondary webmaster region, between node and server (comprising: one-level NM server, secondary NM server, agent selection server), run SNMP between server between two.
Only give two secondary webmaster regions in Fig. 2, in actual applications, the number in secondary webmaster region can be arranged arbitrarily as required.
The composition schematic diagram of the agent selection server that Fig. 3 provides for the embodiment of the present invention, agent selection server is positioned at each based on the secondary webmaster region of P2P, as shown in Figure 3, it mainly comprises: location registration process module 31, OAMAgent sensor selection problem module 32, OAMAgent node are taken over processing module 33, network manager service sensor selection problem module 34 and network manager service node and taken over processing module 35, wherein:
Location registration process module 31: the login request message that the node that reception first time logs in is sent, records the role of this node: ordinary node or OAMAgent node.
OAMAgent sensor selection problem module 32: receive the OAMAgent querying node message that ordinary node is sent, according to the node role that location registration process module 31 records, OAMAgent node listing is returned to this ordinary node, so that this ordinary node selects an OAMAgent node to come to re-establish with the secondary NM server of one's respective area to be connected from this list, wherein, described OAMAgent querying node message is that ordinary node finds to send when directly cannot access secondary NM server; Receive the OAMAgent querying node message that secondary NM server is sent, according to the node role that location registration process module 31 records, OAMAgent node listing is returned to this secondary NM server, so that this secondary NM server selects an OAMAgent node to come to re-establish with the ordinary node in one's respective area to be connected from this list, wherein, described OAMAgent querying node message is that secondary NM server finds to send when directly cannot arrive ordinary node.
OAMAgent node takes over processing module 33: receive the exit message that ordinary node that the first OAMAgent node or the first OAMAgent node serve is sent, according to the node role that location registration process module 31 records, select a new OAMAgent node, each ordinary node of serving to the first OAMAgent node sends this new OAMAgent nodal information, so that each ordinary node is connected by this new OAMAgent node and secondary NM server.
Network manager service sensor selection problem module 34: receive the network manager service node request message that ordinary node is sent, according to the node role that location registration process module 31 records, select a network manager service node, network manager service solicitation message is sent to this network manager service node, when receiving the network manager service application response message that network manager service node returns, this network manager service nodal information is returned to ordinary node, so that this ordinary node sends service request to this network manager service node, wherein, described network manager service node request message is that described ordinary node sends service request information to NM server, send when being rejected service due to the overload of this NM server.
Network manager service node takes over processing module 35: receive the exit message that ordinary node that the first network manager service node or the first network manager service node serve is sent, according to the node role that location registration process module 31 records, select a new network manager service node, each ordinary node of serving to the first network manager service node sends this new network manager service nodal information, so that each ordinary node sends service request to this new network manager service node.
The composition schematic diagram of the ordinary node that Fig. 4 provides for the embodiment of the present invention, this ordinary node is positioned at secondary webmaster region, as shown in Figure 4, it mainly comprises: OAMAgent node application module 41, OAMAgent node are taken over request module 42, network manager service node application module 43 and network manager service node and taken over request module 44, wherein:
OAMAgent node application module 41: when finding that this node directly cannot access secondary NM server, OAMAgent querying node message is sent to agent selection server, when receiving the OAMAgent node listing that agent selection server returns, an OAMAgent node is selected from OAMAgent node listing, Agent Solicitation is sent to this OAMAgent node, when receiving the proxy response message that this OAMAgent node returns, by the secondary NM server transmission connection request message of this OAMAgent node to one's respective area, when receiving the connection response message from secondary NM server that this OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
OAMAgent node takes over request module 42: when receiving the new OAMAgent nodal information that agent selection server is sent, Agent Solicitation is sent to new OAMAgent node, when receiving the proxy response message that new OAMAgent node returns, connection request message is sent to secondary NM server by new OAMAgent node, when receiving the connection response message from secondary NM server that new OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
OAMAgent node is taken over request module 42 and is further used for, and when receiving the exit message that OAMAgent node is sent, returning exit response message to OAMAgent node.
OAMAgent node is taken over request module 42 and is further used for, when sending information to OAMAgent node, but when not receiving the response message that OAMAgent node returns in default response time, send new OAMAgent node solicitation message to agent selection server.
Network manager service node application module 43: when receiving the Service Reject message that secondary NM server returns, network manager service node request message is sent to agent selection server, the network manager service nodal information that Receiving Agent selects server to return, sends service request information to network manager service node.
Network manager service node takes over request module 44: when receiving the new network manager service nodal information that agent selection server is sent, and sends Agent Solicitation to new network manager service node.
Network manager service node is taken over request module 44 and is further used for, and when receiving the exit message that network manager service node is sent, returning exit response message to network manager service node.
Network manager service node is taken over request module 44 and is further used for, when sending service request information to network manager service node, but when not receiving the service response message that network manager service node returns in default response time, send new network manager service node solicitation message to agent selection server.
Below provide the composition of the OAMAgent node that the embodiment of the present invention provides, OAMAgent node is positioned at secondary webmaster region, and it mainly comprises: proxy requests processing module and connection handling module, wherein:
Proxy requests processing module: the Agent Solicitation that reception ordinary node or secondary NM server are sent, returns proxy response message.
Connection handling module: be transmitted to secondary NM server by from the connection request message of ordinary node or connection response message; Ordinary node is transmitted to by from the connection request message of secondary NM server or connection response message.
OAMAgent node also can comprise: gracefulness exits module, and for when exitting network, the ordinary node of serving to agent selection server and this node sends exit message.
Below provide the composition of the network manager service node that the embodiment of the present invention provides, network manager service node is positioned at secondary webmaster region, and it mainly comprises: network manager service application processing module and service processing module, wherein:
Network manager service application processing module: the network manager service solicitation message that Receiving Agent selects server to send, returns network manager service application response message.
Service processing module: receive the service request information that ordinary node is sent, judge whether to give the process of secondary NM server according to the urgency level of this service, if so, this service request information is transmitted to the process of secondary NM server; Otherwise, in this service request information of processing locality.
Network manager service node also can comprise: gracefulness exits module, and for when exitting network, the ordinary node of serving to agent selection server and this node sends exit message.
When a new node enters network, first register flow path to be initiated to agent selection server.
The message flow chart of the node registering method that Fig. 5 provides for the embodiment of the present invention, as shown in Figure 5, its concrete steps are as follows:
Step 501: node logs in for the first time, send login request message to agent selection server, this message carries the role that node may be born, as: ordinary node, OAMAgent node or network manager service node.
Step 502: agent selection server receives this login request message, returns registration reply message to node, and record the corresponding relation of this node identification and node role.
Due to a variety of causes in network, can make not directly to arrive between secondary NM server and ordinary node, provide following solution for this situation.
When not directly arriving between secondary NM server and ordinary node, initiatively can be initiated to re-establish with secondary NM server the flow process be connected by ordinary node, also can by the flow process that secondary NM server is initiatively initiated and ordinary node connects.Embodiment is provided respectively below for both of these case:
Fig. 6 for the embodiment of the present invention one provide not directly arrive between secondary NM server and ordinary node time, the message flow chart re-establishing the method for connection initiatively initiated by ordinary node, as shown in Figure 6, its concrete steps are as follows:
Step 601 a: ordinary node finds self cannot directly access secondary NM server, then send OAMAgent querying node message, to obtain the OAMAgent node of this node to agent selection server.
Step 602: agent selection server receives this OAMAgent querying node message, and return OAMAgent querying node response message to this ordinary node, this message carries OAMAgent node listing.
Usually, the OAMAgent node being positioned at the same area with ordinary node can be returned to this ordinary node by agent selection server.
Step 603: ordinary node receives OAMAgent querying node response message, selects an OAMAgent node from OAMAgent node listing, sends Agent Solicitation to this OAMAgent node.
Step 604: OAMAgent node receives this Agent Solicitation, returns proxy response message to ordinary node.
Step 605: ordinary node Receiving Agent response message, sends connection request message by OAMAgent node to secondary NM server.
Step 606: secondary NM server receives this connection request message, connection response message is returned to OAMAgent node, OAMAgent node receives this connection response message, and this connection response message is transmitted to ordinary node, and ordinary node receives this connection response message.
So far, re-established by OAMAgent node between ordinary node with secondary NM server and be connected.
Fig. 7 for the embodiment of the present invention two provide not directly arrive between secondary NM server and ordinary node time, the message flow chart of the method connected initiatively initiated by secondary NM server, as shown in Figure 7, its concrete steps are as follows:
Step 701: secondary NM server finds that an ordinary node not directly arrives, sends OAMAgent querying node message to agent selection server.
Step 702: agent selection server receives OAMAgent querying node message, and return OAMAgent querying node response message to NM server, this message carries OAMAgent node listing.
Usually, the OAMAgent node being positioned at the same area with secondary NM server can be returned to this secondary NM server by agent selection server.
Step 703: secondary NM server receives this OAMAgent querying node response message, selects an OAMAgent node from OAMAgent node listing, sends Agent Solicitation to this OAMAgent node.
Step 704: OAMAgent node receives this Agent Solicitation, returns proxy response message to secondary NM server.
Step 705: secondary NM server Receiving Agent response message, sends connection request message by OAMAgent node to ordinary node.
Step 706: ordinary node receives this connection request message, returns connection response message by OAMAgent node to secondary NM server, and secondary NM server receives this connection response message.
So far, secondary NM server is connected with being re-established by OAMAgent node between ordinary node.
Containing the factors of instability in network, therefore may there is problem and exit network in OAMAgent node at any time, needs have new OAMAgent node to take over its work immediately, below provide concrete solution after OAMAgent node exits network.
Exiting of OAMAgent node is divided into two kinds of situations: graceful (graceful) exits and not graceful (ungraceful) exits, difference is: the former sends exit message to before exit NM server and other node, and the latter does not then carry out this action.Embodiment is provided respectively below for both of these case:
Fig. 8 for OAMAgent node graceful that the embodiment of the present invention one provides exit time, produce the message flow chart of the method for new OAMAgent node, as shown in Figure 8, its concrete steps are as follows:
Step 801: when OAMAgent node wants graceful to exit, sends exit message to agent selection server and the ordinary node of self serving.
Step 802: agent selection server receives this exit message, changes to the state of this OAMAgent node of self record and exits, and returns to this OAMAgent node and exit response message; Each ordinary node receives this exit message, returns exit response message to this OAMAgent node.
Step 803: what OAMAgent node received that agent selection server and each ordinary node return exits response message, exits network.
Step 804: agent selection server sends OAMAgent node to each ordinary node that this former OAMAgent node is served and takes over message, and this message is carried OAMAgent node and taken over indication information, carries new OAMAgent nodal information simultaneously.
Step 805: each ordinary node receives OAMAgent node and takes over message, records new OAMAgent nodal information, and return OAMAgent node to agent selection server and take over response message, send Agent Solicitation to new OAMAgent node simultaneously.
Step 806: new OAMAgent node receives the Agent Solicitation that arbitrary ordinary node is sent, and returns proxy response message to this node.
Step 807: ordinary node Receiving Agent response message, sends connection request message by new OAMAgent node to secondary NM server.
Step 808: secondary NM server receives connection request message, and return connection response message by new OAMAgent node to ordinary node, ordinary node receives this connection response message.
So far, OAMAgent node is taken over flow process and is completed.
Fig. 9 for OAMAgent node ungraceful that the embodiment of the present invention two provides exit time, produce the message flow chart of the method for new OAMAgent node, in the present embodiment, OAMAgent node ungraceful exits, any node is not notified when namely exiting, as shown in Figure 9, its concrete steps are as follows:
Step 901: ordinary node sends information to OAMAgent node, but in default response time, do not receive the response message that OAMAgent node returns, then determine that OAMAgent node occurs abnormal.
Step 902: ordinary node sends new OAMAgent node solicitation message to agent selection server.
Step 903: agent selection server receives new OAMAgent node solicitation message, returns new OAMAgent nodal information to ordinary node.
Step 904: ordinary node receives new OAMAgent nodal information, sends Agent Solicitation to new OAMAgent node.
Step 905: new OAMAgent node receives the Agent Solicitation that ordinary node is sent, and returns proxy response message to ordinary node.
Step 906: ordinary node Receiving Agent response message, sends connection request message by new OAMAgent node to secondary NM server.
Step 907: secondary NM server receives this connection request message, return connection response message by new OAMAgent node to ordinary node, ordinary node receives this connection response message.
So far, OAMAgent node is taken over flow process and is completed.
Because NM server will manage all nodes, therefore, when node is too much, the load of NM server can be too high, thus affect the performance of NM server.In order to solve this problem, provide following solution.
The message flow chart of NM server being carried out to the method for load balancing that Figure 10 provides for the embodiment of the present invention, as shown in Figure 10, its concrete steps are as follows:
Step 1001: NM server finds self to be in overload status, when after this receiving the service request information that ordinary node is sent, to ordinary node return service refuse information.
Step 1002: ordinary node receives this Service Reject message, sends network manager service node request message to agent selection server.
Step 1003: agent selection server receives this network manager service node request message, selects a node as network manager service node, sends network manager service solicitation message to this network manager service node.
Agent selection server selects network manager service node according to following condition usually:
One, online hours can ensure;
Two, all functions of NM server are possessed;
Three, there is public network IP address;
Four, disposal ability is stronger.
Step 1004: network manager service node receives network manager service solicitation message, returns network manager service application response message to agent selection server.
Step 1005: agent selection server receives network manager service application response message, and return network manager service node response message to ordinary node, this message carries this network manager service nodal information.
Step 1006: ordinary node receives network manager service node response message, sends service request information to network manager service node.
Step 1007: network manager service node receives this service request information, judges whether to give the process of secondary NM server according to the urgency level of this service, if so, performs step 1008; Otherwise, perform step 1009.
Step 1008: this service request information is transmitted to secondary NM server by network manager service node, secondary NM server is disposed, and to ordinary node return service device response message, this flow process terminates.
Step 1009: this service request information of network manager service node processing, is disposed, to ordinary node return service response message.
Destabilizing factor in network may cause network manager service node that abnormal exitting network occurs, and at this moment need a new network manager service node to take over its work, this has mainly been instructed by agent selection server.Exiting of same network manager service node is also divided into graceful and ungraceful two kinds of situations.Embodiment is provided respectively below for both of these case:
Figure 11 for network manager service node graceful that the embodiment of the present invention one provides exit time, produce the message flow chart of the method for new network manager service node, as shown in figure 11, its concrete steps are as follows:
Step 1101: when network manager service node wants graceful to exit, sends exit message to agent selection server and the ordinary node of self serving.
Step 1102: agent selection server receives this exit message, changes to the state of this network manager service node of self record and exits, and returns to this network manager service node and exit response message; Each ordinary node receives this exit message, returns exit response message to this network manager service node.
Step 1103: what network manager service node received that agent selection server and each ordinary node return exits response message, exits network.
Step 1104: agent selection server sends network manager service node to each ordinary node that this former network manager service node is served and takes over message, and this message is carried network manager service node and taken over indication information, carries new network manager service nodal information simultaneously.
Step 1105: each ordinary node receives network manager service node and takes over message, records new network manager service nodal information, and return network manager service node to agent selection server and take over response message, send service request information to new network manager service node simultaneously.
Step 1106: new network manager service node receives the service request information that arbitrary ordinary node is sent, and to this node return service response message, ordinary node receives this service response message.
So far, network manager service node is taken over flow process and is completed.
Figure 12 for network manager service node ungraceful that the embodiment of the present invention two provides exit time, produce the message flow chart of the method for new network manager service node, in the present embodiment, network manager service node ungraceful exits, any node is not notified when namely exiting, as shown in figure 12, its concrete steps are as follows:
Step 1201: ordinary node sends service request information to network manager service node, but in default response time, do not receive the service response message that network manager service node returns, then determine that network manager service node occurs abnormal.
Step 1202: ordinary node sends new network manager service node solicitation message to agent selection server.
Step 1203: agent selection server receives new network manager service node solicitation message, returns new network manager service nodal information to ordinary node.
Step 1204: ordinary node receives new network manager service nodal information, sends service request information to new network manager service node.
Step 1205: new network manager service node receives the service request information that ordinary node is sent, and to ordinary node return service response message, ordinary node receives this service response message.
So far, network manager service node is taken over flow process and is completed.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment made, equivalent replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (20)
1. the network management based on point-to-point P2P, it is characterized in that, the method is applied to and comprises: in the network management system of one-level NM server, secondary NM server, ordinary node, OAMAgent node, agent selection server, wherein, ordinary node, OAMAgent node in each secondary network manager service management this secondary webmaster region, agent selection server is superimposed upon on each secondary webmaster region, runs P2P agreement between the node in secondary webmaster region;
When ordinary node finds directly to access the secondary NM server of one's respective area, OAMAgent querying node message is sent to agent selection server, agent selection server receives this message, OAMAgent node listing is returned to this ordinary node, this ordinary node selects an OAMAgent node from this list, to be re-established be connected by this OAMAgent node with secondary NM server; Or,
When secondary NM server finds the ordinary node that cannot directly arrive in one's respective area, OAMAgent querying node message is sent to agent selection server, agent selection server receives this message, OAMAgent node listing is returned to this secondary NM server, this secondary NM server selects an OAMAgent node from this list, to be re-established be connected by this OAMAgent node with this ordinary node.
2. method according to claim 1, is characterized in that, described ordinary node re-establishes to be connected with secondary NM server by this OAMAgent node and comprises:
Ordinary node sends Agent Solicitation to this OAMAgent node, when receiving the proxy response message that this OAMAgent node returns, by the secondary NM server transmission connection request message of this OAMAgent node to one's respective area, when receiving the connection response message from secondary NM server that this OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
3. method according to claim 1, is characterized in that, described secondary NM server re-establishes to be connected with this ordinary node by this OAMAgent node and comprises:
Secondary NM server sends Agent Solicitation to this OAMAgent node, when receiving the proxy response message that this OAMAgent node returns, connection request message is sent to described ordinary node by this OAMAgent node, when receiving the connection response message from described ordinary node that this OAMAgent node forwards, determine to re-establish with described ordinary node to be connected.
4. method according to claim 1, is characterized in that, described method comprises further:
Agent selection server receives the exit message that ordinary node that the first OAMAgent node or the first OAMAgent node serve is sent, select a new OAMAgent node, each ordinary node of serving to the first OAMAgent node sends this new OAMAgent nodal information, and each ordinary node is connected by this new OAMAgent node and secondary NM server.
5. method according to claim 4, is characterized in that, described each ordinary node is connected by this new OAMAgent node and secondary NM server and comprises:
Ordinary node sends Agent Solicitation to new OAMAgent node, when receiving the proxy response message that new OAMAgent node returns, connection request message is sent to secondary NM server by new OAMAgent node, when receiving the connection response message from secondary NM server that this new OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
6. method according to claim 1, is characterized in that, described method comprises further:
Ordinary node receives the Service Reject message of secondary NM server, sends network manager service node request message to agent selection server; Agent selection server receives this request message, select a node as network manager service node, network manager service solicitation message is sent to this network manager service node, when receiving the network manager service application response message that network manager service node returns, return this network manager service nodal information to this ordinary node; This ordinary node sends service request to this network manager service node.
7. method according to claim 6, is characterized in that, this ordinary node described comprises further after this network manager service node sends service request:
This network manager service node receives this service request information, judges whether to give the process of secondary NM server, if so, this service request information is transmitted to the process of secondary NM server according to the urgency level of this service; Otherwise, in this service request information of processing locality.
8. the method according to claim 6 or 7, is characterized in that, described method comprises further:
Agent selection server receives the exit message that ordinary node that the first network manager service node or the first network manager service node serve is sent, select a new network manager service node, each ordinary node of serving to the first network manager service node sends this new network manager service nodal information, and each ordinary node sends service request to this new network manager service node.
9. an agent selection server, is characterized in that, is positioned at each based on the secondary webmaster region of P2P, comprises:
OAMAgent sensor selection problem module: receive the OAMAgent querying node message that ordinary node is sent, OAMAgent node listing is returned to this ordinary node, so that this ordinary node selects an OAMAgent node to come to re-establish with the secondary NM server of one's respective area to be connected from this list, wherein, described OAMAgent querying node message is that ordinary node finds to send when directly cannot access secondary NM server; Or, receive the OAMAgent querying node message that secondary NM server is sent, OAMAgent node listing is returned to this secondary NM server, so that this secondary NM server selects an OAMAgent node to come to re-establish with the ordinary node in one's respective area to be connected from this list, wherein, described OAMAgent querying node message is that secondary NM server finds to send when directly cannot arrive ordinary node.
10. agent selection server according to claim 9, is characterized in that, described agent selection server comprises further:
OAMAgent node takes over processing module: receive the exit message that ordinary node that the first OAMAgent node or the first OAMAgent node serve is sent, select a new OAMAgent node, each ordinary node of serving to the first OAMAgent node sends this new OAMAgent nodal information, so that each ordinary node is connected by this new OAMAgent node and secondary NM server.
11. agent selection servers according to claim 9, is characterized in that, described agent selection server comprises further:
Network manager service sensor selection problem module: receive the network manager service node request message that ordinary node is sent, select a node as network manager service node, network manager service solicitation message is sent to this network manager service node, when receiving the network manager service application response message that network manager service node returns, this network manager service nodal information is returned to ordinary node, so that this ordinary node sends service request to this network manager service node, wherein, described network manager service node request message is that described ordinary node sends service request information to secondary NM server, send when being rejected service due to the overload of this secondary NM server.
12. agent selection servers according to claim 11, is characterized in that, described agent selection server comprises further:
Network manager service node takes over processing module: receive the exit message that ordinary node that the first network manager service node or the first network manager service node serve is sent, select a new network manager service node, each ordinary node of serving to the first network manager service node sends this new network manager service nodal information, so that each ordinary node sends service request to this new network manager service node.
13. 1 kinds of ordinary nodes, is characterized in that, are positioned at secondary webmaster region, comprise:
OAMAgent node application module: when finding that this node directly cannot access secondary NM server, OAMAgent querying node message is sent to agent selection server, when receiving the OAMAgent node listing that agent selection server returns, an OAMAgent node is selected from OAMAgent node listing, Agent Solicitation is sent to this OAMAgent node, when receiving the proxy response message that this OAMAgent node returns, by the secondary NM server transmission connection request message of this OAMAgent node to one's respective area, when receiving the connection response message from secondary NM server that this OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
14. ordinary nodes according to claim 13, is characterized in that, described ordinary node comprises further:
OAMAgent node takes over request module: when receiving the new OAMAgent nodal information that agent selection server is sent, Agent Solicitation is sent to new OAMAgent node, when receiving the proxy response message that new OAMAgent node returns, connection request message is sent to secondary NM server by new OAMAgent node, when receiving the connection response message from secondary NM server that new OAMAgent node forwards, determine to re-establish with secondary NM server to be connected.
15. ordinary nodes according to claim 14, is characterized in that, described OAMAgent node is taken over request module and is further used for, and when receiving the exit message that OAMAgent node is sent, returning exit response message to OAMAgent node.
16. ordinary nodes according to claim 14, it is characterized in that, described OAMAgent node is taken over request module and is further used for, when sending information to OAMAgent node, but when not receiving the response message that OAMAgent node returns in default response time, send new OAMAgent node solicitation message to agent selection server.
17. ordinary nodes according to claim 13, is characterized in that, described ordinary node comprises further:
Network manager service node application module: when receiving the Service Reject message that secondary NM server returns, network manager service node request message is sent to agent selection server, the network manager service nodal information that Receiving Agent selects server to return, sends service request information to network manager service node.
18. ordinary nodes according to claim 17, is characterized in that, described ordinary node comprises further:
Network manager service node takes over request module: when receiving the new network manager service nodal information that agent selection server is sent, and sends service request information to new network manager service node.
19. ordinary nodes according to claim 18, is characterized in that, described network manager service node is taken over request module and is further used for, and when receiving the exit message that network manager service node is sent, returning exit response message to network manager service node.
20. ordinary nodes according to claim 18, it is characterized in that, described network manager service node is taken over request module and is further used for, when sending service request information to network manager service node, but when not receiving the service response message that network manager service node returns in default response time, send new network manager service node solicitation message to agent selection server.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110175545.2A CN102843255B (en) | 2011-06-24 | 2011-06-24 | Peer-to-peer based network management method and proxy selection server |
| PCT/CN2012/077085 WO2012175006A1 (en) | 2011-06-24 | 2012-06-18 | Network management method and proxy selection server based on peer to peer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110175545.2A CN102843255B (en) | 2011-06-24 | 2011-06-24 | Peer-to-peer based network management method and proxy selection server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102843255A CN102843255A (en) | 2012-12-26 |
| CN102843255B true CN102843255B (en) | 2015-03-11 |
Family
ID=47370332
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110175545.2A Active CN102843255B (en) | 2011-06-24 | 2011-06-24 | Peer-to-peer based network management method and proxy selection server |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102843255B (en) |
| WO (1) | WO2012175006A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104022951B (en) * | 2014-06-18 | 2018-03-23 | 中国人民解放军信息工程大学 | A kind of method for building up and system in network service path |
| CN112822242B (en) * | 2020-12-30 | 2023-03-24 | 杭州趣链科技有限公司 | Point-to-point network and node communication method and device thereof |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101022367A (en) * | 2007-03-27 | 2007-08-22 | 杭州华为三康技术有限公司 | Network management method and system |
| CN101989918A (en) * | 2009-08-04 | 2011-03-23 | 中兴通讯股份有限公司 | Peer-to-peer network management system and method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1878117B (en) * | 2006-07-18 | 2010-05-12 | 北京邮电大学 | Communication method of combining hierarchical structure peer-to-peer network and session initiation protocol |
| CN101989919A (en) * | 2009-08-06 | 2011-03-23 | 中兴通讯股份有限公司 | Local software diagnosing and maintaining system as well as corresponding method and system for diagnosis and maintenance |
-
2011
- 2011-06-24 CN CN201110175545.2A patent/CN102843255B/en active Active
-
2012
- 2012-06-18 WO PCT/CN2012/077085 patent/WO2012175006A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101022367A (en) * | 2007-03-27 | 2007-08-22 | 杭州华为三康技术有限公司 | Network management method and system |
| CN101989918A (en) * | 2009-08-04 | 2011-03-23 | 中兴通讯股份有限公司 | Peer-to-peer network management system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102843255A (en) | 2012-12-26 |
| WO2012175006A1 (en) | 2012-12-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2534790B1 (en) | Methods, systems, and computer readable media for source peer capacity-based diameter load sharing | |
| CN113596184B (en) | Hybrid cloud system, gatekeeper, network access method and storage medium | |
| CN105554065B (en) | Handle method, converting unit and the applying unit of message | |
| US8458298B2 (en) | Failover in an internet location coordinate enhanced domain name system | |
| EP2501083B1 (en) | Relay node, distributed network of relay node and networking method thereof | |
| CN104040964B (en) | Method, device and data center network across service area communication | |
| US20060184672A1 (en) | Communication channels in a storage network | |
| CN108650211A (en) | A kind of detection method and device of DNS abduction | |
| JP5508273B2 (en) | Network location service | |
| WO2021109726A1 (en) | Bandwidth limitation method, apparatus and system | |
| CN103188144B (en) | A kind of system and method for realizing distributed network gate intercommunication | |
| US20080205376A1 (en) | Redundant router having load sharing functionality | |
| CN102045379A (en) | Method and system for IP storage and storage equipment | |
| CN102843255B (en) | Peer-to-peer based network management method and proxy selection server | |
| JP2009518883A (en) | Distributed service site registration method and registration system | |
| CN102316086A (en) | Relay method for service data and relay node system | |
| US20040199643A1 (en) | Distributed service component systems | |
| JP2006157313A (en) | Path creation system, path creation apparatus and path creation program | |
| EP3562101A1 (en) | Bras management method, packet forwarding method, packet forwarding controller, and bras | |
| CN102148847B (en) | Based on the method and system of the client access peer-to-peer network of RELOAD | |
| US20230318960A1 (en) | Methods, systems, and computer readable media for service communication proxy (scp) routing | |
| KR20150062904A (en) | A method for creation, retrieval, update and deletion of group resource with child group and search attributes and apparatus thereof | |
| CN117768924A (en) | Network disaster recovery method, device, client and service control point | |
| KR20150066240A (en) | Middle node for synchronization of notification message delivery | |
| CN117640732A (en) | Bank application communication method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |