WO2019184285A1 - 通信设备、节点的连接方法、存储介质、电子装置 - Google Patents

通信设备、节点的连接方法、存储介质、电子装置 Download PDF

Info

Publication number
WO2019184285A1
WO2019184285A1 PCT/CN2018/107979 CN2018107979W WO2019184285A1 WO 2019184285 A1 WO2019184285 A1 WO 2019184285A1 CN 2018107979 W CN2018107979 W CN 2018107979W WO 2019184285 A1 WO2019184285 A1 WO 2019184285A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
data
coordinated
network
terminal
Prior art date
Application number
PCT/CN2018/107979
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 西安中兴新软件有限责任公司
Priority to EP18911626.2A priority Critical patent/EP3780491A4/en
Priority to US16/982,004 priority patent/US20210021477A1/en
Publication of WO2019184285A1 publication Critical patent/WO2019184285A1/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
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • 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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them

Definitions

  • the present disclosure relates to the field of communications, and in particular to a communication device, a connection method of a node, a storage medium, and an electronic device.
  • a gateway node in a ubiquitous/Internet of Things network collects data of ubiquitous/IoT devices within its scope and periodically uploads the data to an application management center.
  • the upload cycle between the gateway and the application center is usually long. Once the gateway fails, the application center takes a long time to discover the fault.
  • the data collected before the fault occurs may result in the failure to accurately determine the cause of the fault.
  • the smart grid develops a power supply plan and a price adjustment plan by monitoring the power load to ensure the safety, reliability, and economy of the power consumption. Therefore, the safe operation of the grid system is the primary problem that the smart grid needs to solve.
  • the smart grid needs to judge the cause of the fault in time, but because the current smart grid adopts a central structure, the collected data is regularly reported and managed. Center, when there is a problem with a power device, it takes a while to discover the problem. And because the collected data is lost, it will be impossible to determine the cause of the problem.
  • Embodiments of the present disclosure provide a communication device, a connection method of a node, a storage medium, and an electronic device.
  • a communication device comprising: a selection module configured to select a second node; a control module configured to establish and/or dismantle synergy with the second node; and a monitoring module configured to After establishing cooperation with the second node, monitoring the survival status of the second node.
  • a connection method of a node comprising: a first node receiving a coordination node confirmation of a central node, wherein the coordination node confirms a coordination node for indicating allocation; the first node Cooperating with the second node to establish and/or dismantle the collaboration according to the coordination node.
  • a connection method of another node including: receiving, by a second node, a co-establishment request sent by a first node, where the co-establishment request is sent by the first node according to a central node
  • the collaborative node confirms the generated; the second node establishes a collaboration with the first node according to the collaborative establishment request.
  • a method for connecting a node including: the third node determines that it is a central node of the network, where the network includes: a first node, a second node, and the a third node; the third node selects the second node as a coordinated node of the first node; the third node sends a first coordinated node acknowledgement to the first node, where the first coordinated node A confirmation is used to indicate a coordinated node assigned to the first node.
  • a method for connecting a node including: establishing, by a fourth node, a connection with a data platform; after establishing a connection with the data platform, the fourth node establishes a connection with the terminal; The fourth node acquires the data information collected by the terminal, caches the data information locally, and sends the data information to the data platform.
  • a storage medium having stored therein a computer program, wherein the computer program is configured to perform the steps of any one of the method embodiments described above at runtime.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being configured to execute the computer program to perform any of the above The steps in the method embodiments.
  • FIG. 1 is a network architecture diagram of an embodiment of the present disclosure
  • FIG. 2 is a structural block diagram of a communication device in accordance with an embodiment of the present disclosure
  • FIG. 3 is a flowchart 1 of a method of connecting nodes according to an embodiment of the present disclosure
  • FIG. 4 is a second flowchart of a method of connecting nodes according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart 3 of a method of connecting nodes according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart 4 of a method of connecting nodes according to an embodiment of the present disclosure
  • Figure 8 is a flow chart of the connection establishment method of this embodiment.
  • FIG. 1 is a network architecture diagram of an embodiment of the present disclosure.
  • the network architecture includes: a node, a data platform, where the node is functional. Differently divided into common nodes (such as node 1, node 2...node n) and central node, the central node is any node in the network, with all the functions of ordinary nodes, nodes can form a cooperative relationship, and the nodes are connected with the data platform. .
  • a communication device is also provided in this embodiment, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 2 is a structural block diagram of a communication device according to an embodiment of the present disclosure. As shown in FIG. 2, the device includes:
  • the selecting module 20 is configured to select the second node
  • control module 22 configured to establish and/or tear down cooperation with the second node
  • the monitoring module 24 is configured to monitor the survival status of the second node after establishing cooperation with the second node.
  • the selecting module includes: a first selecting unit, configured to determine a central node of the network when the network is formed or when the network topology is changed.
  • the execution body of the foregoing steps may be a communication node, a gateway, or the like, and may be applied to a ubiquitous/Internet of Things application such as a smart home system, a vehicle networking system, a power grid system, a smart city system, etc., but is not limited thereto.
  • the execution entity in this embodiment has the functions of a common node and a central node in the network, and performs corresponding operations according to its own identity in different scenarios, and has corresponding functions.
  • the selecting module further includes: a configuration unit configured to configure encoding information for each node in the network; and a second selecting unit configured to use one or more networks according to the encoding information.
  • the nodes are assigned coordination nodes.
  • the control module includes: a sending unit, configured to receive After the coordination node sent by the central node confirms, the collaborative node selected by the central node sends a collaborative establishment request.
  • the control module includes: a sending unit, configured to send a collaborative establishment request to the second node; and a determining unit, configured to establish a collaboration with the second node after the second node authenticates and authenticates the communication device.
  • the communication device is a coordinated node selected by the central node in the network, and establishes and/or decommissions cooperation with the target gateway according to the received collaborative setup request of the target gateway, and does not receive the coordinated node confirmation sent by the central node.
  • the second node is a cooperative node that actively establishes and/or tears down the collaborative relationship
  • the control module includes: a first confirming unit, configured to: after receiving the collaborative establishment request sent by the second node, determine that the local resource meets the service requirement of the second node , allocating resources for the second node, confirming that the second node establishes cooperation.
  • control module includes: a second confirming unit, configured to locally remove related resources of the second node when performing cooperative node reselection or disconnection, and confirm that the second node is decomposed and coordinated.
  • a second confirming unit configured to locally remove related resources of the second node when performing cooperative node reselection or disconnection, and confirm that the second node is decomposed and coordinated.
  • the monitoring module includes: a monitoring unit, configured to monitor a survival status of the second node according to the received survival information of the second node.
  • the monitoring module further includes: a sending unit, configured to send, to the central node, a notification message indicating that the cooperating node is offline after determining that the current state of the second node is offline.
  • the monitoring module when the communication device is the central node, includes: a determining unit, configured to, after receiving the notification message, attempt to communicate with the second node, and determine, when the communication fails, determine the current state of the second node. The status is offline and instructs the selection module to reassign the coordinating node.
  • the device further includes: a management module, configured to implement access management and data management on the communication device.
  • a management module configured to implement access management and data management on the communication device.
  • the management module includes: an access management unit, configured to: after the communication device is started, initiate a first connection establishment request to the data platform; and the receiving data platform confirms the connection returned by authenticating the communication device; and The network periodically broadcasts the access information, and the second connection establishment request sent by the receiving terminal after receiving the access information; the receiving data platform returns a connection confirmation to the terminal by registering the registration returned after the device registration of the terminal.
  • the terminal includes a sensor, a peripheral device, and the like.
  • the management module further includes: a data management unit, configured to: after establishing cooperation with the second node, receive backup data sent by the second node according to the preset period, and delete locally saved backup data that exceeds the local storage capacity; After the collaboration relationship is interrupted, the backup data of the second node is uploaded to the data platform.
  • a data management unit configured to: after establishing cooperation with the second node, receive backup data sent by the second node according to the preset period, and delete locally saved backup data that exceeds the local storage capacity; After the collaboration relationship is interrupted, the backup data of the second node is uploaded to the data platform.
  • the data management unit is further configured to: after establishing a connection with the data platform, start a data upload timer; when the data upload timer expires, upload the data information collected by the currently stored terminal to the data platform; The node sends an indication for requesting deletion of the backup data of the locally saved communication device, and restarts the data upload timer; and after the connection with the terminal is established, the cached terminal regularly reports the collected data information thereof.
  • 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.
  • FIG. 3 is a flowchart 1 of a method for connecting a node according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes the following steps:
  • Step S302 the first node receives the coordination node confirmation of the central node, where the coordination node confirms the coordination node used to indicate the allocation;
  • Step S304 the first node confirms establishment and/or teardown cooperation with the second node according to the cooperation node.
  • the collaborative node acknowledgement can be a message or message, signaling, and the like.
  • the execution body of the foregoing steps may be a communication node, a gateway, or the like, and may be applied to a ubiquitous/Internet of Things application such as a smart home system, a vehicle networking system, a power grid system, a smart city system, etc., but is not limited thereto.
  • the identity of the first node is a node that actively establishes and/or tears out the coordination (relationship).
  • the first node establishes and/or tears down the collaboration relationship with the second node according to the allocation information (also referred to as: the collaboration node acknowledgement) includes:
  • the first node sends a collaborative establishment request to the second node according to the allocation information.
  • the first node After the second node authenticates and authenticates the first node, the first node establishes a cooperative relationship with the second node.
  • the method further includes: the first node sending the backup data to the second node according to a predetermined period. At the same time, the backup data sent by the second node according to the predetermined period is also received.
  • the method further includes: the first node locally deleting the backup data that has been sent. It can be deleted according to the storage capacity of the node, and the locally saved backup data exceeding the local storage capacity can be deleted until the local storage capacity does not exceed the predetermined capacity.
  • the method further includes:
  • the first node monitors a survival status of the second node.
  • the first node determines, according to the survival status, that the second node is in an offline state or an online state.
  • the method further includes at least one of the following:
  • the first node sends an offline notification message to the central node, where the offline notification message is used to indicate that the second node is offline;
  • the first node sends the locally saved backup data of the second node to the data platform, wherein the data platform is connected to the first node and the second node.
  • FIG. 4 is a second flowchart of a method for connecting nodes according to an embodiment of the present disclosure. As shown in FIG. 4, the process includes the following steps. :
  • Step S402 the second node receives the cooperation establishment request sent by the first node, where the cooperation establishment request is generated by the first node according to the coordination node sent by the central node;
  • Step S404 the second node establishes a cooperative relationship with the first node according to the collaborative establishment request.
  • the execution body of the foregoing steps may be a communication node, a gateway, or the like, and may be applied to a ubiquitous/Internet of Things application such as a smart home system, a vehicle networking system, a power grid system, a smart city system, etc., but is not limited thereto.
  • the identity of the second node is a node that passively establishes a collaboration (relationship) according to the request.
  • the method further includes:
  • the second node authenticates and authenticates the first node.
  • the second node After the second node authenticates and authenticates the first node, the second node determines whether the local resource meets the service requirement of the first node.
  • the second node allocates network resources to the first node when determining that the local resource meets the service requirement of the first node.
  • the method further includes: the second node sending the backup data to the first node according to a predetermined period. Realize mutual backup of data.
  • the method further includes: deleting, by the second node, the backup data that has been sent locally.
  • the method further includes: the second node monitors a survival state of the first node; and the second node determines, according to the survival state, that the first node is offline or online. .
  • the first node determines that the second node is offline according to the survival state, at least one of the following is included:
  • the second node sends an offline notification message to the central node, where the offline notification message is used to indicate that the first node is offline;
  • the second node sends the locally saved backup data of the first node to the data platform, wherein the data platform is connected to the first node and the second node.
  • FIG. 5 is a flowchart 3 of a method for connecting a node according to an embodiment of the present disclosure. As shown in FIG. 5, the process includes the following steps. :
  • Step S502 the third node determines that it is a central node of the network, where the network includes: a first node, a second node, and a third node;
  • Step S504 the third node selects the second node as the coordinated node of the first node
  • Step S506 the third node sends a first coordination node confirmation to the first node, where the first cooperation node confirms the cooperation node used to indicate the first node.
  • the execution body of the foregoing steps may be a communication node, a gateway, or the like, and may be applied to a ubiquitous/Internet of Things application such as a smart home system, a vehicle networking system, a power grid system, a smart city system, etc., but is not limited thereto.
  • the identity of the third node is a central node, and the coordinated node is selected for the target node in the network, and has the function of a common node.
  • the method further includes:
  • the central node receives an offline notification message sent by the first node, where the offline notification message is used to indicate that the second node is offline.
  • the central node attempts to communicate with the second node, and after attempting communication failure, determining that the second node is offline;
  • the central node After determining that the second node is offline, the central node sends the second allocation information to the first node, where the first allocation information is used to indicate the coordinated node allocated for the first node.
  • FIG. 6 is a flowchart 4 of a method for connecting a node according to an embodiment of the present disclosure. As shown in FIG. 6, the process includes the following steps. :
  • Step S602 the fourth node establishes a connection with the data platform
  • Step S604 after establishing a connection with the data platform, the fourth node establishes a connection with the terminal;
  • Step S606 the fourth node acquires the data information collected by the terminal, caches the data information locally, and sends the data information to the data platform.
  • the terminal includes a sensor, a peripheral device, and the like.
  • the execution body of the foregoing steps may be a communication node, a gateway, or the like, and may be applied to a ubiquitous/Internet of Things application such as a smart home system, a vehicle networking system, a power grid system, a smart city system, etc., but is not limited thereto.
  • the identity of the fourth node is any node in the network, including a common node and a central node.
  • the method further includes: the fourth node locally deleting the data information, and requesting the coordinated node of the fourth node to delete the data information locally.
  • establishing, by the fourth node, the connection with the terminal includes:
  • the fourth node broadcasts access information in a local area network, where the access information is used to request the terminal to access the fourth node.
  • the fourth node receives a connection establishment request sent by the terminal, where the connection establishment request carries device information of the terminal.
  • the fourth node establishes a connection with the terminal according to the device information.
  • the fourth node establishes a connection with the terminal according to the device information, including:
  • the fourth node sends the device information to the data platform.
  • the fourth node receives the registration confirmation information fed back by the data platform, where the registration confirmation information is used to indicate that the terminal is registered in the data platform.
  • the fourth node After receiving the registration confirmation information, the fourth node establishes a connection with the terminal.
  • the data is backed up by the collaboration nodes, and when the collaboration node is found to be unable to connect, the collaboration node is reported to the management node to report the fault and the previously collected data is reported.
  • the node device (such as a common node, a central node) includes: a selection module, a monitoring module, a management module, and a control module.
  • the selection module is configured to implement a selection function of the collaborative node, including central node determination, node information coding, and coordinated node assignment function;
  • the monitoring module is configured to implement a monitoring function of the coordinated node, including monitoring a survival state of the coordinated node according to the received survival information;
  • the control module is configured to implement a function of cooperative node access control, including controlling connection establishment and connection removal between the coordinated nodes;
  • the management module is configured to implement a management function of a node, including an access management submodule and a data management submodule; wherein the access management submodule includes management of node access; and the data management submodule includes Collaborative data management.
  • each node needs to upload data information to the data platform.
  • Each node has at most two cooperative nodes, and the cooperative nodes can mutually monitor each other's survival status and back up the other party's data information;
  • the central node is any node in the network (designated, or randomly assigned, or according to a predetermined policy) Selected), with all the functions of a common node, can also assign coordinated nodes to all nodes in the network according to information such as network topology.
  • FIG. 7 is a flowchart of the method for establishing a collaborative manner according to the embodiment.
  • Step S101 When the network is formed or the network topology is changed, the selection module of any gateway acquires the suitability of the gateway and the gateway in the network based on its own node status as the central gateway, and determines the gateway with the highest degree of suitability as the network.
  • Central gateway (corresponding to the third node in the above embodiment);
  • the degree of suitability may be an energy value, a power value, a bandwidth value, a weighted average value, and the like, and the energy value, the power value, and the bandwidth value are the highest.
  • Step S102 The selection module of the central gateway configures coding information for each gateway in the same network
  • the encoding information may be encoding of location information, encoding of application related information.
  • Step S103 The selection module of the central gateway acquires the coding information of the target gateway, and selects a coordinated gateway that meets the preset requirement for the target gateway from the multiple gateways of the same network based on the coding information of the target gateway;
  • Step S104 After receiving the collaborative gateway determining message sent by the central gateway, the selecting module of the target gateway sends a collaborative establishment request to the control module of the collaborative gateway selected by the central gateway.
  • Step S105 After the authentication and authentication of the target gateway, the control module of the collaborative gateway determines that the local resource meets the service requirement of the target gateway, allocates resources for the target gateway, and confirms that the collaboration is established;
  • Step S106 After the collaboration is established, the data management sub-module of the collaborative gateway receives the backup data sent by the target gateway according to the preset period, and deletes the locally saved backup data exceeding the local storage capacity until the local storage capacity is not exceeded;
  • Step S107 The monitoring module of the gateway monitors the survival status of the coordinated node according to the received survival information of the collaborative gateway.
  • Step S108 When the monitoring module of the gateway determines that the current state of the coordinated node is offline, the monitoring module sends a notification message indicating that the collaborative gateway is offline.
  • Step S109 After receiving the notification message, the central gateway attempts to communicate with the collaborative gateway. When the communication fails, the current state of the collaborative gateway is determined to be offline, and the selection module of the central gateway re-synchronizes the gateway.
  • Step S109 After the cooperation is interrupted, the data management module of the gateway uploads the backup data of the collaborative gateway to the data platform;
  • Step S110 When the collaborative gateway reselection or disconnection is required, the data management submodule of the collaborative gateway uploads related data of the collaborative gateway to the data platform; at the same time, the access control module of the collaborative gateway removes the local collaborative gateway thereof. Related resources and confirm the removal of the connection.
  • FIG. 8 is a flowchart of a method for establishing a connection according to this embodiment.
  • Step S201 After the gateway (corresponding to the fourth node in the foregoing embodiment) is started, the access management sub-module of the gateway initiates a connection establishment request to the data platform, where the request message includes device information of the gateway;
  • Step S202 After receiving the request message, the data platform performs authentication authentication on the gateway according to the device information. After the authentication authentication is passed, the data platform returns a connection confirmation to the gateway.
  • Step S203 After establishing the connection, the data management sub-module of the gateway starts a data upload timer.
  • Step S204 The access management submodule of the gateway periodically broadcasts access information in the range of the local area network, and waits for the terminal to access;
  • Step S205 After the terminal is started, the terminal receives the access information, and sends a connection establishment request to the gateway, where the request message includes device information of the terminal.
  • Step S206 After receiving the request message, the access management sub-module of the gateway reports the device information of the terminal to the data platform, and completes the device registration of the terminal on the data platform. After the device registers, the data platform returns a registration confirmation to the gateway.
  • Step S207 After the device registration is completed, the access management submodule of the gateway returns a connection confirmation to the terminal.
  • Step S208 After the connection is established, the terminal periodically reports the collected data information to the data management submodule of the gateway.
  • Step S209 The data management sub-module of the gateway caches the data information reported by the terminal;
  • Step S210 When the data uploading timer expires, the data management sub-module of the gateway uploads the data information collected by all the currently stored terminals to the data platform, and clears the local cache; and sends and deletes the data management sub-module of the collaborative gateway. An indication of the backup data of the locally saved gateway and restart the data upload timer.
  • This embodiment provides a cooperative node device and an application method thereof for explaining the structure of the cooperative node in the prior art, and implements cooperation between the nodes.
  • Embodiments of the present disclosure also provide a storage medium having stored therein a computer program, wherein the computer program is configured to execute the steps of any one of the method embodiments described above.
  • the above storage medium may be configured to store a computer program for performing the following steps:
  • the coordination node of the receiving central node confirms, wherein the coordination node confirms the coordinated node used to indicate the allocation;
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Embodiments of the present disclosure also provide an electronic device including a memory and a processor having a computer program stored therein, the processor being configured to execute a computer program to perform the steps of any one of the method embodiments described above.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • the foregoing processor may be configured to perform the following steps by using a computer program:
  • the coordination node of the receiving central node confirms, wherein the coordination node confirms the coordinated node used to indicate the allocation;
  • 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 to implement a cooperative node in all nodes under the topology network, and implements universal backup and monitoring between nodes, and solves the technical problem that the related technologies cannot perform coordinated monitoring and backup on the nodes, and improves the technical problem. Network stability and failure resistance.

