WO2016177144A1 - 网元监测方法和装置 - Google Patents

网元监测方法和装置 Download PDF

Info

Publication number
WO2016177144A1
WO2016177144A1 PCT/CN2016/076754 CN2016076754W WO2016177144A1 WO 2016177144 A1 WO2016177144 A1 WO 2016177144A1 CN 2016076754 W CN2016076754 W CN 2016076754W WO 2016177144 A1 WO2016177144 A1 WO 2016177144A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
preset
request
sent
response
Prior art date
Application number
PCT/CN2016/076754
Other languages
English (en)
French (fr)
Inventor
胡良俊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016177144A1 publication Critical patent/WO2016177144A1/zh

Links

Images

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

Definitions

  • the present application relates to the field of network management, for example, to a network element monitoring method and apparatus.
  • a polling method is usually adopted.
  • the so-called polling is that the network management system periodically sends an inquiry message to the network element.
  • the network element has a response message and returns it to the network management system, the network element is normal; but if the network element exceeds a certain time, the network management system The system does not receive the response packet of the network element, that is, the network element does not return a response, indicating that the network element is faulty.
  • the network management system is required to quickly discover the network element fault.
  • the network element managed by the network management system is large, such as when several thousand tens of thousands are required, the network management is required. It is very difficult for the system to quickly discover network element failures.
  • a common polling method is to use the Simple Network Management Protocol (SNMP) to poll the status of each network element in the network management system, that is, to send an SNMP GET request to a network element, and wait for the network element to return. After responding or timeout, the same method is used to poll the next network element. If the average time for a network element polling is t and the total number of network elements is n, then the time for the network element to poll the network management system is n ⁇ t. When the value of n reaches several thousand, the total time of polling will be very high. long.
  • An improvement to the related art is to use multi-threaded concurrent polling.
  • the total time of polling is (n ⁇ t / m), in the case of a certain value of n and t, in order to shorten the polling time, the value of m will be increased as much as possible, that is, the number of threads is increased. But adding more threads requires more system resources and requires higher performance hardware support.
  • the embodiment of the invention provides a network element monitoring method and device, which solves the technical problem that the polling technology has a long polling time and the network management has a large thread overhead during the polling process.
  • the preset request is sequentially sent to the network element that needs to be polled.
  • the network element returns a response according to the preset request;
  • the response When the response is received, it is determined that the corresponding network element is normal according to the identifier information of the response.
  • the preset request is sequentially sent to the network element that needs to be polled, after the step of returning the response by the network element according to the preset request,
  • the identifier information of the network element that has sent the preset request is added to the timeout queue.
  • the method further includes:
  • determining whether the number of the identification information of the network element in the timeout queue is not zero, determining whether the number of times the preset request is sent to the network element corresponding to the identifier information reaches a preset value include:
  • the network element corresponding to the identifier information continues to send the preset request.
  • the step of sequentially sending the preset request to the network element that needs to be polled, for the network element to return a response according to the preset request includes:
  • the preset number of preset requests are sequentially sent to the network element that needs to be polled according to the instruction;
  • the preset number of preset requests is continuously sent to the network element that needs to be polled.
  • the embodiment of the present invention further provides a network element monitoring apparatus, where the network element monitoring apparatus includes:
  • the first sending module is configured to: when detecting an instruction to start the polling task, sequentially send a preset request to the network element that needs to be polled, so that the network element returns a response according to the preset request;
  • the first determining module is configured to: determine whether the response returned by the network element is received;
  • the first determining module is configured to: when receiving the response, determine that the corresponding network element is normal according to the identifier information of the response.
  • the network element monitoring apparatus further includes an adding module, configured to add the identifier information of the network element that has sent the preset request to the timeout queue.
  • the network element monitoring device further includes:
  • the removal module is configured to: remove the identifier information corresponding to the normal network element from the timeout queue;
  • the second judging module is configured to: determine whether the number of identifiers of the network element in the timeout queue is zero;
  • the third determining module is configured to: if the number of the identification information of the network element in the timeout queue is not zero, determine whether the number of times the preset request is sent to the network element corresponding to the identifier information reaches a preset value;
  • the second determining module is configured to: if the number of times the preset request is sent to the network element corresponding to the identifier information reaches a preset value, determine that the network element is faulty, and remove the identifier information of the network element from the timeout queue .
  • the network element monitoring apparatus further includes: a second sending module, configured to: if the number of times the preset request is sent to the network element corresponding to the identifier information does not reach a preset value, corresponding to the identifier information The network element continues to send the preset request.
  • a second sending module configured to: if the number of times the preset request is sent to the network element corresponding to the identifier information does not reach a preset value, corresponding to the identifier information The network element continues to send the preset request.
  • the first sending module includes:
  • the first sending unit is configured to: when detecting the instruction to start the polling task, sequentially send a preset number of preset requests to the network element that needs to be polled according to the instruction;
  • the second sending unit is configured to: after waiting for the preset time, continue to send a preset number of preset requests to the network element that needs to be polled.
  • a computer readable storage medium storing computer executable instructions for performing the above method.
  • the network device sends a preset request to the network element that needs to be polled, and after the network element receives the preset request, the network device returns a response, and after receiving the response, the network management device determines the identifier according to the response. It is determined that the corresponding network element is normal. That is, after sending a request to a network element, the network management device does not have to wait for the response to return to start sending a request to the next network element. Reduces the time for network management polling and reduces the overhead of the network management thread during polling.
  • FIG. 1 is a schematic flowchart of a first embodiment of a network element monitoring method according to the present invention
  • FIG. 2 is a sequence of sequentially sending a preset request to a network element that needs to be polled, for the network element to return a response according to the preset request, when an instruction to start a polling task is detected in the embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a second embodiment of a network element monitoring method according to the present invention.
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a network element monitoring apparatus according to the present invention.
  • FIG. 5 is a schematic diagram of a refinement function module of an embodiment of a first sending module according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of functional modules of a second embodiment of a network element monitoring apparatus according to the present invention.
  • the preset request is sequentially sent to the network element that needs to be polled, so that the network element returns a response according to the preset request;
  • the response returned by the network element; when the response is received, determining that the corresponding network element is normal according to the identification information of the response.
  • the yuan is normal. That is, after sending a request to a network element, the network management device does not have to wait for the response to return to start sending a request to the next network element. Reduces the time for network management polling and reduces the overhead of the network management thread during polling.
  • the network management device After sending an SNMP GET request to a network element, the network management device waits for the network element to return a response or the request times out, and then sends an SNMP GET request to the next network element, resulting in The network management polling time is long and the thread overhead is large.
  • the present application provides a network element monitoring method.
  • FIG. 1 is a schematic flowchart diagram of a first embodiment of a network element monitoring method according to the present invention.
  • the network element monitoring method includes:
  • step S10 when the instruction to start the polling task is detected, the preset request is sequentially sent to the network element that needs to be polled, so that the network element returns a response according to the preset request.
  • the NMS creates different polling tasks based on the type of NEs and sets a corresponding polling period for each polling task.
  • the polling period expires, that is, when the network management detects the instruction to start the polling task, the polling task is started, and the preset request is sent to the network element that needs to be polled, that is, the network management sends a pre-order to a network element.
  • the network element does not need to wait until the network element returns a response according to the preset request to start sending a preset request to the next network element.
  • the type of the network element may be classified according to a network used by the network element, such as Put the network elements of the 2G network into a table, put the network elements that use the 3G network into a table, and put the network elements of the 4G network into a table, and set a polling task for each table.
  • Each polling task corresponds to one polling period, and may also be divided according to the function, purpose, and the like of the network element.
  • the setting of the polling period is determined by the network element size managed by the network management system and the network condition of the network element. If the polling period can be set to one minute, that is, the corresponding polling task is polled every one minute, and each polling task corresponds to a timer for monitoring whether the polling period is reached. time.
  • the network management initiates a polling task through the timer, such as one minute after the last polling task.
  • the preset request includes, but is not limited to, an SNMP GET request.
  • the network management performs a polling task by querying a simple variable of the network element, such as querying sysName, which is used to represent a table column, a variable, and a stored procedure parameter for storing an object name.
  • a simple variable of the network element such as querying sysName
  • the content of the protocol data unit sent by the network management system when querying the network element sysName is of type TYPE: 0; the request identification information Request ID: global unique ID value; the error status error status: 0; the error indicator error index: 0; Variable-Bindings: 1.1.3.6.1.2.1.1.5.0.
  • Step S20 determining whether a response returned by the network element is received
  • Step S30 When receiving the response, determine that the corresponding network element is normal according to the identifier information of the response.
  • the network management determines whether the response returned by the network element according to the preset request sent by the network management is received.
  • the network element managed by the network management device is normal, the network element returns a corresponding response to the network management system when receiving the preset request sent by the network management system.
  • the network management system receives the response returned by the network element, it determines that the corresponding network element is normal according to the identifier information of the response.
  • the content of the protocol data unit of the SNMP response is TYPE: 0; Request ID: global unique ID value; error status: No error noError; error index: 0; Variable-Bindings: .1.3.6.1.2.1.1.5.0: sysName.
  • the request identifier Request ID in the SNMP GET response returned by the network element is the same as the Request ID in the SNMP GET request sent by the network management, and the network management determines that the SNMP GET response is based on the Request ID. Which network element is sent.
  • the network device sends a preset request to the network element that needs to be polled, and the network element returns a response after receiving the preset request, and after receiving the response, the network management determines, according to the identifier information of the response.
  • the corresponding network element is normal. That is, after sending a request to a network element, the network management device does not have to wait for the response to return to start sending a request to the next network element. Reduces the time for network management polling and reduces the overhead of the network management thread during polling.
  • a preset request is sequentially sent to a network element that needs to be polled, for the network element to return according to the preset request.
  • the step S10 includes:
  • Step S11 when detecting an instruction to start a polling task, sequentially send a preset number of preset requests to the network element that needs to be polled according to the instruction;
  • Step S12 After waiting for the preset time, continue to send a preset number of preset requests to the network element that needs to be polled.
  • the network management device sequentially sends a preset number of presets to the network element that needs to be polled according to the instruction.
  • the request after the preset number of preset requests are sent, waits for a preset time, and continues to send a preset number of preset requests to the network element that needs to be polled.
  • the network management device sends a preset number of SNMP GET requests to the network element that needs to be polled according to the instruction, and waits for a preset time after the preset number of SNMP GET requests are sent.
  • the network management device After waiting for the preset time, the network management device continues to send a preset number of SNMP GET requests to the network element that needs to be polled.
  • the preset number and the preset time are set according to the capability of the UDP (User Datagram Protocol) protocol stack to process data, because SNMP is based on UDP, and the number of SNMP GET requests sent by the network management is too For a long time, the UDP protocol stack will not be processed, which may cause some SNMP GET request packets to be lost. Therefore, after waiting for a preset time, the NMS continues to send preset numbers to the NEs that need to be polled. SNMP GET request. If the preset number is 10, the preset time is 20 ms.
  • the network management device when detecting the instruction to start the polling task, sequentially sends 10 SNMP GET requests to the network element that needs to be polled according to the instruction, and waits for 20 ms after sending 10 SNMP GET requests. After the 10 SNMP GET requests are sent, the 10 NE GET requests are continuously sent to the NEs that need to be polled.
  • the network device waits for the preset time, and then continues to send the preset number of preset requests to the network element that needs to be polled.
  • the data packet is lost, and the request to be sent is sent out every time, which improves the accuracy of the network element monitoring method.
  • FIG. 3 is a schematic flowchart of a second embodiment of a network element monitoring method according to the present invention.
  • the second embodiment of the network element monitoring method of the present invention is proposed based on the first embodiment.
  • step S10 the method further includes:
  • Step S40 Add the identifier information of the network element that has been sent the preset request to the timeout queue.
  • the method may further include:
  • Step S50 The identification information corresponding to the normal network element is removed from the timeout queue.
  • Step S60 determining whether the number of identification information of the network element in the timeout queue is zero;
  • Step S70 if the number of the identification information of the network element in the timeout queue is not zero, it is determined whether a preset number of preset requests have been sent to the network element corresponding to the identification information;
  • the network management device After the network management device sends the preset request to the network element, the identifier information of the network element that has been sent the preset request is added to the timeout queue, and the identifier information corresponding to the normal network element is removed from the timeout queue.
  • the network management periodically detects the number of the identification information of the network element in the timeout queue, and determines whether the number of the identification information of the network element in the timeout queue is zero. That is, the network management device detects the number of identification information of the network element in the timeout queue after the timer is separated by a timer. For example, the number of the identification information of the network element in the timeout queue is detected every 30 seconds.
  • the network elements that are not faulty in the current polling task are all normal network elements. If the network management unit finds that the number of the network element information in the timeout queue is not zero, it indicates that the network element in the timeout queue does not return a response to the network management within the timeout period. If the identifier information of the network element in the timeout queue has not been removed from the timeout queue after the timeout period, that is, the network management system does not receive the return response of the network element, it indicates that the network element times out.
  • the timeout period is a time when the network management station sends the preset request to receive the response of the network element.
  • the timeout period is longer, but usually the network transmission is fast. Usually 3 seconds is enough. If the number of the identification information of the network element in the timeout queue of the network management is not zero, it is determined whether the number of times the preset request is sent to the network element corresponding to the identifier information in the timeout queue reaches a preset value.
  • Step S80 If the number of times the preset request is sent to the network element corresponding to the identifier information reaches a preset value, the network element is determined to be faulty, and the identifier information of the network element is removed from the timeout queue.
  • Step S90 If the number of times the preset request is sent to the network element corresponding to the identifier information does not reach the preset value, the network element corresponding to the identifier information continues to send the preset request.
  • the preset request is continued to be sent to the network element until the preset number of times is reached.
  • the preset number of times can be set as needed, for example, it can be set to 1 time, 2 times, 3 times, etc., optionally, set to 2 times.
  • the network management finds a timeout queue On the identifier information of the network element, it is determined whether the SNMP GET request is sent twice to the network element corresponding to the identifier information in the timeout queue. And if the network management device has sent the SNMP GET request to the network element corresponding to the identifier information in the timeout queue, the identifier information of the network element is removed from the timeout queue, and the network element is determined to be faulty.
  • the network element corresponding to the identification information in the timeout queue is sent multiple times, and the request is excluded from being lost during the transmission process.
  • the situation improves the accuracy of the network element monitoring method.
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a network element monitoring apparatus according to the present invention.
  • the network element monitoring apparatus includes:
  • the first sending module 10 is configured to: when detecting an instruction to start a polling task, sequentially send a preset request to the network element that needs to be polled, so that the network element returns a response according to the preset request;
  • the NMS creates different polling tasks based on the type of NEs and sets a corresponding polling period for each polling task.
  • the polling period expires, that is, when the network management detects the instruction to start the polling task, the polling task is started, and the preset request is sent to the network element that needs to be polled, that is, the network management sends a pre-order to a network element.
  • the network element does not need to wait until the network element returns a response according to the preset request to start sending a preset request to the next network element.
  • the type of the network element may be divided according to the network used by the network element.
  • the network element using the 2G network is placed in a table, and the network element using the 3G network is placed in a table, and the network element of the 4G network is used.
  • a polling task is set for each table, and each polling task corresponds to one polling period, and may also be divided according to the function and use of the network element.
  • the setting of the polling period is determined by the network element size managed by the network management system and the network condition of the network element. If the polling period can be set to one minute, that is, the corresponding polling task is polled every one minute, and each polling task corresponds to a timer for monitoring whether the polling period is reached. time.
  • the network management initiates a polling task through the timer, such as one minute after the last polling task.
  • the preset request includes, but is not limited to, an SNMP GET request.
  • the network management performs a polling task by querying a simple variable of the network element, such as querying sysName, which is used to represent a table column, a variable, and a stored procedure parameter for storing an object name.
  • a simple variable of the network element such as querying sysName
  • the content of the protocol data unit sent by the network management system when querying the network element sysName is of type TYPE: 0; the request identification information Request ID: global unique ID value; the error status error status: 0; the error indicator error index: 0; Variable-Bindings: 1.1.3.6.1.2.1.1.5.0.
  • the first determining module 20 is configured to: determine whether a response returned by the network element is received;
  • the first determining module 30 is configured to: when receiving the response, determine that the corresponding network element is normal according to the identifier information of the response.
  • the network management determines whether the response returned by the network element according to the preset request sent by the network element is received.
  • the network element managed by the network management device is normal, the network element returns a corresponding response to the network management system when receiving the preset request sent by the network management system.
  • the network management system receives the response returned by the network element, it determines that the corresponding network element is normal according to the identifier information of the response.
  • the network device sends a preset request to the network element that needs to be polled, and the network element returns a response after receiving the preset request, and after receiving the response, the network management determines, according to the identifier information of the response.
  • the corresponding network element is normal. That is, after sending a request to a network element, the network management device does not have to wait for the response to return to start sending a request to the next network element. Reduces the time for network management polling and reduces the overhead of the network management thread during polling.
  • FIG. 5 is a schematic diagram of a refinement function module of an embodiment of a first sending module according to an embodiment of the present invention.
  • the first sending module 10 includes:
  • the first sending unit 11 is configured to: when detecting an instruction to start a polling task, sequentially send a preset number of preset requests to the network element that needs to be polled according to the instruction;
  • the second sending unit 12 is configured to: after waiting for the preset time, continue to send a preset number of preset requests to the network element that needs to be polled.
  • the network management device sequentially sends a preset number of presets to the network element that needs to be polled according to the instruction.
  • the request after the preset number of preset requests are sent, waits for a preset time, and continues to send a preset number of preset requests to the network element that needs to be polled.
  • the network management device sends a preset number of SNMP GET requests to the network element that needs to be polled according to the instruction, and waits for a preset time after the preset number of SNMP GET requests are sent.
  • the network management device After waiting for the preset time, the network management device continues to send a preset number of SNMP GET requests to the network element that needs to be polled.
  • the preset number and preset time are according to UDP (User Datagram Protocol)
  • UDP User Datagram Protocol
  • the NMS continues to send a preset number of SNMP GET requests to the NEs that need to be polled. If the preset number is 10, the preset time is 20 ms.
  • the network management device when detecting the instruction to start the polling task, sequentially sends 10 SNMP GET requests to the network element that needs to be polled according to the instruction, and waits for 20 ms after sending 10 SNMP GET requests. After the 10 SNMP GET requests are sent, the 10 NE GET requests are continuously sent to the NEs that need to be polled.
  • the network device waits for the preset time, and then continues to send the preset number of preset requests to the network element that needs to be polled.
  • the data packet is lost, and the request to be sent is sent out every time, which improves the accuracy of the network element monitoring method.
  • FIG. 6 is a schematic diagram of functional modules of a second embodiment of a network element monitoring apparatus according to the present invention.
  • the second embodiment of the network element monitoring apparatus of the present invention is proposed based on the first embodiment.
  • the network element monitoring apparatus further includes:
  • the adding module 40 is configured to: add the identifier information of the network element that has been sent the preset request to the timeout queue;
  • the removal module 50 is configured to: remove the identifier information corresponding to the normal network element from the timeout queue;
  • the second judging module 60 is configured to: determine whether the number of identifiers of the network element in the timeout queue is zero;
  • the third determining module 70 is configured to: if the number of the identification information of the network element in the timeout queue is not zero, determine whether the number of times the preset request is sent to the network element corresponding to the identifier information reaches a preset value;
  • the network management device After the network management device sends the preset request to the network element, the identifier information of the network element that has been sent by the preset request is added to the timeout queue, and the identifier information corresponding to the normal network element is removed from the timeout queue.
  • the network management periodically detects the number of the identification information of the network element in the timeout queue, and determines whether the number of the identification information of the network element in the timeout queue is zero. That is, the network management device detects the number of identification information of the network element in the timeout queue after a certain period of time, and detects the number of identification information of the network element in the timeout queue every 30 seconds.
  • the network elements that are not faulty in the current polling task are all normal network elements. If When the network management unit finds that the number of the identifiers of the network elements in the timeout queue is not zero, it indicates that the network element in the timeout queue does not return a response to the network management within the timeout period. If the identifier information of the network element in the timeout queue has not been removed from the timeout queue after the timeout period, that is, the network management system does not receive the return response of the network element, it indicates that the network element times out.
  • the timeout period is a time when the network management station sends the preset request to receive the response of the network element.
  • the timeout period is longer, but usually the network transmission is fast. Usually 3 seconds is enough. If the number of the identification information of the network element in the timeout queue of the network management is not zero, it is further determined whether the number of times the preset request is sent to the network element corresponding to the identifier information reaches a preset value.
  • the second determining module 80 is configured to: if the number of times the preset request is sent to the network element corresponding to the identifier information reaches a preset value, determine that the network element is faulty, and remove the identifier information of the network element from the timeout period. queue;
  • the second sending module 90 is configured to continue to send the preset request to the network element corresponding to the identifier information if the number of times the preset request is sent to the network element corresponding to the identifier information does not reach the preset value.
  • the network management device sends the preset request to the network element corresponding to the identifier information reaches a preset value, the network element is determined to be faulty, and the identifier information of the network element is removed from the timeout queue. If the number of times the network management device sends the preset request to the network element corresponding to the identifier information does not reach the preset value, the preset request is continued to be sent to the network element until the preset number of times is reached.
  • the preset number of times can be set as needed, for example, it can be set to 1 time, 2 times, 3 times, etc., optionally, set to 2 times.
  • the network management device finds the identifier information of the network element in the timeout queue, it further determines whether the SNMP GET request is sent twice to the network element corresponding to the identifier information in the timeout queue. And if the network management device has sent the SNMP GET request to the network element corresponding to the identifier information in the timeout queue, the identifier information of the network element is removed from the timeout queue, and the network element is determined to be faulty.
  • the network element corresponding to the identification information in the timeout queue is sent multiple times, and the request is excluded from being lost during the transmission process.
  • the situation improves the accuracy of the network element monitoring method.
  • the embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions for executing the method described in the foregoing embodiments.
  • the contributing portion can be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, optical disk), including a number of instructions for making a terminal device (which can be a mobile phone, The computer, server, air conditioner, or network device, etc.) performs the method described in the embodiments of the present invention.
  • a storage medium such as ROM/RAM, disk, optical disk
  • the embodiment of the invention reduces the time for the network management polling and reduces the thread overhead of the network management during the polling process.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种网元监测方法，包括：当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应；判断是否在接收到网元返回的响应；当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。

