Method and system for data transfer over a mesh network

Abstract

A method of transferring data over a mesh network (400) is disclosed. The method comprises selecting at least one node (405, 415, 425) in the mesh network to be configured as a seed node for transmitting data to a subset of nodes in the mesh network. The method also comprises providing, from a head-end system (410), the at least one seed node with the data to be transmitted to the subset of nodes. The method comprises transmitting the data from the at least one seed node to the subset of nodes. A corresponding system comprising a network of nodes configured to form a mesh network; and a head-end system is also disclosed.

Description

[0001] MC1-033231-WO-ORD METHOD AND SYSTEM FOR DATA TRANSFER OVER A MESH NETWORK RELATED APPLICATONS This application claims priority from Great Britain Patent Application Serial No.2219840.2, filed 30 December 2022, which is incorporated herein in its entirety. FIELD OF INVENTION The disclosure is in the field of methods and systems for transferring data over a mesh network, and in particular a mesh network of nodes comprising devices for metering and / or controlling a resource. BACKGROUND TO INVENTION Metering devices may be deployed at businesses, homes, and other premises for measuring consumption of resources, such as electricity, water, and gas. While some metering devices may provide only basic metering functions, other metering devices, known in the art as “smart meters”, may provide more advanced functionality, such as control and communications functionality. In an example, some metering devices may be configured to communicate information relating to consumption of resources. In another example, some metering devices may be configured to receive information such as billing information and control signals, such as service disconnect control signals or the like. In examples, transmission of information relating to consumption of metered resources may simplify automated billing, reduce operational costs, and may enable advanced analytics of resource consumption. While in some examples a metering device may communicate directly with a router or gateway device, in other examples a wireless mesh network may be formed from multiple metering devices, wherein each metering device operates as an interconnected node within the wireless mesh network. When implemented in a wireless mesh network, a metering device operating as a network node may relay messages to or from a gateway device or router, or a head-end system. In an example, messages may be routed along a path by hopping from node to MC1-033231-WO-ORD node, e.g. from metering device to metering device until said messages reaches a target destination, e.g. the gateway / router or a target metering device. Various routing protocols may be implemented in a wireless mesh network to ensure availability of sufficient data routing paths within the mesh network at any given time. In some examples of wireless mesh networks, paths within the network may self- form and / or self-heal, e.g. reconfigure around broken paths. Such self-healing may allow a routing-based network to operate when a node breaks down or when a connection between nodes becomes unreliable. In use, smart metering devices within a wireless mesh network may constantly communicate with each other to, for example, exchange messages or transmit data. In examples, different nodes within the network may have different hardware and software configurations and thus may support different communication modes. In addition, each node may support multiple communication modes. Throughput and reliability are important issues for communications in such wireless mesh networks. For example, a throughput may be impacted if a node has a pending communication but is unable to access a communications channel. Other nodes may already be using the channel for communication or the channel may be otherwise unavailable. Furthermore, variable environmental conditions and in-band interference can result in communication failures in a wireless mesh network. An example mesh network of metering devices may comprise hundreds-of thousand, or even millions, of devices. In use, a head-end system may need to push data to devices onto the mesh network. However, a throughput of the mesh network may hamper such operations, and may incur a significant overhead at the head-end system. Furthermore, existing data distribution schemes for transmitting data over a mesh- network may implement inefficient schemes, which may create an excessive load of redundant or obsolete data. In some examples, the outbound processing batch may overload the resources of the head-end system. Additionally, as more types of data are supported by the system, more than one message may need to propagate the network for each device. MC1-033231-WO-ORD As an example, unicast transport of data across the mesh network may be practically unfeasible when targeting an entire network, especially of the data to be transmitted has time constraints. Similarly, multicast transport of data may be inherently inefficient over a large mesh network, especially is receiving nodes may either drop the data, or if multicast grouping is not sufficient to filter out devices that do not need the data. Blind unicast is also a poor solution, primarily because it is not scalable. Multicast may load the mesh network unnecessarily. It is therefore desirable to provide a relatively low-complexity, efficient and effective method and system for transferring data over a mesh network, and in particular a mesh network of nodes comprising devices for metering and / or controlling a resource. It is desirable that such a method and system are suitable for transmitting time-sensitive data over a mesh network supporting relatively low bandwidth data transmission between nodes. It is therefore an aim of at least one embodiment of at least one aspect of the present disclosure to obviate or at least mitigate at least one of the above identified shortcomings of the prior art. SUMMARY OF INVENTION The present disclosure is in the field of methods and systems for transferring, e.g. transmitting, data over a mesh network, and in particular a mesh network of nodes comprising devices for metering and / or controlling a resource. According to a first aspect of the disclosure, there is provided a method of transferring data over a mesh network. The method comprises selecting at least one node in the mesh network to be configured as a seed node for transmitting data to a subset of nodes in the mesh network. The method also comprises providing, from a head-end system, the at least one seed node with the data to be transmitted to the subset of nodes. The method also comprises transmitting the data from the at least one seed node to the subset of nodes. Advantageously, by seeding a node such that the seed node transmits the data, an efficient use of the mesh network may be implemented. That is, data may be MC1-033231-WO-ORD transmitted to nodes without the overhead of connecting and sending data to each node directly which can cause a significant overhead at the head-end system. The mesh network may comprise a full mesh topology or a partial mesh topology. The network may comprise one or more intermediate nodes, such as routers or gateways devices. The network may comprise one or more root nodes between the nodes, e.g. end-nodes, and the head-end system. The head-end system may function as a central processing system that transmits and / or receives data, streams of data, data packets and / or messages from the nodes. The head-end system may be, or may comprise, a server. The head-end system may be outside the mesh network, e.g. may transmit / receive form one or more nodes in the nesh- network. The head-end system may generate and / or process the data. The head-end system may be communicably coupled to a further system, such as a cloud based system, for generating and / or processing the data. In examples, the network may be a time-slotted channel hopping (TSCH) network, for example as defined by IEEE 802.15.4 In examples, the nodes may be configured to support communications modes including orthogonal frequency-division multiplexing (OFDM). One or more nodes may be configured to support communications modes based on frequency-shift keying (FSK). The step of providing the at least one seed node with the data may comprise transmitting the data from the head-end system by performing a unicast operation over the mesh network. That is, the head-end system may communicate the data to the node selected to be the seed node, e.g. directly or via one or more nodes by addressing the data to the seed node. Advantageously, this may limit an amount of data transmission on the mesh network. The head-end system may communicate the data via a root node of the mesh network. The step of providing the at least one seed node with the data may comprise transmitting, by the seed node, a request for the data and / or retrieving the data from the head-end system over the mesh network. Advantageously, the node selected as seed node may issue a request to the head- end system for the data. The head-send system may, in response, unicast the data to the MC1-033231-WO-ORD seed node, thereby limiting an amount of unnecessary or duplicate data transmission on the mesh network. The step of providing the at least one seed node with the data may comprise transmitting a request for the data and / or retrieving the data from the head-end system by the at least one seed node over a further network. For example, the node, e.g. end node, may be configured to communicate over another network, such as the internet via a wireless connection or the like. In an example, the node may be a smart-meter installed at a domestic premises, the smart meter having internet capability via household router, such as via a Wi-Fi connection or the like. The node may retrieve the data from the head-end system over the further network, e.g. over the internet. The node may request the data from the head-end system and / or the head-end system may push the data to the node. Advantageously, providing the data to the node via a further network, such as over the internet, may reduce unnecessary or duplicate data transmission on the mesh network. Each node within the subset of nodes may comprise a device or module for metering and / or controlling a resource. For example, the device may comprise circuitry and / or components for metering a consumption of a resource, and / or controlling access to the resource, such as by a service disconnect switch or the like. Each node within the subset of nodes may comprise a device, e.g. an edge device, having processing capabilities configured for communicating over the mesh network with a device of one or more other nodes in the subset. That is, each node may comprise, or may be attached to, a device known in the art as an “edge” device. In an example embodiment, each node may comprises a network radio, which may be attached directly to a metering device for metering a consumption of a resource, such as gas, electricity or water. Such edge devices may be configured to communicate directly with other nodes on the network without necessarily communicating with, or via, the head-end system or any intermediate root nodes. MC1-033231-WO-ORD That is, the edge devices may have sufficient processing and communications capability to enable a degree of autonomous operation without direct and / or continued supervision of control by the head-end system. Selection of the at least one seed node may be based on a geographical location of the at least one seed node relative to other nodes within the network. For example, the seed node may be a node that is located within a relatively dense population of nodes forming the subset. The seed node may be a node that is substantially surrounded by the nodes forming the subset. Selection of the at least one seed node may be based on address and / or identification data corresponding to the at least one seed node. The seed node may be selected based on a zip code / post code. The seed node may be selected based on a coordinate, e.g. a latitude and longitude. Selection of the at least one seed node may be based on a level of interference between the seed node and other nodes in the network. For example, the selection of the at least one seed node may be based on a Received Signal Strength Indicator (RSSI), which may be indicative of a level / quality / reliability of connectivity. Advantageously, the seed node may be selected as a node that has adequate / sufficient connectivity with one or more other nodes, thereby enabling efficient transfer of data within the subset. Selection of the at least one seed node may be based on a type and / or level of connectivity of the at least one seed node to the head-end system. For example, the seed node may be a node having internet access via a further network. In an example, the seed node may have a Wi-Fi connection to a network, enabling internet access. The type may additionally / alternatively refer to a category, such as a router, a metering device, etc. Selection of the at least one seed node may be based on a depth, e.g. a number of hops. That is, the selection of the at least one seed node may be based on, for example, a minimum distance in a mesh network from a node to a root node of the mesh network or to the head-end system. The depth may, in effect, be represented as a map. MC1-033231-WO-ORD Selection of the at least one seed node may be based on a Time-to-Live (TTL) and / or a hop-limit. For example, the selection of the at least one seed node may be based on a pre-defined hop-limit. The TTL, which may be an integer quantity, may refer to a number of hops it takes a message to get from a node (e.g. the seed node) to the root. For example, where the depth may be represented as a map, the TTL may in effect be indicative of the may map, yet taking into account any traffic in the network traffic. In effect, the TTL may be considered representative of a time it may take for one or more message to reach the headend system from a node, e.g. the selected seed node. Advantageously, while the TTL may be similar to depth in some respects, it can be more easily tracked and more easily averaged. A TTL value may, in practice, be based on a geography and / or connectivity. Selection of the at least one seed node may be based on a throughput, e.g. a throughput in a number of messages forwarded. That is, in some examples selection of the at least one seed node may be based on a tracking of how often the network chooses the particular node for message transport. Selection of the at least one seed node may be based on a neighbor list density. For example, given a lookup table of neighbors (e.g. neighboring nodes) a number of occurrences of a node and a number of occurrences of a best / optimum node may be searched. By scoring such a combination, a node may be selected as a seed node. It may be noted that the a node identified as a “best / optimum node” may be based on any one or more of the above-mentioned criteria, e.g. type, category, depth, TTL, throughout, level of interference / RSSI, address and / or identification data, a geographical location or the like. As described above, selection of the at least one seed node may be based upon at least one of several parameters, variables and / or factors. It will be appreciated that combination of one or more of the above may be implemented to select a particular seed node. The method of any preceding claim, wherein the node to be configured as the seed node is dynamically selected. MC1-033231-WO-ORD For example, a node initially selected as the seed node may be disabled in use, and another node may be selected as a seed node to temporarily or permanently replace the initially selected seed node. Selection of a node as the seed node may be made by the head-end system, such as based on an assessed suitability of a node to be a seed node, and / or based on characteristics of one or more nodes and / or based on programmable parameters, such as user setting, installation parameters or the like. A plurality of nodes in the mesh network may be selected to be configured as seed nodes for transmitting data to a subset of nodes in the mesh network. An amount (quantity) of the plurality of nodes selected as seed nodes may, for example, be based on a density of seed nodes. The density of seed nodes may, for example, refer to a geographical density of seed nodes. In some examples, an amount of seed nodes in the mesh network may be increased or decreased, e.g. dynamically increased or decreased. For example, the amount of seed nodes in the mesh network may be increased or decreased based upon a (predefined) time limit of an initial selection or distribution. That is, an initial selection or distribution of seed nodes may expire and subsequently be updated, increased, decreased or otherwise changed. In another example, the amount of seed nodes in the mesh network may be increased or decreased based upon a size of the network. The size may refer to a quantity of nodes and / or a geographical size. For example, as devices (nodes) are registered, e.g. added to the network, further nodes may be selected as seed nodes. In some examples, as devices (nodes) are registered, e.g. added to the network, existing seed nodes may be reconfigured such that they no longer operate as seed nodes. In a non-limiting example, such de-selection of seed nodes may depend upon where any such new devices which are registered on the network are located. In another example, the amount of seed nodes in the mesh network may be increased or decreased based upon a score associated with one or more regions of the network. For example, such a score may be indicated of a potential for success, e.g. successful operation as a seed node, in a particular region of the network. MC1-033231-WO-ORD In another example, the amount of seed nodes in the mesh network may be increased or decreased based upon a score associated with one or more of the seed nodes. For example, if during a network calibration process it is determined that there is an excessive amount of seed nodes, e.g. operation is ‘too good’ then a quantity of seed nodes in the mesh network may be reduced. Conversely, if during the network calibration process it is determined that there is an insufficient amount of seed nodes, e.g. operation is ‘not good enough then a quantity of seed nodes in the mesh network may be increased. As described above, selection the amount of seed nodes in the mesh network may be based upon at least one of several parameters, variables and / or factors. It will be appreciated that combination of one or more of the above may be implemented to select a particular amount of seed nodes in the mesh network. In some examples, the amount of nodes to be configured as seed nodes may be dynamically selected. The subset of nodes may be defined by a geographical location and / or characteristics of each node in the subset of nodes. For example, the subset of node may correspond to a zip code / post code region, or a defined range of latitudes and longitudes. Transmitting the data from the at least one seed node to the subset of nodes may comprise the at least one seed node performing a unicast operation to push the data to one or more neighbouring nodes. Transmitting the data from the at least one seed node to the subset of nodes may comprise the seed device hosting the data and providing the data to one or more neighbouring nodes in response to a request for the data from said one or more neighbouring nodes. Transmitting the data from the at least one seed node to the subset of nodes may comprise the at least one seed node performing a multicast operation to push the data to one or more nodes of the subset via one or more other nodes of the subset. Transmitting the data from the at least one seed node to the subset of nodes may comprise the at least one seed node prioritising transmitting the data to nodes that are without an active internet connection over transmitting the data to nodes that have an active internet connection. MC1-033231-WO-ORD The data may comprise weather forecast data. In other examples, the data may comprise firmware updates. According to a second aspect of the disclosure, there is provided a system, such as a mesh network system. The system comprises a network of nodes configured to form a mesh network. The system also comprises a head-end system. At least one node is configured as a seed node for transmitting data to a subset of nodes in the mesh network. The head-end system is configured to provide the at least one seed node with the data to be transmitted to the subset of nodes. The seed node is configured to transmit the data to the subset of nodes. The head-send system may be configured to transmit the data to the at least one seed node by performing a unicast operation over the mesh network. The at least one seed node may be configured to transmit a request for the data and / or retrieve the data from the head-end system over the mesh network. The at least one seed node may be configured to transmit a request for the data and / or retrieve the data from the head-end system over a further network. Each node within the subset of nodes may comprise a device for metering and / or controlling a resource. Each node within the subset of nodes may comprise a device having processing capabilities configured for communicating over the mesh network with a device of one or more other nodes in the subset. Selection of the at least one seed node may be based on at least one of: a geographical location of the at least one seed node relative to other nodes within the network; address and / or identification data corresponding to the at least one seed node; a level of interference between the at least one seed node and other nodes in the network; and / or a type and / or level of connectivity of the at least one seed node to the head-end system. The node to be configured as the seed node may be dynamically selected. For example, the head-end system may be configured to select the node to be configured as the seed node. The subset of nodes may be defined by a geographical location and / or characteristics of each node in the subset of nodes. MC1-033231-WO-ORD The at least one seed node may be configured to perform a unicast operation to push the data to one or more neighbouring nodes. The at least one seed node may be configured to host the data and provide the data to one or more neighbouring nodes in response to a request for the data from said one or more neighbouring nodes. The at least one seed node may be configured to perform a multicast operation to push the data to one or more nodes of the subset via one or more other nodes of the subset. The at least one seed node may be configured to prioritise transmission of the data to nodes that are without an active internet connection over transmission of the data to nodes that have an active internet connection. The data may comprise weather forecast data. The above summary is intended to be merely exemplary and non-limiting. The disclosure includes one or more corresponding aspects, embodiments or features in isolation or in various combinations whether or not specifically stated (including claimed) in that combination or in isolation. It should be understood that features defined above in accordance with any aspect of the present disclosure or below relating to any specific embodiment of the disclosure may be utilized, either alone or in combination with any other defined feature, in any other aspect or embodiment or to form a further aspect or embodiment of the disclosure. BRIEF DESCRIPTION OF DRAWINGS These and other aspects of the present disclosure will now be described, by way of example only, with reference to the accompanying drawings, wherein: Figure 1 depicts a block diagram of an example of a mesh network; Figure 2 depicts an example of a unicast operation in a mesh network; Figure 3 depicts an example of a multicast operation in a mesh network; Figure 4 depicts several examples of transferring data over a mesh network, according to embodiments of the disclosure; Figure 5 depicts a block diagram of an example node of the mesh network of Figure 4, according to an embodiment of the disclosure; and MC1-033231-WO-ORD Figure 6 depicts a method of transferring data over a mesh network, according to an embodiment of the disclosure. DETAILED DESCRIPTION OF DRAWINGS Figure 1 depicts an example of mesh network 100. The example network 100 may be a time-synchronized channel hopping (TSCH) network. The mesh network 100 is an example of a mesh network upon which the present invention may be implemented. In examples, the mesh network 100 may comprise a full mesh topology, e.g. where any node can communicate with any node within range, or a partial mesh topology with more limited or selected connectivity between nodes. The example mesh network comprises a head-end system 110. The head-end system 110 may function as a central processing system that transmits and / or receives data, streams of data, data packets and / or messages from nodes 105a - 105h of the mesh network 100, as described in more detail below. The head-end system 110 may generate and / or process the data. In examples, head-end system 110 may be communicably coupled to a further system, such as a cloud based system (not shown), for generating and / or processing the data. The example mesh network 100 comprises a root node 115. The root node 115 of the mesh network 100 may be configured for communicating with the nodes 105a-105h to perform operations such as retrieving data from the nodes 105a-105h and / or transmitting data to the head-end system 110. In some examples, the root node 115 may also operate as a node similar to other nodes 105a-105h. The root node 115 may comprises a router or gateway device. The root node 115 may be configured to transmit and receive data to / from the head-end system 110 via another network 120, such as the Internet, an intranet, or any other data communication network. Although only a single root node 115 is depicted for illustrative purposes, it will be understood that the mesh network 100 may comprise more than one root node 115. Similarly, the depicted mesh network 100 comprises multiple nodes 105a-105h. Each node 105a-105h may be an end-node. For purposes of example, only nodes 105a- 105h are depicted, but it will be understood that substantially more than seven nodes may be implemented. For example, in a mesh network of metering device, thousands, MC1-033231-WO-ORD hundreds of thousands or even millions of devices may be implemented in the mesh network. Each node 105a - 105h may comprise a device for metering and / or controlling a resource. For example, the device may comprise circuitry and / or components for metering a consumption of a resource, and / or controlling access to the resource, such as by a service disconnect switch or the like. In an example, the mesh network 100 may be associated with a utility network. In such an example, the nodes 105a – 105h may comprise circuitry and / or components for metering the resource, for determining various operating characteristics of the utility network, and / or for transmitting collected data through the mesh network 100 to the head-end system 110 via the root node 115. Furthermore, the nodes 105a-105h may be further configured to communicate with each other such that data may be exchanged between the nodes 105a-105h. That is, the nodes 105a-105h may comprise local processing capabilities, enabling a degree of autonomy over communication with other nodes in the network 100. The nodes 105a – 105h forming the mesh network 100 may be effectively provided in layers, as annoted in Figure 1. In this example, the root node 115 forms layer 0. Nodes 105a, 105b that are communicably coupled directly to the root node 115 form a first layer, “Layer 1”, of the mesh network 100. Similarly, nodes 105c – 105e that are communicably coupled to the mesh network 100 through a “Layer 1” node form a second layer, “Layer 2”, of the mesh network 100. Similarly, nodes 105f – 105h that are communicably coupled to the mesh network 100 through a “Layer 2” node form a third layer, “Layer 3”, of the mesh network 100. For data to propagate from the root node 115 to a Layer 3 of the mesh network 100 would require three “hops” of the data. In an example use case, it may be necessary for the head-end system to communicate data to some or all nodes of the network 100. In a first example, unicast transport of data across the mesh network 100 may be implemented. However, when targeting an entire network comprising a substantial quantity of nodes and where a transmission bandwidth to any particular node may be extremely limited, such unicast operations may be practically unfeasible. This is described in more detail with reference to Figure 2. MC1-033231-WO-ORD In another example, multicast transport of data may be implemented by the head- end system 110 to transmit data across the mesh network 100. However, such multicasting may be inherently inefficient over a large mesh network, as described in more detail with reference to Figure 3. An example of such a unicast operation is depicted in the example mesh network 200 of Figure 2. In this example, a head-end system communicates, via root node 210, with a plurality of nodes. It can be seen that to transmit data from the root node to a level 1 node, e.g. nodes 205a, 205b, 205c, a single ‘hop’ is performed by the data. However, for the root node 210 to transmit data to the level four end-point nodes 205g, 205h, four hops are required. Furthermore, in the example the data may by consumed by twelve nodes in the process of providing the data to the level four end-point nodes 205g, 205h. That is, the level 1 node 205a may consume the data and provide the data to a further 11 nodes, via a level 2 node 205d and two level three nodes 205e, 205f. Thus it can be seen that unicast may be an inherently inefficient means of transporting data to each endpoint node, consuming substantial bandwidth throughout the mesh network 200 and employing most or all nodes to transport the data. Such unicasting may not be suitable for dissemination of time-critical data. For completeness, an example of a broadcast operation is depicted in the example mesh network 300 of Figure 3. In this example, a head-end system communicates, via root node 310, with a plurality of nodes. In this example, the root node 310 transmits the data to all nodes within a 305a-305e transmission range 320 of the root node 310. In turn, a receiving node, e.g. a level 1 node such as node 305e, may transmit the data to all nodes 305d, 305f within a transmission range 335 of the level 1 node 305e, and so on. It can be seen that such a multicast approach may result in an amount of unnecessary or duplicate data transmission on the mesh network, and therefore may be an inefficient means of providing data to endpoint nodes. Figure 4 depicts several examples of transferring data over a mesh network 400, according to embodiments of the disclosure. MC1-033231-WO-ORD In examples, the data may comprise weather forecast data and / or firmware updates. In a first example, a node in the mesh network 400 is selected as a first seed node 405. The first seed node 405 may be configured as a seed node for transmitting data to a subset of nodes in the mesh network 400. Selection of the first seed node 405 may be based on a geographical location of the first seed node 405 relative to other nodes within the mesh network 400. For example, the first seed node 405 may be a node that is located within a relatively dense population of nodes forming the subset. The first seed node 405 may be a node that is substantially surrounded by the nodes forming the subset. In example embodiments, selection of the first seed node 405 may be based on address and / or identification data corresponding to the first seed node 405. The first seed node 405 may be selected based on a zip code / post code. The first seed node may be selected based on a coordinate, e.g. a latitude and longitude. Selection of the first seed node 405 may be based on a level of interference between the first seed node and other nodes in the network. For example, the selection of the first seed node 405 may be based on a Received Signal Strength Indicator (RSSI), which may be indicative of a level / quality / reliability of connectivity. In example embodiments, selection of the first seed node 405 may be based on a depth, e.g. a number of hops. That is, the selection of the first seed node 405 may be based on, for example, a minimum distance in the mesh network 400 from a node to a root node 210, 310 of the mesh network 400 or to the head-end system. The depth may, in effect, be represented as a map. Selection of the first seed node 405 may be based on a Time-to-Live (TTL) and / or a hop-limit. For example, the selection of the first seed node 405 may be based on a pre- defined hop-limit. Selection of the first seed node 405 may be based on a throughput, e.g. a throughput in a number of messages forwarded. That is, in some examples selection of the first seed node 405 may be based on a tracking of how often the network chooses the particular node for message transport. Selection of the first seed node 405 may be based on a neighbor list density. For example, given a lookup table of neighbors (e.g. neighboring nodes) a number of MC1-033231-WO-ORD occurrences of a node and a number of occurrences of a best / optimum node may be searched. By scoring such a combination, a node may be selected as the first seed node 405. It may be noted that the a node identified as a “best / optimum node” may be based on any one or more of the above-mentioned criteria, e.g. type, category, depth, TTL, throughout, level of interference / RSSI, address and / or identification data, a geographical location or the like. A head-end system 410 provides the first seed node 405 with the data to be transmitted to the subset of nodes. The head-end system 410 may function as a central processing system that transmits and / or receives data, streams of data, data packets and / or messages from the nodes. The head-end system 410 may generate and / or process the data. The head-end system 410 may be communicably coupled to a further system, such as a cloud based system, for generating and / or processing the data. The first seed node 405 may transmit the data, or may process the data and transmit further data based on the processed data and / or based on commands or instructions in the data. In the first example, the head-end system 410 may directly address the first seed node 405 to provide the data to the first seed node 405. Advantageously, this may limit an amount of data transmission on the mesh network 400. As can be seen in Figure 4, the first seed node may transmit the data (or processed data) from the first seed node to a subset of nodes. That is, the first seed node may receive data from the head-end system 410 and push the data (or processed data or the like) to other nodes within the mesh network 400. In some examples, providing the first seed node 405 with the data may comprise transmitting, by the first seed node 405, a request for the data and / or retrieving the data from the head-end system 410 over the mesh network 400. In yet further examples, the first seed node 405 may receive the data from the head-end 410 system over a further network. For example, the first seed node 405 may be configured to communicate over another network, such as the internet via a wireless connection or the like. In an example, the first seed node 405 may comprise a device, e.g. a smart-meter, installed at a domestic premises, the device having internet capability via household a router, such as via a Wi-Fi connection or the like. The first seed node 405 MC1-033231-WO-ORD may retrieve the data from the head-end system 410 over the further network, e.g. over the internet. The first seed node 405 may request the data from the head-end system 410 and / or the head-end system 410 may push the data to the first seed node 405. In some example, transmission of the data from the first seed node 405 to the subset of nodes may comprise the first seed 405 node prioritising transmission of the data to nodes that are without an active internet connection over transmission of the data to nodes that have an active internet connection. It can be seen that, in comparison to the unicast operation of Figure 2 or the multicast operation of Figure 3, seeding a first seed node with the data, wherein the first seed node is configured to broadcast the data to further nodes within range, may be an efficient means of transmitting data between edge-nodes compared to a unicast or multicast operation from a root node as illustrated in Figures 2 and 3. Edge-nodes may be end-points of the mesh network 400. That is, data may be transmitted to nodes without the overhead of connecting and sending data to each node in the network directly which may cause a significant overhead at the head-end 410 system. In some examples, the node to be configured as the first seed node 405 may be dynamically selected. For example, a node initially selected as the first seed node 405 may be disabled, such as powered-off, and another node in the mesh network 400 may be selected a seed node to temporarily or permanently replace the initially selected first seed node 405. In a second example, a node in the mesh network 400 may be selected as a second seed node 415. The second seed node 415 may be configured as a seed node for transmitting data to a subset of nodes in the mesh network 400. Selection of the second seed node 415 may be based on a geographical location of the second seed node 415 relative to other nodes within the mesh network 400. For example, the second seed node 415 may be a node that is located within a relatively dense population of nodes forming the subset. The second seed node 415 may be a node that is substantially surrounded by the nodes forming the subset. The head-end system 410 provides the second seed node 415 with the data to be transmitted to the subset of nodes. MC1-033231-WO-ORD In this second example, the second seed node 415 may host the data and / or a processed version of the data or data generated in response to a command on instruction within the data. The second seed node 415 may be configured to provide the data to another node in the network 400 when said other node in the network 400 request the data, e.g. transmits a request to the second seed node 415. Again, in the second example, the head-end system 410 may directly address the second seed node 415 to provide the data to the second seed node 405, advantageously limiting an amount of data transmission on the mesh network 400. In yet further examples, the second seed node 405 may receive the data from the head-end 410 system over a further network. For example, the second seed node 405 may be configured to communicate over another network, such as the internet via a wireless connection or the like. In some examples, a second seed node 425 may be transmit the data only a limited number of hops, e.g. the data may comprise further data or instructions to receiving nodes to limit a number of hops, e.g. nodes, to which the data is transmitted. It can be seen that, in comparison to the unicast operation of Figure 2 or the multicast operation of Figure 3, seeding a second seed node with the data, wherein the second seed node is configured to host the data and provide the data to further nodes upon request by the further nodes, may be an efficient means of transmitting data between edge-nodes compared to a unicast or multicast operation from a root node as illustrated in Figures 2 and 3. In some examples, the node to be configured as the second seed node 405 may be dynamically selected. In a third example, a node in the mesh network 400 may be selected as a third seed node 425. The third seed node 425 may be configured as a seed node for transmitting data to a subset of nodes in the mesh network 400. Selection of the third seed node 425 may be based on a geographical location of the third seed node 425 relative to other nodes within the mesh network 400. The head-end system 410 provides the third seed node 425 with the data to be transmitted to the subset of nodes. MC1-033231-WO-ORD In this third example, the third seed node 425 may receive the data and then broadcast, e.g. multicast or unicast, the data and / or a processed version of the data or data generated in response to a command on instruction within the received data. In some examples, the third seed node 425 may transmit the data only a limited number of hops, e.g. the data may comprise further data or instructions to receiving nodes to limit a number of hops, e.g. nodes, to which the data is transmitted. It can be seen that, in comparison to the unicast operation of Figure 2 or the multicast operation of Figure 3, seeding a third seed node 425 with the data, wherein the third seed node 425 is configured to receive and the broadcast the data, may be an efficient means of transmitting data between edge-nodes, e.g. end-points of the mesh network 400 compared to a unicast or multicast operation from a root node as illustrated in Figures 2 and 3. In some examples, the node to be configured as the second seed node 405 may be dynamically selected. Although an example network comprising three seed nodes 405, 415, 425 has been described, in other examples there may be fewer than or greater than three seed nodes. Furthermore, any combination of the three data transmission techniques may be implemented, e.g. seed then push, host or broadcast. That is, a plurality of nodes 405, 415, 425 in the mesh network 400 may be selected to be configured as seed nodes for transmitting data to a subset of nodes in the mesh network 400. An amount (quantity) of the plurality of nodes 405, 415, 425 selected as seed nodes may, for example, be based on a density of seed nodes. The density of seed nodes may, for example, refer to a geographical density of seed nodes. In some examples, an amount of seed nodes 405, 415, 425 in the mesh network 400 may be increased or decreased, e.g. dynamically increased or decreased. For example, the amount of seed nodes 405, 415, 425 in the mesh network 400 may be increased or decreased based upon a (predefined) time limit of an initial selection or distribution. That is, an initial selection or distribution of the seed nodes 405, 415, 425 may expire and subsequently be updated, increased, decreased or otherwise changed. In another example, the amount of seed nodes 405, 415, 425 in the mesh network 400 may be increased or decreased based upon a size of the network 400. The MC1-033231-WO-ORD size may refer to a quantity of nodes and / or a geographical size. For example, as devices (nodes) are registered, e.g. added to the network, further nodes may be selected as seed nodes. In some examples, as devices (nodes) are registered, e.g. added to the network, existing seed nodes may be reconfigured such that they no longer operate as seed nodes. In a non-limiting example, such de-selection of seed nodes may depend upon where any such new devices which are registered on the network are located. In another example, the amount of seed nodes 405, 415, 425 in the mesh network 400 may be increased or decreased based upon a score associated with one or more regions of the mesh network 400. For example, such a score may be indicated of a potential for success, e.g. successful operation as a seed node 405, 415, 425, in a particular region of the mesh network 400. In another example, the amount of seed nodes 405, 415, 425 in the mesh network 400 may be increased or decreased based upon a score associated with one or more of the seed nodes 405, 415, 425. For example, if during a mesh network calibration process it is determined that there is an excessive amount of seed nodes 405, 415, 425, e.g. operation is ‘too good’ then a quantity of seed nodes 405, 415, 425 in the mesh network 400 may be reduced. Conversely, if during the network calibration process it is determined that there is an insufficient amount of seed nodes 405, 415, 425, e.g. operation is ‘not good enough, then a quantity of seed nodes 405, 415, 425 in the mesh network 400 may be increased. In some examples, the amount of nodes to be configured as seed nodes 405, 415, 425 may be dynamically selected. Figure 5 depicts a block diagram of an example node 500 of the mesh network 400 of Figure 4, according to an embodiment of the disclosure. In the example, the node 500 comprises a metrology module 505. The metrology module 505 may be for metering and / or controlling a resource, such as electricity, gas, water or the like. The node 500 also comprises a device 510, e.g. an edge device, having processing capabilities configured for communicating over the mesh network with a device of one or more other nodes in the mesh network 400. That is, each node 500 may be attached to a device known in the art as an edge device. In the example embodiment, the edge device 510 comprises a processor 515, memory 520 and transceivers 525, e.g. MC1-033231-WO-ORD one or more transceivers. The processor 515, memory 520 and transceivers 525 are coupled by a bus 530, which may be any suitable switch fabric. The edge device 510 may be configured to communicate directly with other nodes on the network without necessarily communicating with, or via, the head-end system or any intermediate root nodes. That is, the edge device 510 may have sufficient processing and transceivers capability to enable a degree of autonomous operation without direct and / or continued supervision of control by the head-end system. In the example, the transceivers 525 are coupled to an antenna 545 for wireless communicating with other nodes in the network 400. In some examples, such as the example depicted in Figure 5, the transceivers 525 may be coupled to a further network 540, such as the internet via router, such as over Wi-Fi or the like. This may allow the node 500 to pull the data directly without the head- end system having to provide data via the mesh network 400. Figure 6 depicts a method of of transferring data over a mesh network according to an embodiment of the disclosure. In a first step 605, at least one node in the mesh network is selected to be configured as a seed node for transmitting data to a subset of nodes in the mesh network. For example the at least one node may comprise the first seed node 405, the second seed node 415 and / or the third seed node 425 of the mesh network 400 of Figure 4. In a second step 610, a head-end system such as the head-end system 410 of Figure 4, provides the at least one seed node with the data to be transmitted to the subset of nodes. In a third step 615, the data is transmitted from the at least one seed node to the subset of nodes. Transmission of the data may be according to the first, second and / or third examples described above with reference to the example mesh network 400 of Figure 4, e.g. seed then push, host or broadcast. Although the disclosure has been described in terms of particular embodiments as set forth above, it should be understood that these embodiments are illustrative only and that the claims are not limited to those embodiments. Those skilled in the art will be able to make modifications and alternatives in view of the disclosure, which are contemplated as falling within the scope of the appended claims. Each feature disclosed or illustrated MC1-033231-WO-ORD in the present specification may be incorporated in any embodiments, whether alone or in any appropriate combination with any other feature disclosed or illustrated herein.

