WO2019000954A1 - 监测节点存活状态的方法、装置及系统 - Google Patents

监测节点存活状态的方法、装置及系统 Download PDF

Info

Publication number
WO2019000954A1
WO2019000954A1 PCT/CN2018/075659 CN2018075659W WO2019000954A1 WO 2019000954 A1 WO2019000954 A1 WO 2019000954A1 CN 2018075659 W CN2018075659 W CN 2018075659W WO 2019000954 A1 WO2019000954 A1 WO 2019000954A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
survival
state
offline
central
Prior art date
Application number
PCT/CN2018/075659
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
Priority claimed from CN201710612472.6A external-priority patent/CN109218126B/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US16/627,504 priority Critical patent/US11212204B2/en
Publication of WO2019000954A1 publication Critical patent/WO2019000954A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • 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/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a method, apparatus, and system for monitoring a node's survival status.
  • the server is used to monitor the survival of the subordinate nodes.
  • This method has high requirements on the server bandwidth and the storage capacity, and usually the response is slow. Therefore, the node surviving monitoring technology in the related art is not applicable to the case where the central node bandwidth and the computing storage capacity are low, and the cooperative node needs to respond in time after being offline.
  • the embodiments of the present disclosure provide a method, an apparatus, and a system for monitoring a node's survival status, so as to at least solve the technical problem of slow response when monitoring a subordinate node by a server in the related art.
  • a method for monitoring a node survival state including: a first node monitoring a survival state of a second node, wherein the first node and the second node are mutually cooperative nodes; When the survival state indicates that the second node is offline, the first node sends a notification message to the central node indicating that the second node is offline.
  • the method further includes: determining, by the central node, an offline status of the second node; The central node adjusts the collaborative relationship of the governed nodes according to the current topology state of at least one of the first node and the second node.
  • the determining, by the central node, the offline status of the second node includes: the central node performing an attempted communication with the second node; and when the attempting communication fails, the central node determining the second The current state of the node is the offline state.
  • the adjusting, by the central node, the coordinated relationship of the ruled node according to the current topology state of the first node includes one of the following: when the first node has other surviving coordinated nodes, the central node maintains the A collaborative relationship of the nodes; when there is no other surviving cooperating node in the first node, the central node reselects the coordinating node for the ruled node.
  • the central node adjusts, according to a current topology state of at least one of the first node and the second node, a coordinated relationship of the ruled node, including one of the following: there is another surviving at the first node. a cooperative node, and the second node does not have other surviving cooperating nodes, the central node maintains a cooperative relationship of the superordinated nodes; there are other surviving cooperating nodes in the first node, and the third node has other surviving synergies
  • the central node maintains a cooperative relationship of the nodes under its jurisdiction; when there is no other surviving coordinated node in the first node, or when the third node does not have other surviving coordinated nodes, the central node re Selecting a collaborative node for the node under its jurisdiction; wherein the third node is a coordinated node of the second node.
  • the method before the sending, to the central node, the notification message that the second node is offline, the method further includes: determining, by the first node, the current status of the second node according to the Offline status.
  • the first node monitoring the survival status of the second node includes: the first node monitoring a survival status of the second node according to the received survival information of the second node.
  • the first node monitors, according to the received survival information of the second node, the survival status of the second node, where the first node receives the first node according to the first node.
  • the survival information of the second node is monitored by the first time interval between the second node survival information and the second node; the first node is generated according to the second node.
  • the survival information is monitored for a second time interval between the second node and the current generation of the survival information by the second node.
  • the first node monitors, according to the survival information of the second node, the survival status of the second node, where the first node is less than or equal to the first threshold, and the first When the second time is less than or equal to the second threshold, the first node determines that the second node is in a normal state; the first time is less than or equal to the first threshold, and the second time is greater than Or equal to the second threshold, the first node determines that the second node is in an abnormal state; the first time is greater than or equal to the first threshold, and the second node is on When the survival state of a monitoring period is an abnormal state, the first node determines that the survival state of the second node is an offline state; the first time is greater than or equal to the first threshold, and the second node is When the survival state of the monitoring period is a normal state, determining whether the first time is greater than a third threshold, and determining that the second node is in an abnormal state when the determination result is no; The time is greater than or equal to the first
  • the third threshold is greater than the second threshold and the first threshold.
  • the first node monitors, according to the survival information of the second node, the survival status of the second node, where the first node is: when the first time is less than or equal to the first threshold, the A node determines that the survival state of the second node is a normal state; when the first time is greater than or equal to the first threshold, the first node determines that a survival state of the second node is an offline state.
  • the method further includes: the first node receiving the survival information sent by the second node.
  • the central node is any fourth node in the same network.
  • the central node is determined by one of the following methods: preset relationship calculation, network or user designation.
  • the node includes one of the following: a terminal; a gateway.
  • a device for monitoring a node survival state which is applied to a first node, comprising: a monitoring module configured to monitor a survival state of a second node, wherein the first node and the The second node is a cooperative node; the sending module is configured to send, to the central node, a notification message indicating that the second node is offline when the living state indicates that the second node is offline.
  • a system for monitoring a node survival state including: a first node, a second node, and a central node;
  • the first node includes: a monitoring module, configured to monitor the second node a survival state, wherein the first node and the second node are mutually cooperative nodes; and a sending module is configured to send, when the survival state represents that the second node is offline, send the indication to the central node a notification message that the two nodes have been offline;
  • the central node includes: a determining module, configured to determine an offline state of the second node after receiving the notification message; and a management module configured to be according to the first node and The current topology state of at least one of the second nodes adjusts a synergistic relationship of the governed nodes.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the first node monitors a survival state of the second node, where the first node and the second node are mutually cooperative nodes; and when the survival state indicates that the second node is offline, the first node A node sends a notification message to the central node indicating that the second node is offline.
  • FIG. 1 is a network architecture diagram of an embodiment of the present disclosure
  • FIG. 2 is a flow chart of a method of monitoring a node's survival status in accordance with an embodiment of the present disclosure
  • FIG. 3 is a structural block diagram of an apparatus for monitoring a node survival state according to an embodiment of the present disclosure
  • FIG. 4 is a structural block diagram of a system for monitoring a node survival state according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a node survival information sending process according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of processing a offline node by a central node according to an embodiment of the present disclosure.
  • FIG. 1 is a network architecture diagram of an embodiment of the present disclosure.
  • the network architecture includes: a central node, and multiple nodes under the control of the central node. For example, node 1, node 2, etc., there is a synergy relationship between the nodes.
  • FIG. 2 is a flowchart of a method for monitoring a node survival state according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps. step:
  • Step S202 the first node monitors a survival state of the second node, where the first node and the second node are mutually cooperative nodes;
  • Step S204 When the survival state indicates that the second node is offline, the first node sends a notification message to the central node indicating that the second node is offline.
  • the first node monitors the survival state of the second node, where the first node and the second node are mutually cooperative nodes; when the survival state indicates that the second node is offline, the first node sends a notification to the central node for indicating A notification message that the two nodes have been offline.
  • the method further includes:
  • the central node determines an offline state of the second node.
  • the central node adjusts a collaborative relationship of the governed nodes according to a current topology state of at least one of the first node and the second node.
  • the determining, by the central node, the offline status of the second node includes:
  • the central node performs an attempt to communicate with the second node.
  • the central node determines that the current state of the second node is an offline state.
  • the central node adjusts the collaborative relationship of the governed nodes according to the current topology state of the first node, including at least one of the following:
  • the central node maintains the cooperative relationship of the nodes under the jurisdiction
  • the central node When there is no other surviving cooperating node in the first node, the central node re-selects the coordinating node for the node under its jurisdiction.
  • the central node adjusts the collaborative relationship of the governed nodes according to the current topology state of at least one of the first node and the second node, including the following:
  • the central node maintains the cooperative relationship of the nodes under the jurisdiction
  • the central node When there are other surviving cooperating nodes in the first node, and the third node has other surviving cooperating nodes, the central node maintains the cooperative relationship of the nodes under the jurisdiction;
  • the central node When there is no other surviving cooperating node in the first node, or the third node does not have other surviving cooperating nodes, the central node re-selects the coordinating node for the ruled node; wherein the third node is the cooperating node of the second node.
  • the method before the sending, to the central node, the notification message indicating that the second node is offline, the method further includes: determining, by the first node, that the current state of the second node is an offline state according to the survival state.
  • the monitoring, by the first node, the survival status of the second node includes: the first node monitoring the survival status of the second node according to the survival information of the receiving the second node.
  • the survival information includes received time information and generated time information.
  • the monitoring, by the first node, the survival status of the second node according to the received survival information of the second node includes the following two situations:
  • the first node monitors the survival status of the second node according to the first time interval between the survival information of the second node that is received by the first node and the current survival information of the second node. ;
  • the first node monitors the survival status of the second node according to a second time interval between the last node generated survival information and the second node generating the survival information.
  • the first node monitoring the survival status of the second node according to the survival information of the receiving the second node includes the following situations:
  • the first node determines that the second node is in a normal state
  • the first node determines that the second node is in an abnormal state
  • the first node determines that the second node is in an offline state
  • the survival state is an abnormal state
  • the second node When the first time is greater than or equal to the first threshold, and the second node is in the normal state in the previous monitoring period, it is determined whether the first time is greater than the third threshold, and when the determination result is yes, the second node is determined.
  • the survival status is offline.
  • the third threshold is greater than the second threshold and greater than the first threshold.
  • the first threshold is 2s
  • the second threshold is 1s
  • the third threshold is 10s.
  • the first node monitoring the survival status of the second node according to the survival information of the receiving the second node includes the following situations:
  • the first node determines that the second node is in a normal state
  • the first node determines that the survival state of the second node is an offline state.
  • the method further includes: the first node receives the survival information sent by the second node. At the same time, the first node also sends the survival information to the second node.
  • the central node is any one of the unified networks, and may be, but is not limited to, a master node or a gateway node in the network, where the central node is determined by one of the following methods: a preset relationship calculation, a network or User specified.
  • a node such as a first node, a second node, a third node, etc., may be, but is not limited to, the following entities or software: a terminal; a gateway.
  • a device and a system for monitoring the survival state of the node are provided, which are used to implement the foregoing embodiments and preferred embodiments, and are not described again.
  • the term "module” may implement a combination of at least one of software and hardware of a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of an apparatus for monitoring a node survival state according to an embodiment of the present disclosure. As shown in FIG. 3, applied to a first node, the apparatus includes:
  • the monitoring module 30 is configured to monitor a survival state of the second node, where the first node and the second node are mutually cooperative nodes;
  • the sending module 32 is configured to send, to the central node, a notification message indicating that the second node is offline when the survival state indicates that the second node is offline.
  • the device includes: a first node 40, a second node 42, a central node 44;
  • the first node 40 includes:
  • the monitoring module 402 is configured to monitor a survival state of the second node, where the first node and the second node are mutually cooperative nodes;
  • the sending module 404 is configured to send, to the central node, a notification message indicating that the second node is offline when the survival state indicates that the second node is offline;
  • the central node 44 includes:
  • a determining module 442 configured to determine an offline state of the second node after receiving the notification message
  • the management module 444 is configured to adjust a collaborative relationship of the governed nodes according to a current topology state of at least one of the first node and the second node.
  • the second node 42 in this embodiment has the same function as the first node 40, and the same operation can be performed.
  • the foregoing description is only made from the first node side, and the second node is similar, and details are not described herein again.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • This embodiment describes the purpose of the survival monitoring between the coordinated nodes, that is, the offline node is discovered in time, and the central node can timely process the network topology change to avoid a node losing the cooperative node for a long time.
  • This embodiment describes a rule for judging the survival of a partner between the cooperative nodes, that is, if the survival information is not received after a certain period of time, the other party is determined to be offline.
  • Embodiments of the present disclosure also provide a rule for a central node to determine whether a coordination relationship needs to be adjusted. That is, if any of the cooperative nodes of the offline node has no other surviving cooperative nodes, the central node determines that the collaborative relationship of the governed nodes needs to be adjusted.
  • each pair of cooperative nodes monitors each other according to a node survival monitoring method embodiment. If any node detects that its coordinated node is offline, the node reports to the central node. In the offline situation of the cooperative node, according to the steps in the embodiment of the offline node processing method, whether or not to re-select the coordinated node is determined according to whether the coordinated node of the offline node has a cooperative node that is still alive.
  • This embodiment is applicable to a network in which a central node and a cooperative node relationship have been determined.
  • Each node may have 0 to 2 cooperative nodes, and the cooperative nodes send survival information to each other to monitor the survival status of the other party.
  • the central node receives the coordinated node offline message sent by any node in the network and processes it.
  • This embodiment provides a method for monitoring node survival.
  • the offline device can be discovered in time, so that the central node can process the offline device in time.
  • the node survival information contains the following contents:
  • t Define t as the time interval for generating and transmitting survival information when the node is working normally.
  • the time interval needs to be mutually agreed between the cooperative nodes according to network conditions and their own conditions after the collaborative node selection ends. This time interval can be different between different pairs of cooperative nodes in the network.
  • FIG. 5 is a schematic diagram of a process for sending node survival information according to the embodiment, which is a monitoring process between any pair of coordinated nodes in the network, and all the cooperative nodes in the network need to perform this process.
  • Node m and node n are mutually cooperative nodes, including:
  • Step S101 The node m generates survival information.
  • Step S102 The node m sends the survival information to the node n.
  • Step S103 The node n waits for the survival information sent by the receiving node m. If the survival information is received within 2t, and the received survival information, the interval between the time when the last generation of the survival information is generated and the time when the survival information is generated is t, then node n determines that node m is working properly;
  • Step S104 The node n waits for the survival information sent by the node m. If the survival information is received within 2t, and the received survival information, the time interval between the last generation of the survival information and the current generation of the survival information is greater than t. Then, node n judges that there is an abnormality in the operation of node m.
  • Step S105 The node n waits for the survival information sent by the receiving node m. If the survival information is not received within 2t, and the node n has received the survival information of the node m last time, it has been determined that the node m has an abnormal operation, and the node n determines Node m is an offline node;
  • Step S106 Node n waits for the survival information sent by the node m. If the survival information is not received within 2t, and the node n last receives the survival information of the node m, it is determined that the node m is working normally, then step S107 is performed;
  • Step S107 The node n waits for the survival information sent by the receiving node m. If the survival information is received within 10t, it is determined that the node m runs abnormally; if the survival information is not received within 10t, the node n determines that the node m is offline. node.
  • the survival information may not include the two pieces of information. Then the node survival monitoring embodiment steps become:
  • Step S301 Node m generates survival information.
  • Step S302 the node m sends the survival information to the node n;
  • Step S303 Node n waits for the survival information sent by the receiving node m. If the survival information is received within 2t, the node n determines that the node m works normally;
  • Step S304 The node n waits for the survival information sent by the node m. If the survival information is not received within 2t, the node n determines that the node m is an offline node.
  • the above process is only a one-way process for the node n to monitor the node m, and the same process node m should be used to monitor the node n so that the monitoring is bidirectional.
  • FIG. 6 is a schematic flowchart of the processing of the offline node by the central node provided by the embodiment, and the steps required by the node n and the network central node include:
  • Step S201 The node n reports the node m offline message to the central node.
  • Step S202 After receiving the offline message of the node m, the central node attempts to communicate with the node m, and if it is confirmed that the node m is offline, step S203 is performed;
  • Step S203 If the node n has other surviving cooperating nodes, and the node m does not have other surviving cooperating nodes, the central node does not operate; if the node n has other surviving cooperating nodes, and another cooperating node of the node m also exists For other surviving coordinating nodes, the central node does not operate; if node n has no other surviving cooperating node or another cooperating node of node m does not have other surviving cooperating nodes, the central node judges the network topology change and re-does all nodes in the network. Collaborative node selection.
  • a cooperative node survival monitoring method when an abnormality occurs in a node or a link in the network, the offline node can be monitored and processed in a timely manner, thereby improving the response speed of the network to the node abnormality.
  • the node survival monitoring method embodiment can timely detect whether the coordinated node is offline, so that the offline node processing method embodiment can be executed in time.
  • the offline node processing method embodiment can respond to network topology changes brought by offline nodes in time, so that the central node can select new cooperative nodes for all affected nodes most quickly.
  • the application scenario of this embodiment includes but is not limited to, for example, in a smart grid, the network period collects data in each gateway in the power grid.
  • a network failure may be caused by a gateway failure or a failure of a power supply device connected to the gateway.
  • the power supply equipment fails, if the problem cannot be detected early, it may cause cascading failure.
  • the faulty gateway cannot report the information in time, and needs to wait until the next data collection to discover the problem.
  • the discovery and reporting mechanism of the collaborative node involved in this embodiment will facilitate early detection of the problem. In the agricultural Internet of Things with a large coverage, after a node fails, it is difficult to be discovered, and the failure of some key nodes may lead to network isolation. Therefore, it is necessary to use the method provided by the present disclosure to utilize the collaborative node to determine the survival information, and report to the management center in time for further processing.
  • Embodiments of the present disclosure also provide a storage medium.
  • the storage medium may be configured to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs monitoring the survival state of the second node according to the stored program code in the storage medium, where the first node and the second node are mutually cooperative nodes;
  • the processor is configured to send, according to the stored program code in the storage medium, that the second node is offline when the survival state is used to indicate that the second node is offline. Notification message.
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.
  • the present disclosure is applicable to the field of communication, and is used for mutual monitoring between nodes and sent to a central node to solve the technical problem of slow response when monitoring subordinate nodes through a server in the related art, and to improve the response speed of the network to node anomalies.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供了一种监测节点存活状态的方法、装置及系统，其中，该方法包括：第一节点监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；在所述存活状态表征所述第二节点离线时，所述第一节点向中心节点发送用于指示所述第二节点已经离线的通知消息。通过本发明，解决了相关技术中通过服务器监测下属节点时响应较慢的技术问题。

