Method for network load reduction in polling procedures
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SIGNIFY HOLDING BV
- Filing Date
- 2024-12-09
- Publication Date
- 2026-08-04
AI Technical Summary
在带宽受限的网络中,重复请求所有网络节点的状态(轮询)会导致繁重的网络负载,这引起其他网络流量的延迟
Smart Images

Figure CN122514977A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of control systems for connections. More specifically, various methods, apparatuses, and systems related to schemes for improving communication efficiency in polling processes are disclosed herein. Background Technology
[0002] There is a growing trend in the professional lighting market toward connected lighting systems, enabling a wide range of new features such as (remote) dispatching, energy monitoring, sensor-based lighting control, and asset management. In many cases, these systems are installed in existing buildings, where wireless networks are preferred to avoid the need to deploy new cabling through the ceiling (for lighting control). Examples of such wireless network protocols widely used in current practice are open standards such as Zigbee, Thread, BLE, BLE mesh, Wi-Fi, Wi-Fi Direct, and various proprietary network implementations built on IEEE 802.15.4, IEEE 802.15.1, or IEEE 802.11 standards.
[0003] Polling is a technique used in connected control networks to enable communication between multiple devices. In this technique, a central controller (e.g., a server) sends a request for information to each device connected to the network. Each device then responds to the request using the requested information. Polling is commonly used in wireless control networks where a controller is responsible for collecting data from multiple sensors or actuators. By using polling, the controller can efficiently collect data from every node in the network without having to constantly maintain a connection with each node. In the context of lighting, polling is important not only for the state of individual lights but also for the state of a scene in a room, such as detecting the current scene in a room by observing the states of all the lights in the room.
[0004] In many cases, the network connectivity may be so large that not all nodes are reachable via a direct link from the central controller, and therefore those remote nodes may require assistance from one or more relay nodes. In bandwidth-constrained networks, repeatedly requesting the status of all network nodes (polling) can lead to heavy network loads, causing delays in other network traffic. Since each poll includes both a request and a response, it involves two messages. Each of these messages may require multiple hops to reach the polling device and the polled device, causing even more network traffic. Summary of the Invention
[0005] Polling-based state monitoring provides a mechanism to keep the coordinator, central controller, or bridging device constantly updated in response to any changes in the connected network. However, polling also introduces a significant traffic load into the network, especially when polling requires multi-hop routing. This scenario worsens as the network expands. On the other hand, most polling requests return expected or unchanged states, particularly for less dynamic networks such as lighting networks.
[0006] In view of the foregoing, this disclosure relates to methods, apparatus, systems, and computer programs for providing more efficient data exchange during polling processes to reduce traffic load on connected networks. More specifically, the objectives of the invention are achieved by the method for performing a polling process as described in claim 1, by the connected network as described in claim 12, and by the computer program as described in claim 15.
[0007] According to a first aspect of the present invention, a method for performing a polling process is provided. A method for performing a polling process to collect information about the state, attributes, or settings of individual nodes in a connected network; the method includes: - A request is sent from the first node in the connected network to the second node in the connected network, and the request includes the expected response regarding the status, attributes, or settings of the second node; - When the actual state, attributes, or settings of the second node differ from the expected response, the second node sends a response to the first node, wherein the response includes information about the actual state, attributes, or settings of the second node; and - Avoid sending a response from the second node when the actual state, attributes, or settings of the second node are the same as the expected response.
[0008] To reduce the traffic load associated with polling, it is recommended that the expected response be included in the polling request issued by the polling device or the first node. Then, the polled node or the second node will only send a polling response if the actual state, attributes, or settings differ from the expected response received in the polling request. Therefore, instead of the regular two-message polling handshake, in many cases only the polling request is actually executed. Consequently, depending on how frequently the node's state, attributes, or settings will typically change, the network load for polling can be reduced by up to 50%. For large networks with frequent polling messages to many nodes, this can be a significant improvement.
[0009] Alternatively, the expected response to the status, attributes, or settings of the second node in the polling request can be replaced with a flag or indicator that indicates a request for a response, or a response can be requested only if the second node has undergone any change in status, attributes, or settings compared to an earlier status, attribute, or setting reported in a previous response. In this manner, the method includes: - A request is sent from a first node in the connection network to a second node in the connection network, wherein the request includes a flag indicating that a response is required unconditionally or only if the second node has any change in status, attribute, or setting compared to an earlier status, attribute, or setting reported in a previous response; - When a flag in the request indicates that a response is unconditionally required, or when the actual state, attribute, or setting differs from the earlier state, attribute, or setting reported in the previous response, the second node sends a response to the first node, wherein the response includes information about the actual state, attribute, or setting of the second node; and - Avoid sending a response from the second node when the flag in the request indicates that a response is only required if there is any change in the second node's status, attributes, or settings, and the actual status, attributes, or settings of the second node are the same as those reported in a previous response.
[0010] Advantageously, the method further includes the following steps: - Upon receiving the response, the first node updates the expected response based on the information included in the response.
[0011] Basically, upon receiving a response, the first node updates the storage state of the second node using the information included in the response. This changes the expected state for future polls of the second node.
[0012] If no response is received to the request, the first node will assume that there has been no change to the state, attributes, or settings of the individual node; otherwise, it will update the information in its local database accordingly, as well as overwrite the expected response in the next polling request.
[0013] In one example, the method further includes a step in which the first node detects a response in the connected network during a first interval before sending the request to the second node again.
[0014] The first interval can be determined based on one or more of the following: the size of the connected network, the expected latency for receiving a response from the second node, the number of hops from the first node to the second node, the real-time or historical traffic load in the connected network, or the power budget of the first node and / or the second node.
[0015] Preferably, the request is sent periodically by the first node.
[0016] Periodic polling helps the first node obtain continuous updates on information about individual nodes in the connected network. Alternatively, the polling process can also be performed on demand, allowing requests to be triggered by events or needs.
[0017] Advantageously, the method further includes, before detecting any response from a second node or from one or more other nodes in the connected network, the first node sending one or more additional requests, one after another, to one or more other nodes in the connected network; wherein each of the one or more additional requests includes an expected response to the status, attributes, or settings of the corresponding node among the one or more other nodes.
[0018] In one option, polling requests and responses from each individual node are processed sequentially. Alternatively, and potentially beneficial, a batch of requests is sent to multiple nodes one after another before detecting on the channel to see if any response exists from one or more of those nodes. This can be quite efficient when the network is not very dynamic, ensuring that the state, attributes, or settings of the nodes in the network do not change frequently, and that nodes remain silent most of the time when they receive polling requests. This also helps reduce the energy consumption and time spent by the first node in detecting potential responses.
[0019] Advantageously, the method further includes the step of sending an update message by the third node after power-on, wherein the update message includes information related to the state, attributes, or settings of the third node.
[0020] When a new node is added to the connected network, or another node comes back online after a reboot or power-on, it is important to include that new node or the third node in the polling process used to collect information. Advantageously, the method further includes the step of sending an update message by the new node or third node after power-on, wherein the update message includes information related to the third node's status, attributes, or settings. Such an update message is initiated by the new node or third node itself as an unrequested status update, without requiring a polling request.
[0021] Advantageously, the method further includes a step of including a third node during the polling process.
[0022] Upon receiving an aperiodic update message, the first node or another node in the connected network will include the new node or the third node in the polling process, so that the first node will poll the new node or the third node in the same way as the other nodes included in the polling process.
[0023] Preferably, the network being connected is a wireless network.
[0024] Connected networks can have different topologies, such as ring topology, tree topology, star topology, mesh topology, or hybrid topology that combines two or more of the above topologies.
[0025] In one example, the network connection is a multi-hop network.
[0026] In one setup, requests are sent from the first node to the second node via multi-hop routing.
[0027] When the network has a mesh or tree topology, request and response messages between the first and second nodes can be sent via multi-hop routing.
[0028] Advantageously, the first node is at least one of the network coordinator, central controller, bridge, or gateway.
[0029] According to a second aspect of the invention, a connection network is provided. A connection network comprising multiple nodes is configured to perform a polling process to collect information about the state, attributes, or settings of individual nodes in the connection network; the connection network includes: - The first node among multiple nodes is configured to send a request to the second node among multiple nodes, the request including an expected response regarding the second node's status, attributes, or settings; and - The second node is configured as follows: When the actual state, attributes, or settings of the second node differ from the expected response, a response is sent to the first node, the response including information about the actual state, attributes, or settings of the second node; and ○ Avoid sending a response when the actual state, attributes, or settings of the second node are the same as the expected response.
[0030] The network can operate according to wired communication protocols such as Konnex (KNX), Modular Digital Communication System (MODBUS), Building Automation and Control Network (BACnet), or Digital Addressable Lighting Interface (DALI).
[0031] Connectivity networks can operate according to wireless communication protocols, such as enabling large-scale information distribution and collection in wireless control systems with multiple nodes, and can be used for lighting control and / or building automation. It is beneficial for the wireless communication protocol to support multi-hop routing; this protocol can be Zigbee, Thread, Bluetooth Mesh, Wi-Fi mesh, WirelessHART, SmartRF, CityTouch, IP500, Z-wave, or any other mesh- or tree-based technology.
[0032] In one example, the network can be a one-to-many network with a central controller or gateway device and multiple nodes to be controlled. Control commands distributed across the network can originate locally from the central controller or from the cloud via the gateway device. The central controller or gateway device is used to issue control commands to the distributed network in a centralized manner. In turn, the multiple nodes in the distributed network are configured to provide feedback to the central controller or cloud with status information related to functional devices or actuators controlled by the central controller or cloud. In addition to actuators, other sensors may be present that are co-located with the multiple nodes. Therefore, the status information may also include sensing data or status information from other sensors. Thus, in a preferred example, communication in the system can be one-to-many or many-to-one.
[0033] The first node is configured to send a polling request that includes an expected response to the status, attributes, or settings of the second node. The expected response to the second node's status, attributes, or settings can be derived based on historical information, earlier responses, default values, or user input. The second node is configured to: send a response to the first node when the actual status, attributes, or settings of the second node differ from the expected response, the response including information about the actual status, attributes, or settings; and avoid sending a response when the actual status, attributes, or settings of the second node are the same as the expected response.
[0034] Advantageously, the first node is further configured as follows: - Upon receiving a response, update the expected reply based on the information included in the response.
[0035] Therefore, when no response or update is received from the second node, the first node assumes that there has been no change in the state, attributes, or settings of the second node, and that the expected response remains unchanged. In this way, depending on how frequently the node's state, attributes, or settings typically change, the network load used for polling can be reduced by up to 50%. The less dynamic the nodes are, the greater the reduction in traffic load.
[0036] In one example, the first node is further configured as follows: - Before detecting any response from a second node or from one or more other nodes in the connected network, one or more additional requests are sent one after another to one or more other nodes among the plurality of nodes; each of the one or more additional requests includes an expected response to the status, attributes, or settings of the corresponding node among the one or more additional nodes.
[0037] Instead of processing each polling request and response sequentially from each individual node, it may also be beneficial to send a sequence of requests to multiple nodes (thus sending many requests one after another directly), and then only detect on the channel whether a response has been received from one or more of those nodes. This is particularly effective when the network is not very dynamic, meaning the state, attributes, or settings of the nodes in the network do not change frequently, and most of the time the nodes will remain silent when they receive polling requests. Thus, after a series of polling requests, the first node may occasionally receive a response from one of the multiple nodes.
[0038] The invention can be further embodied in a computer program that includes code means, which, when executed by a first or second node according to the invention and including a processing means, causes the processing means included in the first or second node to perform the method according to the invention. Attached Figure Description
[0039] Throughout the accompanying drawings, similar reference numerals typically refer to the same parts. Furthermore, the drawings are not necessarily drawn to scale, but generally focus on illustrating the principles of the invention.
[0040] Figure 1 The diagram illustrates a mesh network; Figure 2 This demonstrates a connected network comprising multiple nodes configured to perform a polling process; and Figure 3 A flowchart is shown for the method used to perform the polling process. Detailed Implementation
[0041] The embodiments described below illustrate information that enables those skilled in the art to practice the embodiments. When reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of this disclosure and will recognize the application of these concepts unless specifically stated herein. It should be understood that these concepts and applications fall within the scope of this disclosure.
[0042] Figure 1 The diagram illustrates a mesh network. In a mesh network, devices are directly and indirectly connected to each other to allow multiple communication paths between nodes. This means data can be sent from one node to another via multiple routes, creating a redundant and resilient network. Mesh networks are commonly used in wireless sensor networks, home automation, and industrial applications where reliability and flexibility are paramount. Figure 1As shown, a mesh network may include a coordinator or central controller, which manages communication between nodes in the network, distributes and / or collects information to nodes in the network, or acts as the central point of the mesh network to connect to another network interface. Multiple router nodes are present, responsible for forwarding data packets between nodes in the network to achieve multi-hop routing. In addition to router nodes, there are other types of nodes called end nodes, which are connected to the network but do not participate in the routing of data packets. End nodes are devices primarily responsible for sensing, actuating, or controlling specific functions or applications. Sometimes, end nodes may have limited processing power, memory, and communication capabilities compared to router nodes or coordinator nodes. They are designed to be simple and low-cost, enabling their large-scale deployment throughout the network. End nodes in a mesh network typically communicate with other nodes in the network through router nodes or parent nodes. They send and receive data packets to and from the network, but they do not participate in the routing of data packets.
[0043] Polling is a common communication method in control networks, where a coordinator sends requests to one or more devices to retrieve data or perform actions. The coordinator is responsible for initiating and controlling communication between devices in the network. In a polling-based control network, the coordinator can periodically send requests to nodes. These requests typically include information about the data to be retrieved or the action to be performed. Nodes in the control network respond to the requests with the requested data or confirmation of the performed action.
[0044] Polling can be done in different ways, such as periodic polling or on-demand polling. In periodic polling, the coordinator polls the nodes periodically, while in on-demand polling, the coordinator polls the nodes only when new data is needed or when an action needs to be performed.
[0045] Polling provides a reliable and efficient method for communication between devices. However, polling can also lead to latency and increased traffic on the network, which can impact network performance. This invention discloses an improved polling process that reduces traffic load overhead.
[0046] Figure 2 A connected network 100 comprising multiple nodes 110, 121-12n is shown, configured to perform a polling process.
[0047] Network 100 can be a local network under the control of a local coordinator for a specific control purpose. This network can also be connected to a cloud or backbone network via gateway, bridge, or router devices.
[0048] The network can operate according to wired communication protocols such as Konnex (KNX), Modular Digital Communication System (MODBUS), Building Automation and Control Network (BACnet), or Digital Addressable Lighting Interface (DALI).
[0049] Connectivity networks can operate according to wireless communication protocols, such as enabling large-scale information distribution and collection in wireless control systems with multiple nodes 110, 121-12n, and can be used for lighting control and / or building automation. Support for multi-hop routing in the wireless communication protocol is beneficial; this protocol can be Zigbee, Thread, Bluetooth Mesh, Wi-Fi mesh, WirelessHART, SmartRF, CityTouch, IP500, Z-wave, or any other mesh- or tree-based technology.
[0050] Given that a control system can include a large number of nodes, transmission between nodes may rely on multi-hop routing. In bandwidth-constrained networks, repeatedly requesting the status of all network nodes (polling) would be a heavy network load, causing delays in other network traffic.
[0051] Using a Zigbee network as an example. Zigbee networks have limited bandwidth, but they can include a large number of nodes (currently up to 63, and in the near future up to 200-255). This is to accurately display the actual status of all lights in a lighting control app within seconds, also for out-of-band light changes (local button, BLE, power on / off, Zigbee remote control) that the bridge only knows about via polling. Polling is important not only for individual light states but also for the scene state in the room, and the current scene in the room is detected by the status of all the lights in the room.
[0052] Furthermore, each polling session includes a request and a response, thus comprising two messages. Each message can sequentially travel through multiple hops to reach the polled device and back to the polling device, causing even more network traffic. In view of this, the present invention discloses a more efficient polling process for reducing the traffic load associated with polling in the network.
[0053] The first node 110 can be a coordinator, central controller, bridge, or gateway connecting network 100. Other nodes to be polled by the first node can be routers or end nodes in the mesh network context.
[0054] In the context of lighting, nodes 120-12n can be included in lighting devices, luminaires, sensors, actuators (such as switches for communication functions for lighting devices, luminaires, sensors, or switches). Nodes 120-12n can also be included in the broader context of building / home automation, in HVAC systems, smart refrigerators, smart ovens, other smart white goods, or remote controls.
[0055] The first node 110 is configured to send a polling request that includes an expected response to the status, attributes, or settings of the second nodes 121-12n. The expected response to the status, attributes, or settings of the second nodes 121-12n can be derived based on historical information, earlier responses, default values, or user input. The second nodes 121-12n are configured to send a response to the first node 110 when their actual status, attributes, or settings differ from the expected response, wherein the response includes information about the actual status, attributes, or settings; and to avoid sending a response when their actual status, attributes, or settings are the same as the expected response.
[0056] The first node 110 is further configured to update the expected response based on the information included in the response when a response is received. Therefore, when no response or update is received from the second node, the first node will assume that the state, attributes, or settings of the second node have not changed, and that the expected response remains unchanged.
[0057] In this scenario, nodes in the network (such as lighting devices, lamps, sensors, actuators) only respond if their state differs from the "expected state" in the request, and the coordinator, central controller, bridge, or gateway interprets "no response" as "state unchanged".
[0058] Therefore, depending on how frequently the node's state, attributes, or settings typically change, the network load for polling can be reduced by 30-50%. The less dynamic the node, the greater the reduction in traffic load.
[0059] Figure 3 A flowchart of a method 800 for performing a polling process to collect information about the status, attributes, or settings of individual nodes in a connected network 100 is shown. Method 800 includes the following steps: - In step S801, the first node 110 in the connection network 100 sends a request to the second nodes 121-12n in the connection network 100, wherein the request includes an expected response regarding the status, attributes, or settings of the second nodes 121-12n; - In step S803, when the actual state, attributes, or settings of the second nodes 121-12n differ from the expected response determined in step S802, the second nodes 121-12n send a response to the first node 110, the response including information about the actual state, attributes, or settings; and - Avoid sending an S804 response from the second nodes 121-12n when the actual state, attributes, or settings of the second nodes 121-12n are the same as the expected response as determined in step S802.
[0060] Optionally, method 800 further includes step S805: upon receiving a response, the first node 110 updates the expected response based on the information included in the response.
[0061] Method 800 may further include the step of the first node 110 detecting a response in the connected network 100 during a first interval before resending the request to the second nodes 121-12n. The first interval may be determined based on one or more of the following: the size of the connected network 100, the expected latency for receiving a response from the second nodes 121-12n, the number of hops from the first node 110 to the second nodes 121-12n, the real-time or historical traffic load in the connected network 100, or the power budget of the first and / or second nodes.
[0062] Advantageously, in order to obtain continuous updates, the first node 110 can send requests periodically. The frequency of periodic requests can be determined based on one or more of the following: the size of the connected network 100, the expected latency of transmitting messages back and forth between the first node 110 and the second nodes 121-12n, the real-time or historical traffic load in the connected network 100, the power budget of the multiple nodes 110 and 121-12n, and the dynamics of the nodes in the network in terms of the rate of change of the state, attributes, or settings of individual nodes.
[0063] Instead of processing each polling request and response sequentially for each individual node, it may also be beneficial to send a sequence of requests to multiple nodes (thus sending several requests one after another directly), and then only detect on the channel to see if there is a response from one or more of those nodes. This is particularly effective when the connected network is less dynamic, such that the state, attributes, or settings of the nodes in the network do not change frequently, and most of the time the nodes will remain silent when they receive polling requests. Therefore, method 800 includes the following steps: before any response is detected in the connected network 100 for a second node 121-12n or from one or more other nodes 121-12n, the first node 110 sends one or more additional requests one after another to one or more other nodes 121-12n in the connected network 100. Each of the one or more additional requests includes an expected response to the state, attributes, or settings of the corresponding node among the one or more other nodes 121-12n. Optionally, a random backoff time scheduling may be applied when one or more of the one or more other nodes 121-12n need to send a response with updated information. Therefore, any potential conflicts between those responses can be reduced. This option helps to further improve the efficiency of the polling process in a connected network.
[0064] In one scenario, there may be a new node added to the connected network or another node that comes back online after a restart or power-on. Therefore, it is important to include this new or third node in the polling process used to collect information. Advantageously, the method further includes the step of sending an update message by the new or third node after power-on, wherein the update message includes information related to the third node's status, attributes, or settings. Such an update message is initiated by the new or third node itself as an unrequested status update, without requiring a polling request.
[0065] Upon receiving an aperiodic update message, the first node or another node in the connected network will include the new node or third node in the polling process, so that the first node will poll the new node or third node in the same way as the other nodes included in the polling process.
[0066] The method according to the invention can be implemented on a computer as a computer-implemented method, or in dedicated hardware or a combination of both.
[0067] The executable code of the method according to the invention can be stored on a computer / machine-readable storage device. Examples of computer / machine-readable storage devices include non-volatile memory devices, optical storage media / devices, solid-state media, integrated circuits, servers, etc. Preferably, the computer program product includes non-transitory program code means stored on a computer-readable medium for executing the method according to the invention when the program product is executed on a computer or processing device included in the node or network or debugging equipment disclosed in the above embodiments.
[0068] Methods, systems, and computer-readable media (temporary and non-temporary) may also be provided to implement selected aspects of the above embodiments.
[0069] The term "controller" is generally used herein to describe various means relating to the operation and other functions of one or more network devices or coordinators. A controller can be implemented in a variety of ways (e.g., utilizing dedicated hardware) to perform the various functions discussed herein. A "processor" is an example of a controller employing one or more microprocessors, which can be programmed using software (e.g., microcode) to perform the various functions discussed herein. A controller can be implemented with or without a processor, and can also be implemented as a combination of dedicated hardware performing some functions and processors (e.g., one or more programmed microprocessors and associated circuitry) performing other functions. Examples of controller components that can be employed in various embodiments of this disclosure include, but are not limited to, conventional microprocessors, application-specific integrated circuits (ASICs), and field-programmable gate arrays (FPGAs).
[0070] In various embodiments, the processor or controller may be associated with one or more storage media (collectively referred to herein as "memory," such as volatile and non-volatile computer memories, such as RAM, PROM, EPROM, and EEPROM, compact disks, optical disks, etc.). In some embodiments, the storage media may be encoded with one or more programs that, when executed on one or more processors and / or controllers, perform at least some of the functions discussed herein. The various storage media may be fixed within the processor or controller, or may be transferable, such that one or more programs stored on the various storage media may be loaded into the processor or controller to implement various aspects of the invention discussed herein. The terms "program" or "computer program" are used herein in a general sense to refer to any type of computer code (e.g., software or microcode) that can be used to program one or more processors or controllers.
[0071] As used herein, the term “network” refers to any interconnection of two or more devices (including controllers or processors) that facilitates the transfer of information (e.g., for device control, data storage, data exchange, etc.) between any two or more devices and / or between multiple devices coupled to the network.
Claims
1. A method (800) for performing a polling process to collect information about the state, attributes, or settings of individual nodes in a connected network (100); the method (800) comprising: - A request (S801) is sent from a first node (110) in the connection network (100) to a second node (121-12n) in the connection network (100), wherein the request includes an expected response to the status, attributes or settings of the second node (121-12n); - When the actual state, attributes, or settings of the second node (121-12n) differ from the expected response (S802), the second node (121-12n) sends a response to the first node (110) (S803), wherein the response includes information about the actual state, attributes, or settings of the second node (121-12n); and - When the actual state, attributes, or settings of the second node (121-12n) are the same as the expected response (S802), avoid sending a response (S804) by the second node (121-12n).
2. The method (800) according to claim 1, further comprising the following steps: - Upon receiving the response, the first node (110) updates (S805) the expected reply based on the information included in the response.
3. The method (800) of claim 1 or 2, further comprising: During a first interval before the request is sent again to the second node (121-12n), the first node (110) detects the response in the connection network (100).
4. The method (800) according to any one of the preceding claims, wherein the request is periodically sent by the first node (110).
5. The method (800) according to any of the preceding claims, further comprising: Before any response from the second node (121-12n) or from one or more other nodes (121-12n) is detected in the connection network (100), the first node (110) sends one or more additional requests, one after another, to one or more other nodes (121-12n) in the connection network (100); each of the one or more additional requests includes an expected response to the status, attributes, or settings of the corresponding node in the one or more other nodes (121-12n).
6. The method (800) according to any of the preceding claims, further comprising: An update message is sent by the third node after power-on, wherein the update message includes information related to the state, attributes or settings of the third node.
7. The method (800) of claim 6, further comprising: Include the third node in the polling process.
8. The method (800) according to any one of the preceding claims, wherein the connection network (100) is a wireless network (100).
9. The method (800) according to any one of the preceding claims, wherein the connection network (100) is a multi-hop network (100).
10. The method (800) of claim 9, wherein the request is sent from the first node (110) to the second node (121-12n) via multi-hop routing.
11. The method (800) according to any one of the preceding claims, wherein the first node (110) is at least one of a coordinator, central controller, bridge or gateway of the connected network (100).
12. A connection network (100) comprising multiple nodes (110, 121-12n), the connection network (100) being configured to perform a polling process to collect information about the status, attributes, or settings of individual nodes in the connection network (100); the connection network (100) comprising: - A first node (110) of the plurality of nodes is configured to send a request to a second node of the plurality of nodes (110, 121-12n), wherein the request includes an expected response to the status, attributes, or settings of the second node (121-12n); and - The second node (121-12n) is configured as follows: ○ When the actual state, attributes, or settings of the second node (121-12n) differ from the expected response, a response is sent to the first node (110), wherein the response includes information about the actual state, attributes, or settings of the second node (121-12n); and ○ Avoid sending a response when the actual state, attributes, or settings of the second node (121-12n) are the same as the expected response.
13. The connection network (100) according to claim 12, wherein the first node (110) is further configured to: - Upon receiving the response, update the expected response based on the information included in the response.
14. The connection network (100) according to claim 12 or 13, wherein the first node (110) is further configured to: - Before any response from the second node (121-12n) or from one or more other nodes is detected in the connection network (100), one or more additional requests are sent one after another to one or more of the plurality of nodes (121-12n); each of the one or more additional requests includes an expected response to the status, attributes or settings of the corresponding node among the one or more additional nodes (121-12n).
15. A computing program including a code means, wherein when the program is executed by a first node (110) or a second node (121-12n) including a processing means according to claim 12, the code means causes the processing means included in the first node (110) or the second node (121-12n) to perform the method (800) according to claims 1-11.