[0002] MC1-033231-WO-ORD LIST OF REFERENCE NUMERALS 100 mesh network 105a-h nodes 110 head-end system 115 root node 120 further network 200 mesh network 205a-c level 1 node 205d level 2 node 205e-f level 3 node 210 root node 300 mesh network 305a-f nodes 310 root node 320 transmission range 335 transmission range 400 mesh network 405 first seed node 410 head-end system 415 second seed node 425 third seed node 500 example node 505 metrology module 510 edge device 515 processor 520 memory 525 transceivers 530 bus 540 further network

Claims

MC1-033231-WO-ORD CLAIMS 1. A method of transferring data over a mesh network (400), the method comprising: selecting at least one node (405, 415, 425) in the mesh network to be configured as a seed node for transmitting data to a subset of nodes in the mesh network; providing, from a head-end system (410), the at least one seed node with the data to be transmitted to the subset of nodes; and transmitting the data from the at least one seed node to the subset of nodes.

2. The method of claim 1, wherein selection of the at least one seed node (405, 415, 425) is based on at least one of: a geographical location of the at least one seed node relative to other nodes within the network; address and / or identification data corresponding to the at least one seed node; a level of interference between the at least one seed node and other nodes in the network; a type and / or level of connectivity of the at least one seed node to the head- end system; a minimum distance in the mesh network from the node to a root node or to the head-end system; a Time-to-Live (TTL) and / or a predefined hop-limit; a throughput of the node and / or a tracking of how often the mesh network chooses the particular node for message transport; and / or a neighbor list density, and optionally wherein the neighbor list density is based on a search of a number of occurrences of a node and / or a number of occurrences of an identified best / optimum node.