Description

监测节点存活状态的方法、装置及系统 技术领域
本公开涉及通信领域，具体而言，涉及一种监测节点存活状态的方法、装置及系统。
背景技术
在相关技术中，都是使用服务器监测下属节点的存活情况，这种方式对服务器带宽及计算存储能力都有较高要求，且通常响应较慢。因此相关技术中的节点存活监测技术不适用于中心节点带宽及计算存储能力较低，且需要在协同节点离线后及时响应的情况。
针对相关技术中存在的上述问题，目前尚未发现有效的解决方案。
发明内容
本公开实施例提供了一种监测节点存活状态的方法、装置及系统，以至少解决相关技术中通过服务器监测下属节点时响应较慢的技术问题。
根据本公开的一个实施例，提供了一种监测节点存活状态的方法，包括：第一节点监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；在所述存活状态表征所述第二节点离线时，所述第一节点向中心节点发送用于指示所述第二节点已经离线的通知消息。
可选的，在所述第一节点向中心节点发送用于指示所述第二节点已经离线的通知消息之后，所述方法还包括：所述中心节点确定所述第二节点的离线状态；所述中心节点根据所述第一节点和所述第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系。
可选的，所述中心节点确定所述第二节点的离线状态包括：所述中心节点与所述第二节点进行尝试通信；在所述尝试通信失败时，所述中心节点确定所述第二节点的当前状态为所述离线状态。
可选的，所述中心节点根据所述第一节点的当前拓扑状态调整所辖节点的协同关系包括以下之一：在所述第一节点存在其他存活的协同节点时，所述中心节点保持所辖节点的协同关系；在所述第一节点不存在其他存活的协同节点时，所述中心节点重新为所辖节点选择协同节点。
可选的，所述中心节点根据所述第一节点和所述第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系包括以下之一：在所述第一节点存在其他存活的协同节点，且第二节点不存在其他存活的协同节点时，所述中心节点保持所辖节点的协同关系；在所述第一节点存在其他存活的协同节点，且第三节点存在其他存活的协同节点时，所述中心节点保持所辖节点的协同关系；在所述第一节点不存在其他存活的协同节点，或，所述第三节点不存在其他存活的协同节点时，所述中心节点重新为所辖节点选择协同节点；其中，所述第三节点为所述第二节点的协同节点。
可选的，在向中心节点发送用于指示所述第二节点已经离线的通知消息之前，所述方法还包括：所述第一节点根据所述存活状态确定所述第二节点的当前状态为离线状态。
可选的，第一节点监测第二节点的存活状态包括：所述第一节点根据接收到的所述第二节点的存活信息监测所述第二节点的存活状态。
可选的，所述第一节点根据接收到的所述第二节点的存活信息监测所述第二节点的存活状态包括以下之一：所述第一节点根据所述第一节点上次接收到所述第二节点的存活信息与本次接收到所述第二节点存活信息所间隔的第一时间监测所述第二节点的存活状态；所述第一节点根据所述第二节点上次生成存活信息与所述第二节点本次生成存活信息所间隔的第二时间监测所述第二节点的存活状态。
可选的，所述第一节点根据接收所述第二节点的存活信息监测所述第二节点的存活状态包括以下之一：在所述第一时间小于或等于第一阈值，且所述第二时间小于或等于第二阈值时，所述第一节点确定所述第二节点的存活状态为正常状态；在所述第一时间小于或等于所述第一阈值，且所述第二时间大于或等于所述第二阈值时，所述第一节点确定所述第二节点的存活状态为异常状态；在所述第一时间大于或等于所述第一阈值，且所述第二节点在上一个监测周期的存活状态为异常状态时，所述第一节点确定第二节点的存活状态为离线状态；在所述第一时间大于或等于所述第一阈值，且所述第二节点在上一个监测周期的存活状态为正常状态时，判断所述第一时间是否大于第三阈值，在判断结果为否时，确定所述第二节点的存活状态为异常状态；在所述第一时间大于或等于所述第一阈值，且所述第二节点在上一个监测周期的存活状态为正常状态时，判断所述第一时间是否大于第三阈值，在判断结果为是时，确定所述第二节点的存活状态为离线状态。
可选的，所述第三阈值大于所述第二阈值和所述第一阈值。
可选的，所述第一节点根据接收所述第二节点的存活信息监测所述第二节点的存活状态包括以下之一：在所述第一时间小于或等于第一阈值时，所述第一节点确定所述第二节点的存活状态为正常状态；在所述第一时间大于或等于所述第一阈值时，所述第一节点确定所述第二节点的存活状态为离线状态。
可选的，所述方法还包括：所述第一节点接收所述第二节点发送的存活信息。
可选的，所述中心节点为同一网络中的任一第四节点。
可选的，所述中心节点通过以下方式之一确定：预设关系计算，网络或用户指定。
可选的，所述节点包括以下之一：终端；网关。
根据本公开的另一个实施例，提供了一种监测节点存活状态的装置，应用在第一节点，包括：监测模块，设置为监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；发送模块，设置为在所述存活状态表征所述第二节点离线时，向中心节点发送用于指示所述第二节点已经离线的通知消息。
根据本公开的又一个实施例，提供了一种监测节点存活状态的系统，包括：第一节点，第二节点，中心节点；所述第一节点包括：监测模块，设置为监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；发送模块，设置为在所述存活状态表征所 述第二节点离线时，向中心节点发送用于指示所述第二节点已经离线的通知消息；所述中心节点包括：确定模块，设置为在接收到所述通知消息后，确定所述第二节点的离线状态；管理模块，设置为根据所述第一节点和所述第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系。
根据本公开的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；
在所述存活状态表征所述第二节点离线时，向中心节点发送用于指示所述第二节点已经离线的通知消息。
通过本公开，第一节点监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；在所述存活状态表征所述第二节点离线时，所述第一节点向中心节点发送用于指示所述第二节点已经离线的通知消息。通过节点间的相互监测并发送到中心节点，解决了相关技术中通过服务器监测下属节点时响应较慢的技术问题，提高了网络对节点异常的反应速度。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开实施例的网络构架图；
图2是根据本公开实施例的监测节点存活状态的方法流程图；
图3是根据本公开实施例的监测节点存活状态的装置的结构框图；
图4是根据本公开实施例的监测节点存活状态的系统的结构框图；
图5为本实施例提供的节点存活信息发送流程示意图；
图6为本实施例提供的中心节点处理离线节点的流程示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例可以运行于图1所示的网络架构上，图1是本公开实施例的网络构架图，如图1所示，该网络架构包括：中心节点、中心节点所管辖的多个节点，如，节点1，节点2等，节点间存在协同关系。
在本实施例中提供了一种运行于上述网络架构的监测节点存活状态的方法，图2是根据本公开实施例的监测节点存活状态的方法流程图，如图2所示，该流程包括如下步骤：
步骤S202，第一节点监测第二节点的存活状态，其中，第一节点与第二节点互为协同节点；
步骤S204，在存活状态表征第二节点离线时，第一节点向中心节点发送用于指示第二节点已经离线的通知消息。
通过上述步骤，第一节点监测第二节点的存活状态，其中，第一节点与第二节点互为协同节点；在存活状态表征第二节点离线时，第一节点向中心节点发送用于指示第二节点已经离线的通知消息。通过节点间的相互监测并发送到中心节点，解决了相关技术中通过服务器监测下属节点时响应较慢的技术问题，提高了网络对节点异常的反应速度。
可选地，在第一节点向中心节点发送用于指示第二节点已经离线的通知消息之后，方法还包括：
S11，中心节点确定第二节点的离线状态；
S12，中心节点根据第一节点和第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系。
在本实施例中，中心节点确定第二节点的离线状态包括：
S21，中心节点与第二节点进行尝试通信；
S22，在尝试通信失败时，中心节点确定第二节点的当前状态为离线状态。
在本实施例中，中心节点根据第一节点的当前拓扑状态调整所辖节点的协同关系包括以下至少之一：
在第一节点存在其他存活的协同节点时，即除了第二节点之外第一节点还有其他协同节点，中心节点保持所辖节点的协同关系；
在第一节点不存在其他存活的协同节点时，中心节点重新为所辖节点选择协同节点。
在根据本实施例的可选实施方式中，中心节点根据第一节点和第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系包括以下情况：
在第一节点存在其他存活的协同节点，且第二节点不存在其他存活的协同节点时，中心节点保持所辖节点的协同关系；
在第一节点存在其他存活的协同节点，且第三节点存在其他存活的协同节点时，中心节点保持所辖节点的协同关系；
在第一节点不存在其他存活的协同节点，或，第三节点不存在其他存活的协同节点时，中心节点重新为所辖节点选择协同节点；其中，第三节点为第二节点的协同节点。
可选地，在向中心节点发送用于指示第二节点已经离线的通知消息之前，方法还包括：第一节点根据存活状态确定第二节点的当前状态为离线状态。
可选地，第一节点监测第二节点的存活状态包括：第一节点根据接收第二节点的存活信息监测第二节点的存活状态。该存活信息包括接收的时间信息和生成的时间信息。
具体的，所述第一节点根据接收到的所述第二节点的存活信息监测所述第二节点的存活状态包括以下两种情形：
所述第一节点根据所述第一节点上次接收到所述第二节点的存活信息与本次接收到所 述第二节点存活信息所间隔的第一时间监测所述第二节点的存活状态；
所述第一节点根据所述第二节点上次生成存活信息与所述第二节点本次生成存活信息所间隔的第二时间监测所述第二节点的存活状态。
在根据本实施例的可选实施方式中，第一节点根据接收第二节点的存活信息监测第二节点的存活状态包括以下情形：
在第一时间小于或等于第一阈值，且第二时间小于或等于第二阈值时，第一节点确定第二节点的存活状态为正常状态；
在第一时间小于或等于第一阈值，且第二时间大于或等于第二阈值时，第一节点确定第二节点的存活状态为异常状态；
在第一时间大于或等于第一阈值，且第二节点在上一个监测周期的存活状态为异常状态时，第一节点确定断第二节点的存活状态为离线状态；
在第一时间大于或等于第一阈值，且第二节点在上一个监测周期的存活状态为正常状态时，判断第一时间是否大于第三阈值，在判断结果为否时，确定第二节点的存活状态为异常状态；
在第一时间大于或等于第一阈值，且第二节点在上一个监测周期的存活状态为正常状态时，判断第一时间是否大于第三阈值，在判断结果为是时，确定第二节点的存活状态为离线状态。
可选的，第三阈值大于第二阈值，同时大于第一阈值，如，第一阈值为2s，第二阈值为1s，第三阈值为10s。
在根据本实施例的另一个可选实施方式中，第一节点根据接收第二节点的存活信息监测第二节点的存活状态包括以下情形：
在第一时间小于或等于第一阈值时，第一节点确定第二节点的存活状态为正常状态；
在第一时间大于或等于第一阈值时，第一节点确定第二节点的存活状态为离线状态。
可选的，方法还包括：第一节点接收第二节点发送的存活信息。同时，第一节点也向第二节点发送的存活信息。
在本实施例中，中心节点为统一网络中的任意一个节点，可以但不限于为网络中的主控节点或网关节点，其中，中心节点通过以下方式之一确定：预设关系计算，网络或用户指定。
在本实施例中，节点，如第一节点，第二节点，第三节点等，可以但不限于为以下实体或软件：终端；网关。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种监测节点存活状态的装置、系统，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和硬件其中至少之一的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本公开实施例的监测节点存活状态的装置的结构框图，如图3所示，应用在第一节点，该装置包括：
监测模块30，用于监测第二节点的存活状态，其中，第一节点与第二节点互为协同节点；
发送模块32，用于在存活状态表征第二节点离线时，向中心节点发送用于指示第二节点已经离线的通知消息。
图4是根据本公开实施例的监测节点存活状态的系统的结构框图，如图4所示，该装置包括：第一节点40，第二节点42，中心节点44；
第一节点40包括：
监测模块402，用于监测第二节点的存活状态，其中，第一节点与第二节点互为协同节点；
发送模块404，用于在存活状态表征第二节点离线时，向中心节点发送用于指示第二节点已经离线的通知消息；
中心节点44包括：
确定模块442，用于在接收到通知消息后，确定第二节点的离线状态；
管理模块444，用于根据所述第一节点和所述第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系。
本实施例中的第二节点42与第一节点40具备相同的功能，可以执行相同的操作，上述仅从第一节点侧进行了说明，第二节点类似，在此不再赘述。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本实施例是本公开的可选实施例，用于结合具体的实例对本申请的方案进行详细说明：
本实施例描述了协同节点间存活监测的目的，即及时发现离线节点，中心节点能够及时处理网络拓扑变更的情况避免某节点长时间失去协同节点。
本实施例描述了协同节点间判断对方存活的规则，即超过一定时间未收到存活信息则判定对方为离线。本公开还实施例了中心节点判断是否需要调整协同关系的规则。即离线节点的所有协同节点中只要有任一节点没有其他存活的协同节点，则中心节点判定需要调整所辖节点的协同关系。
在一个中心节点及协同节点关系已经确定的网络中，首先每对协同节点之间根据节点存活监测方法实施例相互监测，如果任意节点监测到其协同节点已经离线，则该节点向中心节点报告其协同节点离线情况，按照离线节点处理方法实施例中的步骤，根据离线节点的协同 节点是否均有仍然存活的协同节点来决定是否重新进行协同节点选择。
本实施例适用于一个中心节点及协同节点关系已经确定的网络中。其中，每个节点可以有0～2个协同节点，协同节点间通过互相发送存活信息监测对方存活状态。中心节点接收网络中任意节点发来的协同节点离线消息并进行处理。
本实施例包括：
节点存活监测方法实施例
本实施例提供了一种节点存活监测方法，通过监测协同节点的存活情况可以及时发现已离线设备，以便于中心节点能及时对离线设备进行处理。
节点存活信息包含内容如下：
1.节点上次生成存活信息的时间
2.节点本次生成存活信息的时间
定义t为节点正常工作时生成及发送存活信息的时间间隔。该时间间隔需要在协同节点选择结束后协同节点间根据网络条件及自身条件交互商定。网络中不同对协同节点间该时间间隔可以不同。
图5为本实施例提供的节点存活信息发送流程示意图，其为网络中任意一对协同节点间的监测流程，网络中所有协同节点间均需要进行此流程。节点m与节点n互为协同节点，包括：
步骤S101：节点m生成存活信息；
步骤S102：节点m向节点n发送存活信息；
步骤S103：节点n等待接收节点m发来的存活信息，若在2t内收到存活信息，且收到的存活信息中，上次生成存活信息的时间与本次生成存活信息的时间的间隔为t，则节点n判断节点m工作正常；
步骤S104：节点n等待接收节点m发来的存活信息，若在2t内收到存活信息，且收到的存活信息中，上次生成存活信息的时间与本次生成存活信息的时间间隔大于t，则节点n判断节点m运行存在异常。
步骤S105：节点n等待接收节点m发来的存活信息，若在2t内未收到存活信息，且节点n上次接收到节点m的存活信息时已判断节点m存在运行异常，则节点n判断节点m为离线节点；
步骤S106：节点n等待接收节点m发来的存活信息，若在2t内未收到存活信息，且节点n上次接收到节点m的存活信息时判断节点m工作正常，则执行步骤S107；
步骤S107：节点n等待接收节点m发来的存活信息，若在10t内收到存活信息，则判断节点m运行存在异常；若在10t内未收到存活信息，则节点n判断节点m为离线节点。
作为一个可选的方案，在节点计算存储能力较弱，无法保存节点上次生成存活信息的时间及本次存活信息的时间并生成存活信息时，存活信息中可以不包含这两项信息。则节点存活监测实施例步骤变为：
步骤S301：节点m生成存活信息；
步骤S302：节点m向节点n发送存活信息；
步骤S303：节点n等待接收节点m发来的存活信息，若在2t内收到存活信息，则节点n判断节点m工作正常；
步骤S304：节点n等待接收节点m发来的存活信息，若在2t内未收到存活信息，则节点n判断节点m为离线节点。
上述流程仅为节点n监测节点m的单向流程，应有相同流程节点m监测节点n使监测为双向。
离线节点处理方法实施例
本实施例需要在节点存活监测方法实施例监测到离线节点后执行。节点n通过节点存活监测方法检测到其协同节点m离线后，图6为本实施例提供的中心节点处理离线节点的流程示意图，节点n及网络中心节点需要进行步骤包括：
步骤S201：节点n向中心节点上报节点m离线消息；
步骤S202：中心节点接收到节点m离线消息后，尝试与节点m通信，若确认节点m已经离线，则执行步骤S203；
步骤S203：若节点n还有其他存活协同节点，且节点m不存在其他存活协同节点，则中心节点不进行操作；若节点n还有其他存活协同节点，且节点m的另一个协同节点也存在其他存活协同节点，则中心节点不进行操作；若节点n无其他存活协同节点或节点m的另一个协同节点不存在其他存活协同节点，则中心节点判断网络拓扑变更，重新为网络中所有节点进行协同节点选择。
根据本实施例提出的一种协同节点存活监测方法。依据本监测方法，在网络中某一节点或链路出现异常时，能更及时的监测到离线的节点并进行处理，提高了网络对节点异常的反应速度。通过节点存活监测方法实施例能及时监测到协同节点是否离线，使离线节点处理方法实施例能够及时地执行。通过离线节点处理方法实施例能够及时响应离线节点带来的网络拓扑变更，使中心节点能最迅速的为所有受到影响的节点选择新的协同节点。
本实施例的应用场景包括但不限，如在智能电网中，网络周期收集电网中各个网关中的数据。网络故障可能是因为网关故障或者是网关连接的供电设备发生故障造成的。尤其是供电设备发生故障时，如果无法及早发现问题，可能导致级联故障。而故障网关无法及时汇报信息，需要等到下一次数据收集时才能够发现这个问题。而本实施例所涉及的协同节点的发现和汇报机制将利于及早发现问题。而在覆盖范围较大的农业物联网中，节点发生故障后，很难被发现，同时某些关键节点的故障可能导致网络隔离。因此，需要通过本公开提供的方法，利用协同节点判断存活信息，并及时向管理中心汇报，以便进行进一步的处理。
实施例4
本公开的实施例还提供了一种存储介质。应用在第一节点上，可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；
S2，在所述存活状态表征所述第二节点离线时，向中心节点发送用于指示所述第二节点 已经离线的通知消息。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行在所述存活状态表征所述第二节点离线时，向中心节点发送用于指示所述第二节点已经离线的通知消息。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。
工业实用性
本公开适用于通信领域，用以通过节点间的相互监测并发送到中心节点，解决相关技术中通过服务器监测下属节点时响应较慢的技术问题，提高网络对节点异常的反应速度。