Description

网元监测方法和装置 技术领域
本申请涉及网络管理领域，例如涉及一种网元监测方法和装置。
背景技术
在网络管理中，当需要监测网元是否正常时，通常都采用轮询的方法。所谓轮询，是网管系统定期的向网元发送查询报文，当所述网元有应答报文返回给所述网管系统时，说明所述网元正常；但是如果超过一定时间，所述网管系统没有接收到所述网元的应答报文，即所述网元没有返回响应，则说明所述网元出现故障。当网管系统中的网元出现故障时，要求网管系统能够快速发现网元故障，但是当所述网管系统管理的网元规模较大时，如达到几千上万个的时候，要求所述网管系统快速发现网元故障是很难做到。
常见的轮询方法是利用SNMP(Simple Network Management Protocol，简单网络管理协议)依次对网管系统中的每个网元状态进行轮询，即对一个网元发送SNMP GET请求，等待所述网元返回响应或者超时后，再对下一个网元采取同样办法进行轮询。假如一个网元轮询平均时间为t，网元总数为n，那么网管系统中网元轮询一遍的时间为n×t，当n值达到几千的时候，轮询的总时间就会很长。相关技术的改进办法是采用多线程并发去轮询。若线程数为m，那么轮询的总时间为(n×t/m)，在n值和t值一定的情况下，为缩短轮询时间会尽量增大m值，即增加线程数。但是增加线程就需要更多的系统资源，需要更高性能的硬件支持。
上述内容仅用于辅助理解本发明实施例的技术方案，并不代表承认上述内容是现有技术。
发明内容
本发明实施例提供一种网元监测方法及装置，解决轮询技术轮询时间长，网管在轮询过程中线程开销大的技术问题。
本发明实施例提供的一种网元监测方法，包括：
当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求， 以供所述网元根据所述预设请求返回响应；
判断是否接收到网元返回的响应；
当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。
可选地，所述当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应的步骤之后，还包括将被发送过所述预设请求的网元的标识信息添加到超时队列中。
可选地，所述当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常的步骤之后，还包括：
将正常网元对应的标识信息移出所述超时队列；
判断所述超时队列中的网元的标识信息个数是否为零；
当判断所述超时队列中网元的标识信息个数不为零，则判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值；
若向所述标识信息对应的网元发送预设请求的次数达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列。
可选地，所述若所述超时队列中网元的标识信息个数不为零，则判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值的步骤之后，还包括：
若向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述标识信息对应的网元继续发送所述预设请求。
可选地，所述当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应的步骤包括：
当侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发送预设个数的预设请求；
在等待预设时间后，继续向需要轮询的网元依次发送预设个数的预设请求。
本发明实施例还提供一种网元监测装置，所述网元监测装置包括：
第一发送模块，设置为：当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应；
第一判断模块，设置为：判断是否在接收到网元返回的响应；以及
第一判定模块，设置为：当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。
可选地，所述网元监测装置还包括添加模块，用于将被发送过所述预设请求的网元的标识信息添加到超时队列中。
可选地，所述网元监测装置还包括：
移出模块，设置为：将正常网元对应的标识信息移出所述超时队列；
第二判断模块，设置为：判断所述超时队列中网元的标识信息个数是否为零；
第三判断模块，设置为：若所述超时队列中网元的标识信息个数不为零，则判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值；
第二判定模块，设置为：若向所述标识信息对应的网元发送预设请求的次数达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列。
可选地，所述网元监测装置还包括第二发送模块，设置为：若向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述标识信息对应的网元继续发送所述预设请求。
可选地，所述第一发送模块包括：
第一发送单元，设置为：当侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发送预设个数的预设请求；
第二发送单元，设置为：在等待预设时间后，继续向需要轮询的网元依次发送预设个数的预设请求。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述方法。
本发明实施例通过网管向需要轮询的网元依次发送预设请求，当网元接收到所述预设请求之后返回响应，所述网管接收到所述响应之后，根据所述响应的标识信息判定对应的网元正常。即网管在向一个网元发送请求后，不必等到其返回响应就开始对下一个网元发送请求。减少了网管轮询的时间和降低了网管在轮询过程中线程的开销。
附图说明
图1为本发明网元监测方法第一实施例的流程示意图；
图2为本发明实施例中当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应的一种流程示意 图；
图3为本发明网元监测方法第二实施例的流程示意图；
图4为本发明网元监测装置第一实施例的功能模块示意图；
图5为本发明实施例中第一发送模块的一实施例的细化功能模块示意图；
图6为本发明网元监测装置第二实施例的功能模块示意图。
实施方式
本发明实施例中，当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应；判断是否接收到网元返回的响应；当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。通过网管向需要轮询的网元依次发送预设请求，当网元接收到所述预设请求之后返回响应，所述网管接收到所述响应之后，根据所述响应的标识信息判定对应的网元正常。即网管在向一个网元发送请求后，不必等到其返回响应就开始对下一个网元发送请求。减少了网管轮询的时间和降低了网管在轮询过程中线程的开销。
由于在相关技术的网元监测方法中，网管在对一个网元发送SNMP GET请求后，要等待所述网元返回响应或者所述请求超时后，再向下一个网元发送SNMP GET请求，导致网管轮询时间长，线程开销大。
基于上述问题，本申请提供一种网元监测方法。
参照图1，图1为本发明网元监测方法第一实施例的流程示意图。
在本实施例中，所述网元监测方法包括：
步骤S10，当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应；
网管根据网元的类型创建不同的轮询任务，并为每个轮询任务设置一个对应的轮询周期。当轮询周期到时，即所述网管侦测到开始轮询任务的指令时，启动轮询任务，向需要轮询的网元依次发送预设请求，即所述网管向一个网元发送预设请求后，不用等到所述网元根据所述预设请求返回响应就开始向下一个网元发送预设请求。所述网元的类型可以根据该网元使用的网络来划分，如 将使用2G网络的网元放入一个表中，将使用3G网络的网元放入一个表中，使用4G网络的网元放入一个表中，为每一个表都设置一种轮询任务，每一种轮询任务对应一个轮询周期，也可以根据所述网元的功能、用途等进行划分。所述轮询周期的设定由所述网管管理的网元规模和网元所在的网络状况而定。如所述轮询周期可以设定为一分钟，即每隔一分钟就对对应的轮询任务轮询一次，每个轮询任务都对应着有一个定时器，用来监测是否到达轮询周期的时间。如当上一次轮询任务过去一分钟之后，所述网管通过所述定时器启动轮询任务。所述预设请求包括但不限于SNMP GET请求。
所述网管执行轮询任务只要查询所述网元的一个简单的变量，如查询sysName，所述sysName是用于表示表列、变量以及用于存储对象名的存储过程参数。如所述网管查询所述网元sysName时发送的协议数据单元内容为类型TYPE：0；请求标识信息Request ID：全局唯一ID值；错误状态error status：0；错误指标error index：0；变量绑定Variable-Bindings：.1.3.6.1.2.1.1.5.0。
步骤S20，判断是否接收到网元返回的响应；
步骤S30，当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。
所述网管判断是否接收到网元根据网管发送的预设请求返回的响应。当所述网管管理的网元正常时，所述网元在接收到所述网管发送的预设请求时，会返回对应的响应给所述网管。当所述网管接收到所述网元返回的响应时，根据所述响应的标识信息判定对应的网元正常。如当所述网管接收到所述网元根据所述SNMP GET请求返回的SNMP GET响应，则所述SNMP响应的协议数据单元的内容为TYPE：0；Request ID：全局唯一ID值；error status：无错误noError；error index：0；Variable-Bindings：.1.3.6.1.2.1.1.5.0：sysName。
所述网元返回的SNMP GET响应中的请求标识符Request ID与所述网管发送的SNMP GET请求中的Request ID是一样的，所述网管就是根据所述Request ID来确定所述SNMP GET响应是哪个网元发送过来的。
本实施例通过网管向需要轮询的网元依次发送预设请求，当网元接收到所述预设请求之后返回响应，所述网管接收到所述响应之后，根据所述响应的标识信息判定对应的网元正常。即网管在向一个网元发送请求后，不必等到其返回响应就开始对下一个网元发送请求。减少了网管轮询的时间和降低了网管在轮询过程中线程的开销。
参照图2，图2为本发明实施例中当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应的一种流程示意图。所述步骤S10包括：
步骤S11，当侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发送预设个数的预设请求；
步骤S12，在等待预设时间后，继续向需要轮询的网元依次发送预设个数的预设请求。
当网管所管理的网元的轮询周期到来时，即侦测到要开始轮询任务的指令时，所述网管根据所述指令向需要轮询的网元依次发送预设个数的预设请求，当所述预设个数的预设请求发送完毕之后，等待预设时间，继续向需要轮询的网元发送预设个数的预设请求。如所述网管根据所述指令向需要轮询的网元依次发送预设个数的SNMP GET请求，当所述预设个数的SNMP GET请求发送完成之后，等待预设时间。所述网管在等待预设时间之后，继续向需要轮询的网元依次发送预设个数的SNMP GET请求。所述预设个数和预设时间根据UDP(User Datagram Protocol，用户数据协议报)协议栈处理数据的能力来设置，因为SNMP是基于UDP的，当所述网管发送的SNMP GET请求个数太多时，所述UDP协议栈会处理不过来，可能会造成一些SNMP GET请求数据包的丢失，所以需要等待预设时间之后，所述网管才继续向需要轮询的网元依次发送预设个数的SNMP GET请求。如所述预设个数为10个，预设时间为20ms。即所述网管在侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发送10个SNMP GET请求，在发送完10个SNMP GET请求之后，等待20ms，保证所述10个SNMP GET请求发送完毕之后，继续向需要轮询的网元依次发送10个SNMP GET请求。
本实施例通过在网管依次向需要轮询的网元发送预设个数的预设请求之后，等待预设时间，才继续向需要轮询的网元依次发送预设个数的预设请求，以防在传输预设请求数据包的过程中造成数据包的丢失，保证了每次要发送的请求都发送出去，提高了网元监测方法的准确度。
参照图3，图3为本发明网元监测方法第二实施例的流程示意图，基于第一实施例提出本发明网元监测方法第二实施例。
在本实施例中，步骤S10之后，还包括：
步骤S40，将被发送过所述预设请求的网元的标识信息添加到超时队列中；
步骤S30之后，还可以包括：
步骤S50，将正常网元对应的标识信息移出所述超时队列；
步骤S60，判断所述超时队列中网元的标识信息个数是否为零；
步骤S70，若所述超时队列中网元的标识信息个数不为零，则判断是否已发送预设次数的预设请求给所述标识信息对应的网元；
当网管向网元发送预设请求之后，将被发送过所述预设请求的网元的标识信息添加到其超时队列中，并将正常网元对应的标识信息移出所述超时队列。所述网管定时检测其超时队列中网元的标识信息个数，判断所述超时队列中网元的标识信息个数是否为零。即所述网管通过其定时器在间隔一定的时间段后，检测其超时队列中网元的标识信息个数，如每间隔30秒钟检测一次其超时队列里面的网元的标识信息个数。若所述网管的超时队列中的网元的标识信息个数为零，则说明本次轮询任务中没有出现故障的网元，全部都是正常的网元。若所述网管发现所述超时队列中的网元的标识信息个数不为零时，则表示所述超时队列中的网元在超时时间内没有返回响应给所述网管。如当所述超时队列中的网元的标识信息在超时时间之后还没有被移出超时队列，即所述网管没有接收到所述网元的返回响应，则表示所述网元超时。所述超时时间是所述网管在发送所述预设请求到接收到所述网元的响应的时间，如果当前网络较差时，超时时间会长一点，但是通常情况下网络传输是很快的，一般3秒时间就足够了。若所述网管的超时队列中网元的标识信息个数不为零，则判断向所述超时队列中标识信息对应的网元发送预设请求的次数是否达到预设值。
步骤S80，若向所述标识信息对应的网元发送预设请求的次数达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列；
步骤S90，若向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述标识信息对应的网元继续发送所述预设请求。
若向所述标识信息对应的网元发送预设请求的次数是否达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列。若向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述网元继续发送所述预设请求，直到达到预设次数。所述预设次数可以根据需要设置，如可以设置为1次，2次，3次等，可选地，设置为2次。如当所述网管发现超时队列里存 在网元的标识信息，则判断是否发送过两次SNMP GET请求给所述超时队列中标识信息对应的网元。若所述网管已经发送过两次SNMP GET请求给所述超时队列中标识信息对应的网元，则将所述网元的标识信息移出所述超时队列，判定所述网元故障。
本实施例通过当网管的超时队列中网元的标识信息个数不为零时，进行多次发送请求到所述超时队列中的标识信息对应的网元，排除所述请求在传输过程丢失的情况，提高了网元监测方法的准确度。
参照图4，图4为本发明网元监测装置第一实施例的功能模块示意图。
在本实施例中，所述网元监测装置包括：
第一发送模块10，设置为：当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应；
网管根据网元的类型创建不同的轮询任务，并为每个轮询任务设置一个对应的轮询周期。当轮询周期到时，即所述网管侦测到开始轮询任务的指令时，启动轮询任务，向需要轮询的网元依次发送预设请求，即所述网管向一个网元发送预设请求后，不用等到所述网元根据所述预设请求返回响应就开始向下一个网元发送预设请求。所述网元的类型可以根据其使用的网络来划分，如将使用2G网络的网元放入一个表中，将使用3G网络的网元放入一个表中，使用4G网络的网元放入一个表中，为每一个表都设置一种轮询任务，每一种轮询任务对应一个轮询周期，也可以根据所述网元的功能、用途等进行划分。所述轮询周期的设定由所述网管管理的网元规模和网元所在的网络状况而定。如所述轮询周期可以设定为一分钟，即每隔一分钟就对对应的轮询任务轮询一次，每个轮询任务都对应着有一个定时器，用来监测是否到达轮询周期的时间。如当上一次轮询任务过去一分钟之后，所述网管通过所述定时器启动轮询任务。所述预设请求包括但不限于SNMP GET请求。
所述网管执行轮询任务只要查询所述网元的一个简单的变量，如查询sysName，所述sysName是用于表示表列、变量以及用于存储对象名的存储过程参数。如所述网管查询所述网元sysName时发送的协议数据单元内容为类型TYPE：0；请求标识信息Request ID：全局唯一ID值；错误状态error status：0；错误指标error index：0；变量绑定Variable-Bindings：.1.3.6.1.2.1.1.5.0。
第一判断模块20，设置为：判断是否接收到网元返回的响应；
第一判定模块30，设置为：当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。
所述网管判断是否接收到网元根据网元发送的预设请求返回的响应。当所述网管管理的网元正常时，所述网元在接收到所述网管发送的预设请求时，会返回对应的响应给所述网管。当所述网管接收到所述网元返回的响应时，根据所述响应的标识信息判定对应的网元正常。如当所述网管接收到所述网元根据所述SNMP GET请求返回的SNMP GET响应，则所述SNMP响应的协议数据单元的内容为TYPE：0；Request ID：全局唯一ID值；error status：无错误noError；error index：0；Variable-Bindings：.1.3.6.1.2.1.1.5.0：sysName。所述网元返回的SNMP GET响应中的请求标识符Request ID与所述网管发送的SNMP GET请求中的Request ID是一样的，所述网管就是根据所述Request ID来确定所述SNMP GET响应是哪个网元发送过来的。
本实施例通过网管向需要轮询的网元依次发送预设请求，当网元接收到所述预设请求之后返回响应，所述网管接收到所述响应之后，根据所述响应的标识信息判定对应的网元正常。即网管在向一个网元发送请求后，不必等到其返回响应就开始对下一个网元发送请求。减少了网管轮询的时间和降低了网管在轮询过程中线程的开销。
参照图5，图5为本发明实施例中第一发送模块的一实施例的细化功能模块示意图。所述第一发送模块10包括：
第一发送单元11，设置为：当侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发送预设个数的预设请求；
第二发送单元12，设置为：在等待预设时间后，继续向需要轮询的网元依次发送预设个数的预设请求。
当网管所管理的网元的轮询周期到来时，即侦测到要开始轮询任务的指令时，所述网管根据所述指令向需要轮询的网元依次发送预设个数的预设请求，当所述预设个数的预设请求发送完毕之后，等待预设时间，继续向需要轮询的网元发送预设个数的预设请求。如所述网管根据所述指令向需要轮询的网元依次发送预设个数的SNMP GET请求，当所述预设个数的SNMP GET请求发送完成之后，等待预设时间。所述网管在等待预设时间之后，继续向需要轮询的网元依次发送预设个数的SNMP GET请求。所述预设个数和预设时间根据UDP (User Datagram Protocol，用户数据协议报)协议栈处理数据的能力来设置，因为SNMP是基于UDP的，当所述网管发送的SNMP GET请求个数太多时，所述UDP协议栈会处理不过来，可能会造成一些SNMP GET请求数据包的丢失，所以需要等待预设时间之后，所述网管才继续向需要轮询的网元依次发送预设个数的SNMP GET请求。如所述预设个数为10个，预设时间为20ms。即所述网管在侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发送10个SNMP GET请求，在发送完10个SNMP GET请求之后，等待20ms，保证所述10个SNMP GET请求发送完毕之后，继续向需要轮询的网元依次发送10个SNMP GET请求。
本实施例通过在网管依次向需要轮询的网元发送预设个数的预设请求之后，等待预设时间，才继续向需要轮询的网元依次发送预设个数的预设请求，以防在传输预设请求数据包的过程中造成数据包的丢失，保证了每次要发送的请求都发送出去，提高了网元监测方法的准确度。
参照图6，图6为本发明网元监测装置第二实施例的功能模块示意图，基于第一实施例提出本发明网元监测装置第二实施例。
在本实施例中，所述网元监测装置还包括：
添加模块40，设置为：将被发送过所述预设请求的网元的标识信息添加到超时队列中；
移出模块50，设置为：将正常网元对应的标识信息移出所述超时队列；
第二判断模块60，设置为：判断所述超时队列里网元的标识信息个数是否为零；
第三判断模块70，设置为：若所述超时队列里网元的标识信息个数不为零，则判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值；
当网管向网元发送预设请求之后，将被发送过所述预设请求的网元的标识信息添加到超时队列中，并将正常网元对应的标识信息移出所述超时队列。所述网管定时检测其超时队列中网元的标识信息个数，判断所述超时队列中网元的标识信息个数是否为零。即所述网管通过定时器在间隔一定的时间段后，检测其超时队列中网元的标识信息个数，如每间隔30秒钟检测一次其超时队列里面的网元的标识信息个数。若所述网管的超时队列中的网元的标识信息个数为零，则说明本次轮询任务中没有出现故障的网元，全部都是正常的网元。若所 述网管发现所述超时队列中的网元的标识信息个数不为零时，则表示所述超时队列中的网元在超时时间内没有返回响应给所述网管。如当所述超时队列中的网元的标识信息在超时时间之后还没有被移出超时队列，即所述网管没有接收到所述网元的返回响应，则表示所述网元超时。所述超时时间是所述网管在发送所述预设请求到接收到所述网元的响应的时间，如果当前网络较差时，超时时间会长一点，但是通常情况下网络传输是很快的，一般3秒时间就足够了。若所述网管的超时队列中网元的标识信息个数不为零，则进一步判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值。
第二判定模块80，设置为：若向所述标识信息对应的网元发送预设请求的次数达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列；
第二发送模块90，设置为：若向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述标识信息对应的网元继续发送所述预设请求。
若所述网管向所述标识信息对应的网元发送预设请求的次数达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列。若所述网管向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述网元继续发送所述预设请求，直到达到预设次数。所述预设次数可以根据需要设置，如可以设置为1次，2次，3次等，可选地，设置为2次。如当所述网管发现超时队列里存在网元的标识信息，则进一步判断是否发送过两次SNMP GET请求给所述超时队列中标识信息对应的网元。若所述网管已经发送过两次SNMP GET请求给所述超时队列中标识信息对应的网元，则将所述网元的标识信息移出所述超时队列，判定所述网元故障。
本实施例通过当网管的超时队列中网元的标识信息个数不为零时，进行多次发送请求到所述超时队列中的标识信息对应的网元，排除所述请求在传输过程丢失的情况，提高了网元监测方法的准确度。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述实施例所述的方法。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，本发明实施方式的技术方案本质上或者说对现有技术做 出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本发明实施例所述的方法。
工业实用性
本发明实施例减少了网管轮询的时间和降低了网管在轮询过程中线程的开销。