Landscapes

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

Abstract

本申请公开了一种通信设备、节点的连接方法、存储介质、电子装置，其中，该通信设备包括：选择模块，设置为选择第二节点；控制模块，设置为与所述第二节点建立和/或拆除协同；监测模块，设置为在与所述第二节点建立协同后，监测所述第二节点的存活状态。通过本申请，解决了相关技术中不能对节点进行协同监测和备份的技术问题。

Description

通信设备、节点的连接方法、存储介质、电子装置 技术领域
本公开涉及通信领域，具体而言，涉及一种通信设备、节点的连接方法、存储介质、电子装置。
背景技术
随着物联网技术应用范围的逐渐扩大，出现了越来越多地域跨度较大的“泛在/物联网络”。为了覆盖这些跨度较大的泛在网络，通常需要同时使用多个网关进行数据的采集和传输。而另一方面，由于泛在/物联网络环境复杂，终端设备通常无人值守，故存在通信不稳定的情况，为了提高信息传输的可靠性，满足物联网应用的需求，通常需要选择协同节点实现数据的冗余备份和恢复，从而促进网络高效数据传输，实现网络安全性及通信可靠性，满足特定应用需求的核心内容。
相关技术中，通常泛在/物联网中的网关节点会收集其负责范围内泛在/物联网设备的数据，并定期将这些数据上传到应用管理中心。考虑到泛在/物联网的部署环境和规模，通常网关和应用中心之间的上传周期较长。一旦网关发生故障，一方面应用中心需要较长的时间才能发现故障，另外一方面由于丢失故障发生前采集的数据，可能导致无法准确判断故障发生原因。
相关技术中，智能电网通过监测用电负荷，制订供电计划和价格调节方案，确保电力用电的安全性、可靠性和经济性。因此，电网系统的安全运行是智能电网需要解决的首要问题。当电网中某些电力设备因为负荷过重跳闸，或因为自然或人为因素遭到破坏时，智能电网需要及时判断出现故障的原因，但由于目前智能电网采用中心式结构，采集的数据定时上报管理中心，当某个电力设备出现问题时，需要等待一段时间才能发现此问题。且由于采集数据丢失，将无法判断是何种原因导致的问题。
针对相关技术中存在的上述问题，目前尚未发现有效的解决方案。
发明内容
本公开实施例提供了一种通信设备、节点的连接方法、存储介质、电子装置。
根据本公开的一个实施例，提供了一种通信设备，包括：选择模块，设置为选择第二节点；控制模块，设置为与所述第二节点建立和/或拆除协同；监测模块，设置为在与所述第二节点建立协同后，监测所述第二节点的存活状态。
根据本公开的一个实施例，提供了一种节点的连接方法，包括：第一节点接收中心节点的协同节点确认，其中，所述协同节点确认用于指示分配的协同节点；所述第一节点根据所述协同节点确认与第二节点建立和/或拆除协同。
根据本公开的一个实施例，提供了另一种节点的连接方法，包括：第二节点接收第一节 点发送的协同建立请求，其中，所述协同建立请求是所述第一节点根据中心节点发送的协同节点确认生成的；所述第二节点根据所述协同建立请求与所述第一节点建立协同。
根据本公开的一个实施例，提供了又一种节点的连接方法，包括：第三节点确定自身为网络的中心节点，其中，所述网络包括：第一节点，第二节点，以及所述第三节点；所述第三节点选择所述第二节点为所述第一节点的协同节点；所述第三节点向所述第一节点发送第一协同节点确认，其中，所述第一协同节点确认用于指示为所述第一节点分配的协同节点。
根据本公开的一个实施例，提供了又一种节点的连接方法，包括：第四节点与数据平台建立连接；在与所述数据平台建立连接后，所述第四节点与终端建立连接；所述第四节点获取所述终端采集的数据信息，在本地缓存所述数据信息，并将所述数据信息发送至所述数据平台。
根据本公开的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本公开，通过中心节点的分配，并与第二节点建立和/或拆除协同关系，可以实现在拓扑网络下的所有节点都存在协同节点，实现节点间的普遍备份和监测，解决了相关技术中不能对节点进行协同监测和备份的技术问题，提高了网络的稳定性和抗故障能力。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开实施例的网络构架图；
图2是根据本公开实施例的通信设备的结构框图；
图3是根据本公开实施例的节点的连接方法的流程图一；
图4是根据本公开实施例的节点的连接方法的流程图二；
图5是根据本公开实施例的节点的连接方法的流程图三；
图6是根据本公开实施例的节点的连接方法的流程图四；
图7是本实施例协同建立方法的流程图；
图8是本实施例连接建立方法的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例可以运行于图1所示的网络架构上，图1是本公开实施例的网络构架图，如图1所示，该网络架构包括：节点、数据平台，其中，节点根据功能的不同分为普通节点(如节点1，节点2…节点n)和中心节点，中心节点为网络中的任一节点，具有普通节点的所有功能，节点间可以形成协同的关系，节点与数据平台连接。
在本实施例中还提供了一种通信设备，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图2是根据本公开实施例的通信设备的结构框图，如图2所示，该装置包括：
选择模块20，用于选择第二节点；
控制模块22，用于与第二节点建立和/或拆除协同；
监测模块24，用于在与第二节点建立协同后，监测第二节点的存活状态。
可选的，选择模块包括：第一选择单元，用于在组建网络时或者网络拓扑变更时，确定网络的中心节点。
可选地，上述步骤的执行主体可以为通信节点，网关等，可以应用于智能家居系统，车联网系统，电力电网系统，智慧城市系统等泛在/物联网应用中，但不限于此。
本实施例中的执行主体同时具备网络中普通节点和中心节点的功能，在不同的场景中，根据自身的身份执行对应的操作，具备对应的功能。
可选的，在通信设备为中心节点时，选择模块还包括：配置单元，用于为网络中的每个节点配置编码信息；第二选择单元，用于根据编码信息为一个或多个网络中的节点分配协同节点。
在本实施例中，通信设备为网络中中心节点选择的目标节点(目标网关)时，第二节点为被动建立和/或拆除协同关系的协同节点，控制模块包括：发送单元，用于在接收到中心节点发送的协同节点确认后，向中心节点选取的协同节点发送协同建立请求。控制模块包括：发送单元，用于向第二节点发送协同建立请求；确定单元，用于在第二节点对通信设备的认证和鉴权通过后，与第二节点建立协同。
在本实施例中，通信设备为网络中中心节点选择的协同节点，根据接收到的目标网关的协同建立请求与目标网关建立和/或拆除协同，不会收到中心节点发送的协同节点确认，第二节点为主动建立和/或拆除协同关系的协同节点，控制模块包括：第一确认单元，用于在接收到第二节点发送的协同建立请求后，判断本地资源满足第二节点的业务需求，为第二节点分配资源，确认与第二节点建立协同。
可选的，控制模块包括：第二确认单元，用于在进行协同节点重选或者断开连接时，在本地移除第二节点的相关资源，确认与第二节点拆除协同。
可选的，监测模块包括：监测单元，用于根据接收到的第二节点的存活信息监测第二节点的存活状态。监测模块还包括：发送单元，用于在判断第二节点的当前状态为离线时，向 中心节点发送用于指示其协同节点已经离线的通知消息。
在本实施例中，在通信设备为中心节点时，监测模块包括：确定单元，用于在接收到通知消息后，尝试与第二节点进行通信，在尝试通信失败时，确定第二节点的当前状态为离线，并指示选择模块重新分配协同节点。
可选的，设备还包括：管理模块，用于实现对通信设备的接入管理和数据管理。
可选的，管理模块包括：接入管理单元，用于在通信设备启动后，向数据平台发起第一连接建立请求；接收数据平台通过对通信设备的鉴权认证后返回的连接确认；以及在网络中定期广播接入信息，接收终端在接收到接入信息后发送的第二连接建立请求；接收数据平台通过对终端的设备注册后返回的注册确认，向终端返回连接确认。可选的，终端包括传感器，末梢设备等。
可选的，管理模块还包括：数据管理单元，用于在与第二节点建立协同后，接收第二节点根据预设周期发送的备份数据，以及删除超出本地存储容量的本地保存的备份数据；在协同关系中断后，将第二节点的备份数据上传到数据平台。
可选的，数据管理单元还用于：与数据平台建立连接后，启动数据上传定时器；在数据上传定时器到期时，将当前存储的终端采集的数据信息上传给数据平台；向第二节点发送用于请求删除本地保存的通信设备的备份数据的指示，并重启数据上传定时器；以及在与终端建立连接后，缓存终端定期上报的其采集的数据信息。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
在本实施例中提供了一种运行于上述网络架构的节点的连接方法，图3是根据本公开实施例的节点的连接方法的流程图一，如图3所示，该流程包括如下步骤：
步骤S302，第一节点接收中心节点的协同节点确认，其中，协同节点确认用于指示分配的协同节点；
步骤S304，第一节点根据协同节点确认与第二节点建立和/或拆除协同。协同节点确认可以是一种消息或者信息，信令等。
通过上述步骤，通过中心节点的分配，并与第二节点建立和/或拆除协同关系，可以实现在拓扑网络下的所有节点都存在协同节点，实现节点间的普遍备份和监测，解决了相关技术中不能对节点进行协同监测和备份的技术问题，提高了网络的稳定性和抗故障能力。
可选地，上述步骤的执行主体可以为通信节点，网关等，可以应用于智能家居系统，车联网系统，电力电网系统，智慧城市系统等泛在/物联网应用中，但不限于此。本实施例中，第一节点的身份为主动建立和/或拆除协同(关系)的节点。
可选地，第一节点根据分配信息(也可称呼为：协同节点确认)与第二节点建立和/或拆除协同关系包括：
S11，第一节点根据分配信息向第二节点发送协同建立请求；
S12，在第二节点对第一节点的认证和鉴权通过后，第一节点与第二节点建立协同关系。
可选地，在第一节点根据分配信息与第二节点建立协同关系之后，方法还包括：第一节点按照预定周期向第二节点发送备份数据。同时也会接收第二节点按照预定周期发送的备份数据。
可选地，在第一节点按照预定周期向第二节点发送备份数据之后，方法还包括：第一节点在本地删除已经发送的备份数据。可以根据节点的存储能力来删除，删除本地保存的超出本地存储容量的备份数据，直到本地存储容量未超出预定容量为止。
可选地，在第一节点根据分配信息与第二节点建立协同关系之后，还包括：
S21，第一节点监测第二节点的存活状态；
S22，第一节点根据存活状态确定第二节点为离线状态或在线状态。
可选地，在第一节点根据存活状态确定第二节点为离线状态之后，还包括以下至少之一：
第一节点向中心节点发送离线通知消息，其中，离线通知消息用于指示第二节点已经离线；
第一节点将本地保存的第二节点的备份数据发送至数据平台，其中，数据平台与第一节点和第二节点连接。
在本实施例中提供了另一种运行于上述网络架构的节点的连接方法，图4是根据本公开实施例的节点的连接方法的流程图二，如图4所示，该流程包括如下步骤：
步骤S402，第二节点接收第一节点发送的协同建立请求，其中，协同建立请求是第一节点根据中心节点发送的协同节点确认生成的；
步骤S404，第二节点根据协同建立请求与第一节点建立协同关系。
可选地，上述步骤的执行主体可以为通信节点，网关等，可以应用于智能家居系统，车联网系统，电力电网系统，智慧城市系统等泛在/物联网应用中，但不限于此。本实施例中，第二节点的身份为根据请求被动建立协同(关系)的节点。
可选的，在第二节点根据协同建立请求与第一节点建立协同关系之前，还包括：
S31，第二节点对第一节点进行认证和鉴权；
S32，第二节点在对第一节点的认证和鉴权通过后，判断本地资源是否满足第一节点的业务需求；
S33，第二节点在确定本地资源满足第一节点的业务需求时，为第一节点分配网络资源。
可选的，在第二节点根据协同建立请求与第一节点建立协同关系之后，还包括：第二节点按照预定周期向第一节点发送备份数据。实现数据的相互备份。
可选的，在第二节点按照预定周期向第一节点发送备份数据之后，还包括：第二节点在本地删除已经发送的备份数据。
可选的，在第二节点按照预定周期向第一节点发送备份数据之后，还包括：第二节点监测第一节点的存活状态；第二节点根据存活状态确定第一节点为离线状态或在线状态。
在第一节点根据存活状态确定第二节点为离线状态之后，包括以下至少之一：
第二节点向中心节点发送离线通知消息，其中，离线通知消息用于指示第一节点已经离线；
第二节点将本地保存的第一节点的备份数据发送至数据平台，其中，数据平台与第一节点和第二节点连接。
在本实施例中提供了又一种运行于上述网络架构的节点的连接方法，图5是根据本公开实施例的节点的连接方法的流程图三，如图5所示，该流程包括如下步骤：
步骤S502，第三节点确定自身为网络的中心节点，其中，网络包括：第一节点，第二节点，以及第三节点；
步骤S504，第三节点选择第二节点为第一节点的协同节点；
步骤S506，第三节点向第一节点发送第一协同节点确认，其中，第一协同节点确认用于指示为第一节点分配的协同节点。
可选地，上述步骤的执行主体可以为通信节点，网关等，可以应用于智能家居系统，车联网系统，电力电网系统，智慧城市系统等泛在/物联网应用中，但不限于此。本实施例中，第三节点的身份为中心节点，为网络中的目标节点选择协同节点，同时具备普通节点的功能。
可选的，在第三节点向第一节点发送第一分配信息(第一协同节点确认)之后，还包括：
S41，中心节点接收第一节点发送的离线通知消息，其中，离线通知消息用于指示第二节点已经离线；
S42，中心节点尝试与第二节点进行通信，在尝试通信失败后，确定第二节点已经离线；
S43，在确定第二节点已经离线之后，中心节点向第一节点发送第二分配信息，其中，第一分配信息用于指示为第一节点分配的协同节点。
在本实施例中提供了又一种运行于上述网络架构的节点的连接方法，图6是根据本公开实施例的节点的连接方法的流程图四，如图6所示，该流程包括如下步骤：
步骤S602，第四节点与数据平台建立连接；
步骤S604，在与数据平台建立连接后，第四节点与终端建立连接；
步骤S606，第四节点获取终端采集的数据信息，在本地缓存数据信息，并将数据信息发送至数据平台。可选的，终端包括传感器，末梢设备等。
可选地，上述步骤的执行主体可以为通信节点，网关等，可以应用于智能家居系统，车联网系统，电力电网系统，智慧城市系统等泛在/物联网应用中，但不限于此。本实施例中，第四节点的身份为网络中的任意节点，包括普通节点和中心节点。
可选的，在第四节点将数据信息发送至数据平台之后，还包括：第四节点在本地删除数据信息，以及请求第四节点的协同节点在本地删除数据信息。
可选的，第四节点与终端建立连接包括：
S51，第四节点在局域网范围内广播接入信息，其中，接入信息用于请求终端接入第四节点；
S52，第四节点接收终端发送的连接建立请求，其中，连接建立请求携带终端的设备信息；
S53，第四节点根据设备信息与终端建立连接。
可选的，第四节点根据设备信息与终端建立连接包括：
S61，第四节点将设备信息发送给数据平台；
S62，第四节点接收数据平台反馈的注册确认信息，其中，注册确认信息用于指示终端在数据平台注册完成；
S63，第四节点在接收到注册确认信息后，与终端建立连接。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
本实施例是本公开的可选实施例，用于结合具体的示例对本申请的方案进行完整和详细说明：
本实施例通过协同节点之间相互备份数据，并且在发现协同节点无法连接时，代替协同节点主动上报管理中心出现故障，并将之前备份的采集数据上报。
在本实施例中，节点设备(如普通节点，中心节点)包括：选择模块、监测模块、管理模块与控制模块。
所述选择模块，用于实现协同节点的选择功能，包括中心节点确定、节点信息编码、协同节点分配功能；
所述监测模块，用于实现协同节点的监测功能，包括根据接收到的存活信息监测其协同节点的存活状态；
所述控制模块，用于实现协同节点接入控制的功能，包括控制协同节点间的连接建立以及连接拆除；
所述管理模块，用于实现节点的管理功能，包括接入管理子模块和数据管理子模块；其中，所述接入管理子模块包括对节点接入的管理；所述数据管理子模块包括对协同数据的管理。
本实施例适用的网络中，需要确定一个中心节点，而每个节点需要向数据平台上传数据信息。其中，每个节点有至多两个协同节点，协同节点间能够相互监测对方的存活状态，备份对方的数据信息；中心节点为网络中的任一节点(指定，或随机分配，或者是按照预定策略选择的)，具有普通节点的所有功能，还能根据网络拓扑等信息为网络中的所有节点分配协同节点。
本实施例还包括以下示例：
示例1：协同建立方法实施例
本实施例提供了建立和/或拆除协同的方法，请参考图7，图7是本实施例协同建立方法的流程图，协同建立方法流程包括：
步骤S101：在组建网络时或者网络拓扑变更时，任一网关的选择模块获取该网关以及 网络中的网关基于自身的节点状态确定的其作为中心网关的适合程度，确定适合程度最高的网关为网络的中心网关(对应上述实施例中的第三节点)；
可选的，所述适合程度可以是能量值、功率值、带宽值、加权平均值等，如能量值、功率值、带宽值最高的为中心网关。
步骤S102：中心网关的选择模块为同一网络中的每个网关配置编码信息；
需要说明的是，所述编码信息可以是位置信息的编码、应用相关信息的编码
步骤S103：中心网关的选择模块获取目标网关的编码信息，基于目标网关的编码信息从同一网络的多个网关中为目标网关选取满足预设要求的协同网关；
步骤S104：目标网关的选择模块接收到中心网关发送的协同网关确定消息后，向中心网关选取的协同网关的控制模块发送协同建立请求；
步骤S105：协同网关的控制模块通过对目标网关的认证和鉴权后，判断本地资源满足目标网关的业务需求，为目标网关分配资源，并确认建立协同；
步骤S106：协同建立后，协同网关的数据管理子模块接收目标网关根据预设周期发送的备份数据，并删除本地保存的超出本地存储容量的备份数据，直到本地存储容量未超出为止；
步骤S107：网关的监测模块根据接收到的其协同网关的存活信息监测其协同节点的存活状态；
步骤S108：网关的监测模块判断其协同节点的当前状态为离线时，向中心网关发送用于指示其协同网关已经离线的通知消息；
步骤S109：中心网关接收到所述通知消息后，尝试与该协同网关进行通信，在尝试通信失败时，确定该协同网关的当前状态为离线，则中心网关的选择模块重新进行协同网关分配；
步骤S109：协同中断后，网关的数据管理模块将其协同网关的备份数据上传到数据平台；
步骤S110：在需要进行协同网关重选或者断开连接时，协同网关的数据管理子模块向数据平台上传其协同网关的相关数据；同时，协同网关的接入控制模块移除本地其协同网关的相关资源，并确认拆除连接。
示例2：连接建立方法实施例
本实施例提供了建立连接的方法，请参考图8，图8是本实施例连接建立方法的流程图，连接建立方法流程包括：
步骤S201：网关(对应上述实施例中的第四节点)启动后，网关的接入管理子模块向数据平台发起连接建立请求，请求消息中包含网关的设备信息；
步骤S202：数据平台接收到所述请求消息后，根据所述设备信息对网关进行鉴权认证；鉴权认证通过后，数据平台向网关返回连接确认；
步骤S203：建立连接后，网关的数据管理子模块启动数据上传定时器；
步骤S204：网关的接入管理子模块在局域网范围内定期广播接入信息，等待终端接入；
步骤S205：终端启动后，接收到所述接入信息，向网关发送连接建立请求，请求消息中包含终端的设备信息；
步骤S206：网关的接入管理子模块接收到所述请求消息后，将终端的设备信息上报给数据平台，完成终端在数据平台的设备注册；设备注册通过后，数据平台向网关返回注册确认；
步骤S207：完成设备注册后，网关的接入管理子模块向终端返回连接确认；
步骤S208：建立连接后，终端定期向网关的数据管理子模块上报采集的数据信息；
步骤S209：网关的数据管理子模块缓存终端上报的数据信息；
步骤S210：数据上传定时器到期时，网关的数据管理子模块将当前存储的所有终端采集的数据信息上传给数据平台，并清除本地缓存；同时，向其协同网关的数据管理子模块发送删除本地保存的网关的备份数据的指示，并重启数据上传定时器。
本实施例针对现有技术中未对协同节点的结构进行说明的问题，提供了一种协同节点设备及其应用方法，实现了节点间的协同。
实施例3
本公开的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的计算机程序：
S1，接收中心节点的协同节点确认，其中，协同节点确认用于指示分配的协同节点；
S2，根据协同节点确认与第二节点建立和/或拆除协同。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，接收中心节点的协同节点确认，其中，协同节点确认用于指示分配的协同节点；
S2，根据协同节点确认与第二节点建立和/或拆除协同。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步 骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。
工业实用性
本公开适用于通信领域，用以实现在拓扑网络下的所有节点都存在协同节点，实现节点间的普遍备份和监测，解决了相关技术中不能对节点进行协同监测和备份的技术问题，提高了网络的稳定性和抗故障能力。