Claims (19)

  1. 一种监测节点存活状态的方法，包括：
    第一节点监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；
    在所述存活状态表征所述第二节点离线时，所述第一节点向中心节点发送用于指示所述第二节点已经离线的通知消息。
  2. 根据权利要求1所述的方法，其中，在所述第一节点向中心节点发送用于指示所述第二节点已经离线的通知消息之后，所述方法还包括：
    所述中心节点确定所述第二节点的离线状态；
    所述中心节点根据所述第一节点和所述第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系。
  3. 根据权利要求2所述的方法，其中，所述中心节点确定所述第二节点的离线状态包括：
    所述中心节点与所述第二节点进行尝试通信；
    在所述尝试通信失败时，所述中心节点确定所述第二节点的当前状态为所述离线状态。
  4. 根据权利要求2所述的方法，其中，所述中心节点根据所述第一节点的当前拓扑状态调整所辖节点的协同关系包括以下之一：
    在所述第一节点存在其他存活的协同节点时，所述中心节点保持所辖节点的协同关系；
    在所述第一节点不存在其他存活的协同节点时，所述中心节点重新为所辖节点选择协同节点。
  5. 根据权利要求2所述的方法，其中，所述中心节点根据所述第一节点和所述第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系包括以下之一：
    在所述第一节点存在其他存活的协同节点，且第二节点不存在其他存活的协同节点时，所述中心节点保持所辖节点的协同关系；
    在所述第一节点存在其他存活的协同节点，且第三节点存在其他存活的协同节点时，所述中心节点保持所辖节点的协同关系；
    在所述第一节点不存在其他存活的协同节点，或，所述第三节点不存在其他存活的协同节点时，所述中心节点重新为所辖节点选择协同节点；
    其中，所述第三节点为所述第二节点的协同节点。
  6. 根据权利要求1所述的方法，其中，在向中心节点发送用于指示所述第二节点已经离线的通知消息之前，所述方法还包括：
    所述第一节点根据所述存活状态确定所述第二节点的当前状态为离线状态。
  7. 根据权利要求1所述的方法，其中，第一节点监测第二节点的存活状态包括：
    所述第一节点根据接收到的所述第二节点的存活信息监测所述第二节点的存活状态。
  8. 根据权利要求7所述的方法，其中，所述第一节点根据接收到的所述第二节点的存活信息监测所述第二节点的存活状态包括以下之一：
    所述第一节点根据所述第一节点上次接收到所述第二节点的存活信息与本次接收到所述第二节点存活信息所间隔的第一时间监测所述第二节点的存活状态；
    所述第一节点根据所述第二节点上次生成存活信息与所述第二节点本次生成存活信息所间隔的第二时间监测所述第二节点的存活状态。
  9. 根据权利要求8所述的方法，其中，所述第一节点根据接收所述第二节点的存活信息监测所述第二节点的存活状态包括以下之一：
    在所述第一时间小于或等于第一阈值，且所述第二时间小于或等于第二阈值时，所述第一节点确定所述第二节点的存活状态为正常状态；
    在所述第一时间小于或等于所述第一阈值，且所述第二时间大于或等于所述第二阈值时，所述第一节点确定所述第二节点的存活状态为异常状态；
    在所述第一时间大于或等于所述第一阈值，且所述第二节点在上一个监测周期的存活状态为异常状态时，所述第一节点确定第二节点的存活状态为离线状态；
    在所述第一时间大于或等于所述第一阈值，且所述第二节点在上一个监测周期的存活状态为正常状态时，判断所述第一时间是否大于第三阈值，在判断结果为否时，确定所述第二节点的存活状态为异常状态；
    在所述第一时间大于或等于所述第一阈值，且所述第二节点在上一个监测周期的存活状态为正常状态时，判断所述第一时间是否大于第三阈值，在判断结果为是时，确定所述第二节点的存活状态为离线状态。
  10. 根据权利要求9所述的方法，其中，所述第三阈值大于所述第二阈值和所述第一阈值。
  11. 根据权利要求8所述的方法，其中，所述第一节点根据接收所述第二节点的存活信息监测所述第二节点的存活状态包括以下之一：
    在所述第一时间小于或等于第一阈值时，所述第一节点确定所述第二节点的存活状态为正常状态；
    在所述第一时间大于或等于所述第一阈值时，所述第一节点确定所述第二节点的存活状态为离线状态。
  12. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第一节点接收所述第二节点发送的存活信息。
  13. 根据权利要求1至12任一项所述的方法，其中，所述中心节点为同一网络中的任一第四节点。
  14. 根据权利要求13所述的方法，其中，所述中心节点通过以下方式之一确定：预设关系计算，网络或用户指定。
  15. 根据权利要求1至12任一项所述的方法，其中，所述节点包括以下之一：终端；网关。
  16. 一种监测节点存活状态的装置，应用在第一节点，包括：
    监测模块，设置为监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；
    发送模块，设置为在所述存活状态表征所述第二节点离线时，向中心节点发送用于指示所述第二节点已经离线的通知消息。
  17. 一种监测节点存活状态的系统，包括：
    第一节点，第二节点，中心节点；其中
    所述第一节点包括：
    监测模块，设置为监测第二节点的存活状态，其中，所述第一节点与所述第二节点互为协同节点；
    发送模块，设置为在所述存活状态表征所述第二节点离线时，向中心节点发送用于指示所述第二节点已经离线的通知消息；
    所述中心节点包括：
    确定模块，设置为在接收到所述通知消息后，确定所述第二节点的离线状态；
    管理模块，设置为根据所述第一节点和所述第二节点其中至少之一的当前拓扑状态调整所辖节点的协同关系。
  18. 一种存储介质，其中，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至15中任一项所述的方法。
  19. 一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行权利要求1至15中任一项所述的方法。