Claims (11)

  1. 一种网元监测方法，包括：
    当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应；
    判断是否接收到网元返回的响应；
    当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。
  2. 如权利要求1所述的网元监测方法，所述方法在所述当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应的步骤之后，还包括将被发送过所述预设请求的网元的标识信息添加到超时队列中。
  3. 如权利要求2所述的网元监测方法，所述方法在所述当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常的步骤之后，还包括：
    将正常网元对应的标识信息移出所述超时队列；
    判断所述超时队列中网元的标识信息个数是否为零；
    当判断所述超时队列中网元的标识信息个数不为零，则判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值；
    当向所述标识信息对应的网元发送预设请求的次数达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列。
  4. 如权利要求3所述的网元监测方法，所述方法在所述当判断所述超时队列中网元的标识信息个数不为零，则判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值的步骤之后，还包括：
    若向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述标识信息对应的网元继续发送所述预设请求。
  5. 如权利要求1至4任一项所述的网元监测方法，其中，所述当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应的步骤包括：
    当侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发 送预设个数的预设请求；
    在等待预设时间后，继续向需要轮询的网元依次发送预设个数的预设请求。
  6. 一种网元监测装置，包括：
    第一发送模块，设置为当侦测到开始轮询任务的指令时，向需要轮询的网元依次发送预设请求，以供所述网元根据所述预设请求返回响应；
    第一判断模块，设置为判断是否在接收到网元返回的响应；以及
    第一判定模块，设置为当接收到所述响应时，根据所述响应的标识信息判定对应的网元正常。
  7. 如权利要求6所述的网元监测装置所述网元监测装置还包括添加模块，设置为将被发送过所述预设请求的网元的标识信息添加到超时队列中。
  8. 如权利要求7所述的网元监测装置，所述网元监测装置还包括：
    移出模块，设置为将正常网元对应的标识信息移出所述超时队列；
    第二判断模块，设置为判断所述超时队列中网元的标识信息个数是否为零；
    第三判断模块，设置为若所述超时队列中网元的标识信息个数不为零，则判断向所述标识信息对应的网元发送预设请求的次数是否达到预设值；以及
    第二判定模块，设置为若向所述标识信息对应的网元发送预设请求的次数达到预设值，则判定所述网元故障，将所述网元的标识信息移出所述超时队列。
  9. 如权利要求8所述的网元监测装置，所述网元监测装置还包括第二发送模块，设置为若向所述标识信息对应的网元发送预设请求的次数未达到预设值，则向所述标识信息对应的网元继续发送所述预设请求。
  10. 如权利要求6至9任一项所述的网元监测方法，其中，所述第一发送模块包括：
    第一发送单元，设置为：当侦测到开始轮询任务的指令时，根据所述指令向需要轮询的网元依次发送预设个数的预设请求；以及
    第二发送单元，设置为：在等待预设时间后，继续向需要轮询的网元依次发送预设个数的预设请求。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-10任一项所述的方法。