Claims (19)

  1. 一种通信设备，包括：
    选择模块，设置为选择第二节点；
    控制模块，设置为与所述第二节点建立和/或拆除协同；
    监测模块，设置为在与所述第二节点建立协同后，监测所述第二节点的存活状态。
  2. 根据权利要求1所述的设备，其中，所述选择模块包括：
    第一选择单元，设置为在组建网络时或者网络拓扑变更时，确定网络的中心节点。
  3. 根据权利要求1所述的设备，其中，在所述通信设备为中心节点时，所述选择模块还包括：
    配置单元，设置为为所述网络中的每个节点配置编码信息；
    第二选择单元，设置为根据所述编码信息为一个或多个网络中的节点分配协同节点。
  4. 根据权利要求1所述的设备，其中，所述控制模块包括：
    发送单元，设置为在接收到中心节点发送的协同节点确认后，向所述中心节点选取的协同节点发送协同建立请求。
  5. 根据权利要求1所述的设备，其中，所述控制模块包括：
    第一确认单元，设置为在接收到所述第二节点发送的协同建立请求后，判断本地资源满足所述第二节点的业务需求，为第二节点分配资源，确认与所述第二节点建立协同。
  6. 根据权利要求5所述的设备，其中，所述控制模块包括：
    第二确认单元，设置为在进行协同节点重选或者断开连接时，在本地移除所述第二节点的相关资源，确认与所述第二节点拆除协同。
  7. 根据权利要求1所述的设备，其中，所述监测模块包括：
    监测单元，设置为根据接收到的第二节点的存活信息监测所述第二节点的存活状态。
  8. 根据权利要求7所述的设备，其中，所述监测模块还包括：
    发送单元，设置为在判断所述第二节点的当前状态为离线时，向中心节点发送用于指示其协同节点已经离线的通知消息。
  9. 根据权利要求8所述的设备，其中，在所述通信设备为中心节点时，所述监测模块包括：
    确定单元，设置为在接收到所述通知消息后，尝试与所述第二节点进行通信，在尝试通信失败时，确定所述第二节点的当前状态为离线，并指示所述选择模块重新分配协同节点。
  10. 根据权利要求1至9任一项所述的设备，其中，所述设备还包括：
    管理模块，设置为实现对所述通信设备的接入管理和数据管理。
  11. 根据权利要求10所述的设备，其中，所述管理模块包括：
    接入管理单元，设置为在所述通信设备启动后，向数据平台发起第一连接建立请求；接收所述数据平台通过对所述通信设备的鉴权认证后返回的连接确认；以及在网络中定期 广播接入信息，接收终端在接收到所述接入信息后发送的第二连接建立请求；接收所述数据平台通过对所述终端的设备注册后返回的注册确认，向所述终端返回连接确认。
  12. 根据权利要求11所述的设备，其中，所述管理模块包括：
    数据管理单元，设置为在与所述第二节点建立协同后，接收所述第二节点根据预设周期发送的备份数据，以及删除超出本地存储容量的本地保存的备份数据；在协同中断后，将所述第二节点的备份数据上传到数据平台。
  13. 根据权利要求12所述的设备，其中，所述数据管理单元还设置为：
    与数据平台建立连接后，启动数据上传定时器；在所述数据上传定时器到期时，将当前存储的所述终端采集的数据信息上传给所述数据平台；向所述第二节点发送用于请求删除本地保存的所述通信设备的备份数据的指示，并重启所述数据上传定时器；以及在与所述终端建立连接后，缓存所述终端定期上报的其采集的数据信息。
  14. 一种节点的连接方法，包括：
    第一节点接收中心节点的协同节点确认，其中，所述协同节点确认用于指示分配的协同节点；
    所述第一节点根据所述协同节点确认与第二节点建立和/或拆除协同。
  15. 一种节点的连接方法，包括：
    第二节点接收第一节点发送的协同建立请求，其中，所述协同建立请求是所述第一节点根据中心节点发送的协同节点确认生成的；
    所述第二节点根据所述协同建立请求与所述第一节点建立协同。
  16. 一种节点的连接方法，包括：
    第三节点确定自身为网络的中心节点，其中，所述网络包括：第一节点，第二节点，以及所述第三节点；
    所述第三节点选择所述第二节点为所述第一节点的协同节点；
    所述第三节点向所述第一节点发送第一协同节点确认，其中，所述第一协同节点确认用于指示为所述第一节点分配的协同节点。
  17. 一种节点的连接方法，包括：
    第四节点与数据平台建立连接；
    在与所述数据平台建立连接后，所述第四节点与终端建立连接；
    所述第四节点获取所述终端采集的数据信息，在本地缓存所述数据信息，并将所述数据信息发送至所述数据平台。
  18. 一种存储介质，其中，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求14至17任一项中所述的方法。
  19. 一种电子装置，包括存储器和处理器，其中，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求14至17任一项中所述的方法。