PCT/CN2018/075659 2017-06-30 2018-02-07 监测节点存活状态的方法、装置及系统 WO2019000954A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/627,504 US11212204B2 (en) 2017-06-30 2018-02-07 Method, device and system for monitoring node survival state

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710524175.6 2017-06-30
CN201710524175 2017-06-30
CN201710612472.6 2017-07-25
CN201710612472.6A CN109218126B (zh) 2017-06-30 2017-07-25 监测节点存活状态的方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2019000954A1 true WO2019000954A1 (zh) 2019-01-03

Family

ID=64740979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/075659 WO2019000954A1 (zh) 2017-06-30 2018-02-07 监测节点存活状态的方法、装置及系统

Country Status (2)

Country Link
US (1) US11212204B2 (zh)
WO (1) WO2019000954A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112910981B (zh) * 2021-01-27 2022-07-26 联想(北京)有限公司 一种控制方法及装置
CN116170346A (zh) * 2022-12-27 2023-05-26 天翼云科技有限公司 一种监控方法、装置及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103117901A (zh) * 2013-02-01 2013-05-22 华为技术有限公司 一种分布式心跳检测方法、装置及系统
CN104506357A (zh) * 2014-12-22 2015-04-08 国云科技股份有限公司 一种高可用集群节点管理方法
WO2016192408A1 (zh) * 2015-06-05 2016-12-08 华为技术有限公司 集群系统中节点的故障检测方法和装置
CN106656682A (zh) * 2017-02-27 2017-05-10 网宿科技股份有限公司 集群心跳检测方法、系统及装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060224687A1 (en) * 2005-03-31 2006-10-05 Popkin Laird A Method and apparatus for offline cooperative file distribution using cache nodes
AU2010244945B2 (en) * 2009-05-05 2015-01-22 Absolute Software Corporation Discriminating data protection system
US9419871B2 (en) * 2013-03-15 2016-08-16 Vector Unlimited, LLC Method and system for remotely monitoring device status and internet connectivity on a computer network
US9002991B2 (en) * 2013-04-06 2015-04-07 Miranda Technologies Partnership System and methods for cloud-based media play out
US9424133B2 (en) * 2013-07-10 2016-08-23 Netapp, Inc. Providing an eventually-consistent snapshot of nodes in a storage network
CN104349298B (zh) * 2013-08-09 2019-07-02 中兴通讯股份有限公司 一种网络计费方法、控制器、数据中心及系统
US10977634B2 (en) * 2015-08-11 2021-04-13 Catalina Marketing Corporation Media hub devices with passive monitoring of user devices and targeted media transmission through in-channel transmission or shifted channel transmission
CN106454955B (zh) * 2015-08-12 2019-09-17 电信科学技术研究院 一种资源信息发送、广播方法及装置
JP2019532378A (ja) * 2016-07-27 2019-11-07 ヴェルト アナリティクス オーワイ シングルソースクロスプラットフォームメディア測定装置、デバイス、及び関連方法
US9905118B1 (en) * 2016-08-29 2018-02-27 At&T Digital Life, Inc. Limiting service availability when sensor device is non-operational due to noise floor change
US10425316B2 (en) * 2017-09-29 2019-09-24 Nokia Of America Corporation Heart beat monitoring for broadband access devices and enterprise devices

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103117901A (zh) * 2013-02-01 2013-05-22 华为技术有限公司 一种分布式心跳检测方法、装置及系统
CN104506357A (zh) * 2014-12-22 2015-04-08 国云科技股份有限公司 一种高可用集群节点管理方法
WO2016192408A1 (zh) * 2015-06-05 2016-12-08 华为技术有限公司 集群系统中节点的故障检测方法和装置
CN106656682A (zh) * 2017-02-27 2017-05-10 网宿科技股份有限公司 集群心跳检测方法、系统及装置