PCT/CN2016/076754 2015-07-16 2016-03-18 网元监测方法和装置 WO2016177144A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510420193.0 2015-07-16
CN201510420193.0A CN106712979A (zh) 2015-07-16 2015-07-16 网元监测方法和装置

Publications (1)

Publication Number Publication Date
WO2016177144A1 true WO2016177144A1 (zh) 2016-11-10

Family

ID=57217502

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/076754 WO2016177144A1 (zh) 2015-07-16 2016-03-18 网元监测方法和装置

Country Status (2)

Country Link
CN (1) CN106712979A (zh)
WO (1) WO2016177144A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109634252A (zh) * 2018-11-06 2019-04-16 华为技术有限公司 一种根因诊断的方法、装置
CN116431558A (zh) * 2023-06-12 2023-07-14 太初(无锡)电子科技有限公司 一种基于axi协议的请求响应方法、装置、系统及介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111200833B (zh) * 2018-11-19 2021-11-30 大唐移动通信设备有限公司 一种网元状态的确定方法及装置
CN110505286B (zh) * 2019-08-01 2022-05-06 京信网络系统股份有限公司 设备在线的监测方法、装置及系统
CN112433872A (zh) * 2020-10-23 2021-03-02 深圳点猫科技有限公司 一种接口请求超时提醒方法、系统及存储介质
CN113453371B (zh) * 2021-08-31 2021-12-03 蘑菇物联技术（深圳）有限公司 用于无线通信的方法、基站和计算机存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1758617A (zh) * 2004-09-17 2006-04-12 美国博通公司 一种可配置的娱乐网络及其配置方法
CN1859183A (zh) * 2005-12-30 2006-11-08 华为技术有限公司 一种实现设备状态轮询的方法及装置
CN102082689A (zh) * 2011-01-10 2011-06-01 武汉烽火网络有限责任公司 使用异步轮询方式产生设备告警信息的方法
CN104408068A (zh) * 2014-10-29 2015-03-11 中国建设银行股份有限公司 一种报表数据处理方法及相关设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1758617A (zh) * 2004-09-17 2006-04-12 美国博通公司 一种可配置的娱乐网络及其配置方法
CN1859183A (zh) * 2005-12-30 2006-11-08 华为技术有限公司 一种实现设备状态轮询的方法及装置
CN102082689A (zh) * 2011-01-10 2011-06-01 武汉烽火网络有限责任公司 使用异步轮询方式产生设备告警信息的方法
CN104408068A (zh) * 2014-10-29 2015-03-11 中国建设银行股份有限公司 一种报表数据处理方法及相关设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109634252A (zh) * 2018-11-06 2019-04-16 华为技术有限公司 一种根因诊断的方法、装置
CN109634252B (zh) * 2018-11-06 2020-06-26 华为技术有限公司 一种根因诊断的方法、装置
CN116431558A (zh) * 2023-06-12 2023-07-14 太初(无锡)电子科技有限公司 一种基于axi协议的请求响应方法、装置、系统及介质
CN116431558B (zh) * 2023-06-12 2023-09-29 太初(无锡)电子科技有限公司 一种基于axi协议的请求响应方法、装置、系统及介质