PCT/CN2018/107979 2018-03-27 2018-09-27 通信设备、节点的连接方法、存储介质、电子装置 WO2019184285A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18911626.2A EP3780491A4 (en) 2018-03-27 2018-09-27 COMMUNICATION APPARATUS, NODE CONNECTION METHOD, INFORMATION SUPPORT AND ELECTRONIC DEVICE
US16/982,004 US20210021477A1 (en) 2018-03-27 2018-09-27 Communication Device, Node Connection Method, Storage Medium and Electronic Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810260565.1 2018-03-27
CN201810260565.1A CN110311800B (zh) 2018-03-27 2018-03-27 通信设备、节点的连接方法、存储介质、电子装置

Publications (1)

Publication Number Publication Date
WO2019184285A1 true WO2019184285A1 (zh) 2019-10-03

Family

ID=68062361

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107979 WO2019184285A1 (zh) 2018-03-27 2018-09-27 通信设备、节点的连接方法、存储介质、电子装置

Country Status (4)

Country Link
US (1) US20210021477A1 (zh)
EP (1) EP3780491A4 (zh)
CN (1) CN110311800B (zh)
WO (1) WO2019184285A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111181747B (zh) * 2018-11-09 2023-05-02 中兴通讯股份有限公司 一种网关协同实现方法、装置、IoT网关及存储介质
CN111404647B (zh) * 2019-01-02 2023-11-28 中兴通讯股份有限公司 一种节点协同关系的控制方法及相关设备
CN112512021A (zh) * 2020-02-19 2021-03-16 中兴通讯股份有限公司 拥塞控制方法、装置、设备、介质及系统
CN112584421A (zh) * 2020-12-01 2021-03-30 深圳力维智联技术有限公司 Fsu的管理方法、装置及计算机可读存储介质
CN112702192B (zh) * 2020-12-11 2023-09-29 阳光电源股份有限公司 通信设备的故障处理方法、装置、系统及存储介质
CN116506327B (zh) * 2023-06-26 2023-11-24 中航金网(北京)电子商务有限公司 物理节点监测方法、装置、计算机设备及存储介质
CN117113310B (zh) * 2023-10-16 2024-03-08 北京华鲲振宇智能科技有限责任公司 一种数据传输控制方法及系统、设备、介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101237267A (zh) * 2008-03-05 2008-08-06 中科院嘉兴中心微系统所分中心 无线传感网中的多传输节点协同波束成形方法
CN101577956A (zh) * 2009-06-15 2009-11-11 北京邮电大学 协作中继节点选择方法及系统
CN101860418A (zh) * 2009-04-10 2010-10-13 华为技术有限公司 一种无线网络协作方法及系统、网络节点
WO2013143065A1 (en) * 2012-03-27 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Shared keep-alive and failure detection mechanisms in distributed network

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH07311725A (ja) * 1994-05-18 1995-11-28 Fujitsu Ltd 開放型システム間相互接続におけるアプリケーション層のアソシエーション制御方法及びこれを用いたループキャリアシステム
US8169331B2 (en) * 2004-09-10 2012-05-01 Cooper Technologies Company Circuit protector monitoring assembly
US8549180B2 (en) * 2004-10-22 2013-10-01 Microsoft Corporation Optimizing access to federation infrastructure-based resources
CN101212326B (zh) * 2006-12-29 2011-01-12 上海贝尔阿尔卡特股份有限公司 一种在任意播组内对节点配置的方法和辅助方法及装置
CN101232415B (zh) * 2007-01-22 2012-01-11 华为技术有限公司 对等网络节点访问装置、方法和系统
WO2009093215A1 (en) * 2008-01-25 2009-07-30 Nokia Corporation Method, apparatus, and computer program product for providing device monitoring in a network
US9026603B2 (en) * 2011-06-30 2015-05-05 Broadcom Corporation Device configuration including a master communications device with a slave device extension
CN102932253B (zh) * 2011-08-10 2015-06-03 株式会社日立制作所 通信路径控制装置
US9450852B1 (en) * 2014-01-03 2016-09-20 Juniper Networks, Inc. Systems and methods for preventing split-brain scenarios in high-availability clusters
US10122604B2 (en) * 2014-02-28 2018-11-06 Cisco Technology, Inc. Emergency network services by an access network computing node
CN104394236B (zh) * 2014-12-18 2017-11-07 重庆邮电大学 节点与消息状态联合感知的分布式协作缓存方法
US10044705B2 (en) * 2016-01-20 2018-08-07 Facebook, Inc. Session management for internet of things devices
GB2546812B (en) * 2016-02-01 2020-05-27 Shields Energy Services Ltd System for controlling a plurality of power-consuming devices
EP3573422B1 (en) * 2017-01-17 2024-02-21 Sony Group Corporation Pairing of wireless nodes
CN106982248B (zh) * 2017-03-01 2019-12-13 中国科学院深圳先进技术研究院 一种内容中心网络的缓存方法及装置
CN107231251A (zh) * 2017-05-23 2017-10-03 中国电子科技集团公司第四十研究所 一种网络化分布式测试系统的多节点协同控制方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101237267A (zh) * 2008-03-05 2008-08-06 中科院嘉兴中心微系统所分中心 无线传感网中的多传输节点协同波束成形方法
CN101860418A (zh) * 2009-04-10 2010-10-13 华为技术有限公司 一种无线网络协作方法及系统、网络节点
CN101577956A (zh) * 2009-06-15 2009-11-11 北京邮电大学 协作中继节点选择方法及系统
WO2013143065A1 (en) * 2012-03-27 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Shared keep-alive and failure detection mechanisms in distributed network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3780491A4 *