3. The method of any preceding claim, wherein the node to be configured as the seed node (405, 415, 425) is dynamically selected.MC1-033231-WO-ORD 4. The method of any preceding claim, wherein an amount of nodes selected as the at least one seed node (405, 415, 425) is based on at least one of: a density of seed nodes; a (predefined) time limit of an initial selection or distribution of the at least one seed node; a size of the mesh network; a score associated with one or more regions of the network; and / or a score associated with the at least one seed node.

5. The method of any preceding claim, wherein the amount of nodes to be configured as seed nodes (405, 415, 425) is dynamically selected.

6. The method of any preceding claim, wherein the step of providing the at least one seed node (405, 415, 425) with the data comprises transmitting the data from the head-end system (410) by performing a unicast operation over the mesh network (400).

7. The method of any of claims 1 to 6, wherein the step of providing the at least one seed node (405, 415, 425) with the data comprises transmitting, by the at least one seed node, a request for the data and / or retrieving the data from the head-end system (410) over the mesh network (400).

8. The method of any of claims 1 to 6, wherein the step of providing the at least one seed node (405, 415, 425) with the data comprises transmitting a request for the data and / or retrieving the data from the head-end system (410) by the at least one seed node over a further network (540).

9. The method of any preceding claim, wherein each node (500) within the subset of nodes comprises a module (505) for metering and / or controlling a resource.MC1-033231-WO-ORD 10. The method of any preceding claim, wherein each node (500) within the subset of nodes comprises a device (510) having processing capabilities configured for communicating over the mesh network (400) with a device of one or more other nodes in the subset.