Also Published As

Publication number Publication date
CN106712979A (zh) 2017-05-24

Similar Documents

Publication Publication Date Title
WO2016177144A1 (zh) 网元监测方法和装置
US12052150B2 (en) Monitoring wireless access point events
CN101035037B (zh) 检测网络通信质量的方法、系统及相关装置
TW201944236A (zh) 任務處理方法、裝置及系統
EP3607715B1 (en) NF SERVICE CONSUMER RESTART DETECTION USING DIRECT SIGNALING BETWEEN NFs
EP3258644B1 (en) Monitoring processing method and device
CN109150659B (zh) 一种处理器及bfd报文传输方法
CN104202212A (zh) 一种获取分布式集群系统告警的系统和方法
US9049129B2 (en) Node monitoring apparatus, node monitoring method, and computer readable medium
CN112118151A (zh) 网络测速方法、装置、系统、电子设备及存储介质
JP6421516B2 (ja) サーバ装置、冗長構成サーバシステム、情報引継プログラム及び情報引継方法
CN108880913B (zh) 一种流量特征的管理方法、装置及中心节点服务器
CN110224872B (zh) 一种通信方法、装置及存储介质
WO2007059667A1 (fr) Procede d'obtention de donnees d'alarme des elements de reseau
CN108924013B (zh) 网络流量精确采集方法及装置
CN111541771A (zh) 物联网通信方法、装置、系统及计算机可读存储介质
CN111224983A (zh) 跨网段发现设备的方法及装置
CN111092956A (zh) 资源同步方法、装置、存储介质及设备
CN103178985B (zh) 网络设备轮询方法、系统和装置
CN111200578A (zh) 一种通信方法、客户端设备及服务端设备
EP3065445A1 (en) Method, cse, and system for transmitting m2m application request
US20160192110A1 (en) Method and Apparatus for Processing Operation on Endpoint Peripheral
US20060217156A1 (en) Base station controller for radio communication network and method of collecting alarm information thereof
JP3570300B2 (ja) 障害管理方式および方法
CN111385520B (zh) 一种视频监控设备的自动组网方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16789138

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16789138

Country of ref document: EP

Kind code of ref document: A1