Also Published As

Publication number Publication date
CN110311800B (zh) 2022-10-11
EP3780491A1 (en) 2021-02-17
US20210021477A1 (en) 2021-01-21
EP3780491A4 (en) 2021-05-19
CN110311800A (zh) 2019-10-08

Similar Documents

Publication Publication Date Title
WO2019184285A1 (zh) 通信设备、节点的连接方法、存储介质、电子装置
JP5414807B2 (ja) ネットワークにおけるアドレス割り当て
CN105095022B (zh) 一种数据备份方法及装置
CN111083718A (zh) 一种会话管理方法、网络功能及网络系统
US11251981B2 (en) Communication method and apparatus
WO2020093979A1 (zh) 网关协同实现方法、装置、IoT网关及存储介质
CN102783094A (zh) 用于基于会话发起协议的通信系统的弹性路由
EP3028207B1 (en) Communication using over-the -top identities without centralized authority
CN105208530A (zh) 一种组呼业务处理方法、终端及核心网网元
US8625462B2 (en) Ownership requests for access points
WO2017000625A1 (zh) 动态主机配置协议dhcp服务器管理方法及装置
CN112788089A (zh) 多边缘云的网络通讯控制方法及边缘运算装置与系统
WO2019019607A1 (zh) 数据备份方法、装置及系统
WO2014067313A1 (zh) 终端外设的注销方法和装置
WO2021254466A1 (zh) 一种配置边缘侧设备的方法、装置及系统
WO2019062645A1 (zh) 节点管理方法及装置
EP3435615B1 (en) Network service implementation method, service controller, and communication system
JP6119073B2 (ja) 基地局の自律のための方法、ベースバンドユニット、基地局、及びクラウド基地局システム
WO2019242459A1 (zh) 节点切换方法、网络节点、网络系统及存储介质
CN112394662A (zh) 一种变电站监控系统服务器角色确定方法及系统
CN111400095A (zh) 一种集群以及异常断电重启集群的方法、系统以及介质
CN105830408B (zh) 脑裂情况期间的资源的分配
CN116744352A (zh) 网络容灾方法、装置及存储介质
JP5851919B2 (ja) 呼制御システムおよび呼制御に利用する情報の冗長化方法
CN116916466A (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: 18911626

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018911626

Country of ref document: EP

Effective date: 20201027