11. The method of any preceding claim, wherein the subset of nodes is defined by a geographical location and / or characteristics of each node in the subset of nodes.

12. The method of any preceding claim, wherein transmitting the data from the at least one seed node (405, 415, 425) to the subset of nodes comprises: the at least one seed node performing a unicast operation to push the data to one or more neighbouring nodes.

13. The method of any preceding claim, wherein transmitting the data from the at least one seed node (405, 415, 425) to the subset of nodes comprises: the at least one seed node hosting the data and providing the data to one or more neighbouring nodes in response to a request for the data from said one or more neighbouring nodes 14. The method of any preceding claim, wherein transmitting the data from the at least one seed node (405, 415, 425) to the subset of nodes comprises: the at least one seed node performing a multicast operation to push the data to one or more nodes of the subset via one or more other nodes of the subset.

15. The method of any preceding claim, wherein transmitting the data from the at least one seed node (405, 415, 425) to the subset of nodes comprises: the at least one seed node prioritising transmitting the data to nodes that are without an active internet connection over transmitting the data to nodes that have an active internet connection.MC1-033231-WO-ORD 16. The method of any preceding claim, wherein the data comprises weather forecast data.

17. A system comprising: a network of nodes (400) configured to form a mesh network; and a head-end system (410); wherein at least one node is configured as a seed node (405, 415, 425) for transmitting data to a subset of nodes in the mesh network; wherein the head-end system is configured to provide the at least one seed node with the data to be transmitted to the subset of nodes; and wherein the at least one seed node is configured to transmit the data to the subset of nodes.

Images