Also Published As

Publication number Publication date
US20200169487A1 (en) 2020-05-28
US11212204B2 (en) 2021-12-28

Similar Documents

Publication Publication Date Title
CN109218126B (zh) 监测节点存活状态的方法、装置及系统
KR102072148B1 (ko) 네트워크에서 링크 손실을 처리하기 위한 시스템 및 방법
WO2019061720A1 (zh) 一种数据同步的方法和系统
TWI740210B (zh) 終端設備管理方法及伺服器
US11539609B2 (en) Method and apparatus for reporting power down events in a network node without a backup energy storage device
JP2018531535A6 (ja) ネットワークにおけるリンクロスの処理のためのシステムおよび方法
CN108141369A (zh) 机器对机器装置的操作状态的建立
WO2019000954A1 (zh) 监测节点存活状态的方法、装置及系统
CN113852506A (zh) 一种故障处理方法、装置及电子设备和存储介质
WO2019019607A1 (zh) 数据备份方法、装置及系统
US20140059154A1 (en) Leader Node Appointment
US11101689B2 (en) Systems and methods for providing network connection resiliency in power supply devices
CN111490859A (zh) 一种arq模式的切换方法及装置
WO2023185214A1 (zh) 网络切换方法、节点、电子设备和可读存储介质
CN107566475B (zh) 一种会话故障转移方法及装置
CN102185720A (zh) 一种北向通知管理接口装置及其管理方法
CN111247819B (zh) 设备管理的方法和ble设备
CN110535712B (zh) Bfd参数设置方法、装置、电子设备
US9699215B2 (en) Computer devices and security management device communicationally-connected to the same
US20130083669A1 (en) Fault management traffic reduction in heterogeneous networks
CN110958128B (zh) 告警上报调度方法及装置
CN115408199A (zh) 一种边缘计算节点的容灾处理方法及装置
US20150372894A1 (en) Direct-link quality monitoring method, communications device, and system
US9514303B2 (en) Computer devices and security management device communicationally-connected to the same
JP6022948B2 (ja) 通信ネットワークの制御装置の管理装置及びプログラム

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: 18824126

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: 18824126

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 28/05/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18824126

Country of ref document: EP

Kind code of ref document: A1