Cross-boundary communication method for wireless mesh network

Abstract

A border node (200) is located in an overlap area of a first wireless mesh network (110) and a second wireless mesh network (120), where the second wireless mesh network (120) has a different network configuration than the first wireless mesh network (110), the border node (200) comprising a radio configured to receive a first packet from the first wireless mesh network (110) operating on a first channel; detecting a data message from the first packet; compiling the detected data message into a second packet, where the second packet has a network header including the same network source address and the same network sequence number as included in the network header of the first packet; and sending the second packet to a second wireless mesh network (120) operating on a second channel, wherein the second channel is the same as or different from the first channel.

Description

Technical Field

[0001] The present invention relates to the field of cross-border wireless communications. More specifically, various methods, devices and systems related to filtering duplicate cross-network messages in an efficient manner are disclosed herein. Background Art

[0002] Zigbee, Thread, and Bluetooth Mesh are examples of wireless protocols for IoT applications such as lighting and building automation. They provide low-latency, low-rate services that enable messages to be passed between, for example, a light switch and one or more luminaires. To enable messages to be routed correctly, each node on the wireless network is assigned a local network unicast address and can be addressed directly as an individual node or as a member of a group via a group address. Once configured, such a network is generally expected to operate autonomously.

[0003] A control system deployed in a building may include multiple Zigbee, Thread, or Bluetooth Mesh networks, each of which includes multiple electronic devices in the same room or on the same floor. By deploying separate switches / sensors / gateways in each of these networks, each network can be controlled in an independent manner. These independent networks may not communicate with each other and may also reside on different channels to reduce congestion and potential conflicts of messages. However, there may be use cases where one may want to communicate between these independent networks so that the same control commands can be applied to large groups of devices across different rooms / floors. In such scenarios, cross-border communication is required.

[0004] In a Zigbee system, cross-border communication can be achieved by using Zigbee InterPAN messages. However, a limitation of the InterPAN mechanism is that all networks participating in such communication must be on the same channel. Therefore, this solution lacks flexibility in some application scenarios.

[0005] Some silicon vendors offer a multi-network feature that allows a single device to be on two different Zigbee networks. For example, one solution from Silicon Labs with its multi-network feature allows a device to be a Zigbee router on one network and a dormant end device on another network. The networks can be on different channels, and the device with the multi-network feature time shares between the two networks. This solution can be used for cross-border communication between independent networks. A device that is part of two different networks is called a border node, and there can be multiple border nodes between two different networks.

[0006] US2014176340A1 relates to a transparent networking system for meter infrastructure, which includes a first ZigBee network provided in a first spatial area and a second ZigBee network provided in a second spatial area. The network has a power line carrier configured between the first ZigBee network and the second ZigBee network to facilitate packet-by-packet transmission of bidirectional information between the first ZigBee network and the second ZigBee network.

[0007] EP3050314A1 relates to a system for connecting smart devices, the system comprising at least two bridging devices, each bridging device being arranged relatively close to at least one of at least two smart devices arranged at different locations within a building, wherein the at least two bridging devices are connected to the smart devices via a wireless connection and are connected to each other via a broadband network. Summary of the invention

[0008] Multiple links can be created between adjacent networks via more than one border node. This helps avoid single points of failure in communication between networks. However, it also means that the same message may arrive multiple times from one network to another via different paths. If duplicate filtering mechanisms are not implemented, undesirable behavior may be observed because all incoming messages will be processed in another network. For example, when a central switch sends a command to switch a light, the light may end up in different states across networks if the same message is received multiple times in the network.

[0009] The inventors have realized that in such a multi-network system, it is beneficial to implement repeated filtering of messages via one or more border nodes. More specifically, the object of the present invention is achieved by a border node as claimed in claim 1, by a wireless communication system as claimed in claim 12, and by a method of a border node as claimed in claim 15.

[0010] According to a first aspect of the present invention, a border node is provided. A border node is located in an overlapping area of ​​a first wireless mesh network and a second wireless mesh network, wherein the second wireless mesh network has a different network configuration than the first wireless mesh network, the border node comprising: a radio configured to receive a first packet from the first wireless mesh network operating on a first frequency channel; detect a data message from the first packet; compile the detected data message into a second packet, wherein the second packet has a network header, the network header includes the same network source address and the same network sequence number as included in the network header of the first packet; and send the second packet to the second wireless mesh network operating on a second frequency channel, wherein the second frequency channel is the same as or different from the first frequency channel.

[0011] The border node is part of both the first wireless mesh network and the second wireless mesh network and is identified in the two networks by different network addresses.To reduce congestion and mutual interference, it may be beneficial to operate adjacent mesh networks on different frequency channels, such that the first frequency channel may be different from the second frequency channel.

[0012] The radio may be a single chip radio device.More preferably, the radio is enabled by a multi-network feature as described above.

[0013] For communication within the same network, duplicate filtering of broadcast messages at the network layer can be implemented by treating messages with the same source address and the same network sequence number as duplicates. In this way, duplicate messages will not reach the application layer because the protocol stack will discard duplicate packets at the network layer itself.

[0014] Border nodes can be used to forward data packets from a first network to a second or additional network. By having any two adjacent networks share at least one border node, communication across multiple Zigbee networks can be achieved. Deploying more than one border node in the overlapping area of ​​two adjacent networks can help avoid single points of failure in communication between networks. However, this also means that the same message can reach another network multiple times from one network via different paths. If a duplicate filtering mechanism is not implemented, undesirable behavior may be seen because typically all incoming messages will be processed in the network. For example, when the message is related to a command to switch a light, if the same message is received multiple times in another network, different lights may end up in different states across the network.

[0015] Therefore, a mechanism is needed to implement duplicate filtering of inter-network communications. The present invention discloses that the network source address and network sequence number remain the same as the original message from the first network, thereby avoiding processing duplicate messages from multiple border nodes. By maintaining the same network source address and the same network sequence number, all other nodes in one or more additional networks can easily identify whether the newly received packet includes a duplicate data message (such as a packet received earlier).

[0016] In a preferred embodiment, the border node is configured to have a first link group subscription and a link endpoint subscription corresponding to the first link group subscription. The first link group subscription is shared by one or more nodes in the first wireless mesh network and the second wireless mesh network; and the first packet is destined for a node belonging to the first link group.

[0017] Note that endpoints are logical extensions defined by applications that can be thought of as devices accessible through a single radio. For example, a light switch attached to a radio might be an endpoint. A dimmer attached to the same radio might be another endpoint, not a completely new application.

[0018] Nodes in the first wireless mesh network and the second wireless mesh network may have subscriptions to different link groups associated with different applications and / or functions in the system. A single node may have subscriptions to more than one link group. The same applies to border nodes, which may also have subscriptions to more than one link group. Additionally, border nodes will have link endpoint subscriptions to facilitate cross-network communications.

[0019] Advantageously, the border node has a subscription to a plurality of link groups, and the subscription to one or more of the plurality of link groups is shared by one or more nodes in the first wireless mesh network and the second wireless mesh network, and an additional first packet received by the border node from the first wireless mesh network is destined for a node belonging to at least one of the plurality of link groups.

[0020] In one option, multiple link groups may share the same link endpoint subscription, such that when a border node has link endpoint subscriptions corresponding to multiple link groups, it will forward data messages destined for any of the multiple link groups to the second wireless mesh network.

[0021] In another option, a subset of the plurality of link groups may share the same link endpoint subscription. The border node may then receive data messages destined for any of the plurality of link groups, but forward data messages destined for a link group in the link group subset to the second wireless mesh network only if it has a link endpoint subscription corresponding to the link group subset.

[0022] Thus, a link endpoint subscription may correspond to a single link group subscription, multiple link group subscriptions, or a subset of the multiple link group subscriptions that a border node has.

[0023] In one example, the first wireless mesh network and the second wireless mesh network are in accordance with the Zigbee standard.

[0024] The Zigbee standard is widely adopted in home automation and lighting control applications. The Zigbee network layer natively supports both star and tree networks as well as general mesh networking. Powerful topology control provides great flexibility in control systems, especially for reaching target nodes far away from the source node using direct links.

[0025] Preferably, the border node is configured to act as a router node in the first wireless mesh network, and to act as an end device or router in the second wireless mesh network.

[0026] Zigbee specifies three different device types: Zigbee Coordinator (ZC), Zigbee Router (ZR), and Zigbee End Device (ZED). These three devices play different roles in a Zigbee network. Zigbee Router (ZR) passes data between devices and / or coordinators. Zigbee End Device (ZED) provides only basic functionality. ZEDs are leaf nodes. They communicate only through their parent node, and unlike router devices, they cannot relay messages intended for other nodes. They do not participate in any routing. End devices rely on their parent router to send and receive messages. With respect to IEEE802.15.4, ZC and ZR are full function devices (FFD), while ZED is a reduced function device (RFD).

[0027] The border node can operate as an end device or a dormant end node in the second wireless mesh network. Ordinary end devices that do not have strict power consumption requirements can choose to have their radios turned on at all times. A dormant end device is a special kind of end device that turns off its radio when idle, which makes it a suitable choice for battery-powered devices.

[0028] In a preferred embodiment, the data message is a control command for controlling one or more nodes in the first and / or second wireless mesh network.

[0029] The control commands may be used in building automation to control sensors and actuators integrated in or co-located with one or more nodes in the first and / or second wireless mesh networks.

[0030] Advantageously, the control commands are used for lighting control, such as turning a light on / off or changing the color temperature of a light, etc. Different use cases can be enabled, such as

[0031] Used for large area lighting control

[0032] - Buildings / floors with central switches

[0033] -Circadian lighting using a single clock source

[0034] -Light control for horticulture

[0035] -Automated demand response

[0036] - Emergency test trigger and result readout

[0037] -Energy report from the drive

[0038] For local lighting control

[0039] -Control a subset of rooms in a large space

[0040] -Corridors linked with motion detection in nearby rooms.

[0041] As a detailed example, it may be desirable to have a central switch that lets a user turn off all lights in a building. Without such a switch, the user would have to go to each room / floor individually and use the dedicated switch for the lights in that room.

[0042] In other examples, it may be necessary to read the energy consumption of all networks in the area by connecting to only one of the networks, or to check the status of emergency drives in a building by connecting to only one network instead of connecting separately to the network where the emergency drives are located.

[0043] In another example, it may be desirable to send real-time information to all luminaires for synchronization of scheduling behavior.

[0044] In all of these scenarios, it is beneficial to allow the same control commands to propagate across multiple networks to achieve a unified control effect.

[0045] Advantageously, the source address is the network address of the first node initiating the control command.

[0046] The first node is located in a first wireless mesh network.

[0047] For wireless mesh networks, the network address may also be referred to as a local identifier, short address, or node address. As an example, a Zigbee network uses a 16-bit short address to uniquely identify a specific node within the network. For another type of short-range wireless communication network, the length of the network address may be different.

[0048] Lighting systems are becoming increasingly wirelessly connected for both professional and domestic use cases. Devices in these wirelessly connected systems communicate using either standardized or proprietary protocols. Zigbee is a popular wireless mesh network protocol that is widely used in many products.

[0049] In one example, the first node is a proxy node, a gateway, or a central switch.

[0050] The control command may be initiated by a central controller of a system that includes more than one wireless mesh network. The central controller may be a proxy node, a gateway, or a central switch. For example, in a gateway-less system, there may also be a situation where a proxy node receives a control message according to another communication protocol and injects the control message into the wireless mesh network. In one example, the proxy node may receive the control message via a BLE link and then inject the message into the Zigbee network.

[0051] In another example, the first node is a green power device.

[0052] The Zigbee Green Power protocol is an end-to-end open standard that allows ultra-low power devices, called Green Power Devices (GPDs), to operate on a Zigbee network. It allows these devices to reliably send messages to destinations in a mesh network that may be far beyond the direct communication range of these ultra-low power devices. Such ultra-low power devices are typically based on energy harvesting technology. Without the need for power supply or battery replacement, Zigbee Green Power devices can be placed almost anywhere, especially in places where wiring is difficult. Therefore, green power technology greatly improves the flexibility of IoT connections.

[0053] Advantageously, the first packet is a Zigbee Cluster Library Green Power (ZCL GP) command or a ZCL GP notification.

[0054] The Zigbee Cluster Library (ZCL) is defined according to functional domains such as General, Closures, HVAC, and Lighting. Clusters from these functional domains are used in the Zigbee Common Profile to produce descriptions of devices such as dimmer lights, dimmer switches, or thermostats.

[0055] Advantageously, the second packet is a Zigbee Cluster Library (ZCL) command translated from a Zigbee Cluster Library Green Power (ZCL GP) notification.

[0056] Instead of transmitting ZCL GP notifications directly to the second mesh network, the border node can send translated ZCL commands to the second network. The advantage of this approach is that traditional Zigbee nodes will be able to receive ZCL commands and the second network does not require green power commissioning.

[0057] According to a second aspect of the present invention, a wireless communication system is provided. A wireless communication system comprises: a first wireless mesh network comprising a first plurality of nodes; a second wireless mesh network comprising a second plurality of nodes, wherein the second wireless mesh network has a different network configuration than the first wireless mesh network; and a boundary node located in an overlapping area of ​​the first wireless mesh network and the second wireless mesh network according to the present invention.

[0058] The wireless communication system may include more than two mesh networks. For example, there may be another mesh network located next to the second mesh network, and one or more border nodes located in the overlapping area of ​​the second mesh network and the other mesh network are configured to forward a data message received in the second network to the other network. When the data message originates from the first mesh network, the network source address and network sequence number of the packet including the data message remain the same when propagating from the first mesh network to the second mesh network and from the second mesh network to the other mesh network.

[0059] Advantageously, the border node is configured to have a first link group subscription and a link endpoint subscription corresponding to the first link group subscription. The first link group subscription is shared by one or more nodes in the first wireless mesh network and the second wireless mesh network; and the first packet is destined for a node belonging to the first link group.

[0060] In another setting, the border node has a subscription to multiple link groups, and the subscription to one or more of the multiple link groups is shared by one or more nodes in the first wireless mesh network and the second wireless mesh network, and an additional first packet received by the border node from the first wireless mesh network is destined for a node belonging to at least one of the multiple link groups.

[0061] According to a third aspect of the present invention, a method is provided. According to a method of a border node of the present invention, the method comprises the following steps: receiving a first packet from a first wireless mesh network operating on a first frequency channel; detecting a data message from the first packet; compiling the detected data message into a second packet, wherein the second packet has a network header, the network header includes the same network source address and the same network sequence number as those included in the network header of the first packet; and sending the second packet to a second wireless mesh network operating on a second frequency channel, wherein the second frequency channel is the same as or different from the first frequency channel. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In the drawings, like reference numerals generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention.

[0063] Figure 1 A wireless communication system comprising a plurality of mesh networks connected via border nodes is illustrated;

[0064] Figure 2 An example of multi-network communication is illustrated;

[0065] Figure 3 Another example of multi-network communication is illustrated;

[0066] Figure 4 Another example of multi-network communication is illustrated;

[0067] Figure 5 illustrates an example of a small cluster within a large multi-network region; and

[0068] Figure 6 A flow chart showing a method for a boundary node. DETAILED DESCRIPTION

[0069] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments. After reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize the application of these concepts not specifically mentioned herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0070] Figure 1 A wireless communication system 100 is illustrated that includes multiple mesh networks 110, 120, 130 connected via a border node 200. Each mesh network 110, 120, 130 includes multiple nodes or devices 200, 300. Different mesh networks 110, 120, 130 may operate on different frequency channels to reduce the chance of congestion or mutual interference between adjacent networks.

[0071] There may be a proxy node, central switch, gateway or controller 400 that is configured to send data messages or control signals of nodes 200, 300 across more than one mesh network 110, 120, 130. A border node is a node located in an overlapping area between two adjacent networks, which is part of both networks and can be identified in the two networks via different network addresses. A border node located in an overlapping area of ​​mesh networks 110 and 120 is configured to forward data messages originating from a first node (such as a gateway, switch node or proxy device 400) in the first network 110 to the second network 120. Another border node located in an overlapping area of ​​mesh networks 120 and 130 is configured to forward data messages originating from the first network 110 from the second network 120 to the further network 130.

[0072] Different embodiments of the present invention are further described in detail in the context of a central switch 400 that communicates across multiple wireless mesh networks 110, 120, 130. As examples, the central switch 400 can be a conventional Zigbee switch, a Zigbee Green Power Switch, or a proxy device. Similar methods can be applied to different use cases, such as energy reading or configuring luminaires across networks. Communication across multiple Zigbee networks can be achieved by having any two adjacent networks share at least one boundary node. Special Zigbee groups and endpoints are defined for cross-border communication, which are called link groups and link endpoints, respectively.

[0073] Multiple nodes 200 may have subscriptions to different link groups associated with different applications and / or functions in the system. A single node may have subscriptions to more than one link group. This also applies to border nodes 200, which may also have subscriptions to more than one link group. Additionally, border nodes 200 may have link endpoint subscriptions to facilitate cross-network communication. Endpoint subscriptions may correspond to a subset of a single link group subscription, multiple link group subscriptions, or multiple link group subscriptions that border nodes 200 may have.

[0074] As an example, a border node may subscribe to multiple link groups, and the multiple link groups share the same link endpoint subscription.When a border node receives a data message destined for any of the multiple link groups, it will forward the data message to another wireless mesh network 120,130.

[0075] In another example, for multiple link groups to which the border node 200 has a subscription, a subset of the multiple link groups may share the same link endpoint subscription. The border node 200 may then receive data messages destined for any of the multiple link groups, but forward data messages destined for link groups in the link group subset to another wireless mesh network 120, 130 only if it has a link endpoint subscription corresponding to the link group subset.

[0076] With respect to the lighting control system, each node across the network can have a link group and light endpoint subscription for normal light control operations. On the boundary nodes, link groups and link endpoint subscriptions are added in addition to the light endpoints. In the following example, more details of how these link groups and link endpoints are used for cross-boundary communication are disclosed.

[0077] Figure 2 An example of multi-network communication is illustrated. In this example, the A1 switch 400 that initiates the control message is a conventional Zigbee switch. For multiple nodes 300 and border nodes 200 in the system, as recorded in the protocol stacks of the nodes 300, 200, the light endpoint subscription is represented by 1 and the link endpoint subscription is represented by 2. In the figure, the link group subscription is represented by 0xABCD. The transmission of data messages is represented by arrowed lines and the arrows are used to indicate the direction of transmission. Depending on the configuration of a particular network, data messages can be embedded in different data packets. Depending on the operating frequencies of different networks, the border node can also be configured to switch from the first channel of the first mesh network to the second channel of the second mesh network for forwarding data messages.

[0078] like Figure 2As illustrated in , when a data message or a Zigbee message is sent from switch A 1400 to a link group, all endpoints 200, 300 registered with the group are notified. This means that in the case of border node A 4200, the message is also received on the link endpoint. When the border node 200 receives the message on the link endpoint, it switches to another network B 1120 and broadcasts the message as is on the other network. The network source address and sequence number remain the same as the original message from the first network 110, thereby avoiding processing duplicate messages from multiple border nodes. In other words, in order to avoid forwarding duplicate messages by different border nodes located in the overlapping area of ​​two adjacent networks, the border node is configured to keep the second packet to be transmitted to the other mesh network with a network header, which includes the same network source address (e.g., src 0x1234) and the same network sequence number (e.g., seq:11) as included in the network header of the first packet received from the first mesh network. By maintaining the same network source address and the same network sequence number, all other nodes in one or more additional networks can easily identify whether a newly received packet includes a duplicate data message (such as a packet that was received earlier).

[0079] Figure 3 An example of multi-network communication in a system including a green power device is shown. In the case where the central switch is a green power device, the main concept of cross-border communication remains the same. Figure 3 As shown in , the Green Power Switch first sends out a Green Power Data Frame (GPDF), which is picked up by a nearby Green Power Proxy (GPP). The GPP encapsulates the GPDF in a ZCL message and sends it as a ZCL GP Notification (multicast to group 0xABCD) to all Green Power Receivers (GPS). The GPS then uses its translation table entry to convert the incoming ZCL GP Notification into a ZCL Switch or On / Off command and passes it to the registered endpoint on the node.

[0080] Since the border node has an additional registration for the link endpoint, when a message is received on the link endpoint, the border node simply switches to the other mesh network 120 and multicasts the same ZCL GP Notification with the same network source address and sequence number to the second network 120 group. In this way, the border node acts as a GPP for all other nodes on the second network 120. All GPSs on the second network 120 will process the incoming ZCL GP Notification as they normally would for messages originating from a "real" proxy.

[0081] Figure 4Another example of multi-network communication in a system including a green power device is illustrated. In another variation of the green power switch 400 case, the border node 200 can inject the translated ZCL command into the second network 120 instead of injecting the ZCL GP notification. Again, the network source address used here will belong to the green power switch 400 that initiated the command, not to the border node 200. The advantage of this approach is that no green power commissioning is required on all the other networks 120. Figure 4 The message flow of this approach is shown.

[0082] In potential application scenarios, the system may include multiple small clusters / mesh networks within a large multi-network area. As an example, there may be a central switch 400 controlling all lights on one floor, and in parallel, there may be some smaller partitions in the system with additional control mechanisms, such as several rooms with motion sensors linked to corridors. This can be achieved by maintaining a white list of link groups on the border node 200, so that cross-border communications are only related to a subset of multiple link groups by having a link endpoint registration corresponding to a subset of link groups. The border node 200 can then receive data messages to any link group in the multiple link groups, but only forwards data messages to the link groups in the link group subset to another wireless mesh network 120, 130 when it has a link endpoint subscription corresponding to the link group subset.

[0083] Figure 5 Such an example is shown, the area within the dashed line represents a small cluster within a large multi-network area. This could be a central switch ZCL that controls all lights on one floor and a few smaller partitions of rooms with motion sensors linked to corridors. This is achieved by maintaining a whitelist of link groups on the border nodes as shown in the figure. Arrows indicate the links and direction of message flow from the border nodes. Group 0xAAAA (abbreviated A) is used for global multi-network communication and 0xBBBB (abbreviated B) is used for corridor link use cases.

[0084] Therefore, maintaining a whitelist of groups rather than using a single group can help

[0085] Control lights in smaller sections of a building

[0086] Limit control messages to this smaller partition

[0087] · Use existing multi-network links for cross-network communication.

[0088] Figure 6A flow chart of a method 600 of a border node 200 is shown. The method 600 includes the following steps of the border node 200: receiving a first packet from a first wireless mesh network 110 operating on a first frequency channel in step S601; detecting a data message from the first packet in step S602; compiling the detected data message into a second packet in step S603, wherein the second packet has a network header, the network header including the same network source address and the same network sequence number as included in the network header of the first packet; and sending the second packet to a second wireless mesh network 120 operating on a second frequency channel in step S604, wherein the second frequency channel is the same as or different from the first frequency channel.

[0089] The method according to the present invention can be implemented on a computer as a computer-implemented method, or in dedicated hardware, or in a combination of both.

Claims

1. A border node (200) located in an overlapping area of ​​a first wireless mesh network (110) and a second wireless mesh network (120), wherein the second wireless mesh network (120) has a different network configuration than the first wireless mesh network (110), the border node (200) comprising: The radio is configured to: - receiving a first packet from said first wireless mesh network (110) operating on a first frequency channel; - detecting a data message from said first group; - compiling the detected data message into a second packet, wherein the second packet has a network header including the same network source address and the same network sequence number as included in the network header of the first packet; and - sending the second packet to a second wireless mesh network (120) operating on a second frequency channel, wherein the second frequency channel is the same as or different from the first frequency channel.

2. The border node (200) according to claim 1, wherein the border node (200) is configured to have: - first link group subscription, and - a link endpoint subscription corresponding to the first link group subscription; wherein the first link group subscription is shared by one or more nodes (300) in the first wireless mesh network (110) and the second wireless mesh network (120); And the first packet is destined for a node (300) belonging to the first link group.

3. The border node (200) according to claim 2, wherein the border node (200) has a subscription to multiple link groups, and the subscription to one or more link groups in the multiple link groups is shared by one or more nodes (300) in the first wireless mesh network (110) and the second wireless mesh network (120), and the additional first packet received by the border node (200) from the first wireless mesh network (110) is destined for a node (300) belonging to at least one link group in the multiple link groups.

4. The border node (200) according to any one of the preceding claims, wherein the first wireless mesh network (110) and the second wireless mesh network (120) are in accordance with the Zigbee standard.

5. The border node (200) according to any one of the preceding claims, the border node (200) being configured to act as a router node in the first wireless mesh network (110) and to act as an end device or router in the second wireless mesh network (120).

6. The border node (200) according to any one of the preceding claims, wherein the data message is a control command for controlling one or more nodes (300) in the first and / or the second wireless mesh network (120).

7. The border node (200) according to claim 6, wherein the source address is a network address of a first node that initiated the control command.

8. The border node (200) according to claim 7, wherein the first node is a proxy node, a gateway or a central switch.

9. The border node (200) of claim 7, wherein the first node is a green power device.

10. The border node (200) of claim 9, wherein the first packet is a Zigbee Cluster Library Green Power (ZCL GP) command or a ZCL GP notification.

11. The border node (200) of claim 9, wherein the second packet is a Zigbee Cluster Library (ZCL) command translated from a Zigbee Cluster Library Green Power (ZCL GP) notification.

12. A wireless communication system (100), comprising: - a first wireless mesh network (110) comprising a first plurality of nodes (300), - a second wireless mesh network (120) comprising a second plurality of nodes (300), wherein the second wireless mesh network (120) has a different network configuration than the first wireless mesh network (110), and - A border node (200) as claimed in any of the preceding claims 1-11, located in an overlapping area of ​​the first wireless mesh network (110) and the second wireless mesh network (120).

13. The wireless communication system (100) according to claim 12, wherein the border node (200) is configured to have: - first link group subscription, and - a link endpoint subscription corresponding to the first link group subscription; wherein the first link group subscription is shared by one or more nodes (300) in the first wireless mesh network (110) and the second wireless mesh network (120); And the first packet is destined for a node (300) belonging to the first link group.

14. The wireless communication system (100) of claim 13, wherein the border node (200) has a subscription to a plurality of link groups, and the subscription to one or more of the plurality of link groups is shared by one or more nodes (300) in the first wireless mesh network (110) and the second wireless mesh network (120), and an additional first packet received by the border node (200) from the first wireless mesh network (110) is destined for a node (300) belonging to at least one of the plurality of link groups.

15. The method of the border node (200) of claim 1, the method (600) comprising the steps of a radio included in the border node (200): - receiving (S601) a first packet from a first wireless mesh network (110) operating on a first frequency channel; - detecting (S602) a data message from said first group; - compiling (S603) the detected data message into a second packet, wherein the second packet has a network header, the network header comprising the same network source address and the same network sequence number as included in the network header of the first packet; and - sending (S604) the second packet to a second wireless mesh network (120) operating on a second frequency channel, wherein the second frequency channel is the same as or different from the first frequency channel.

Images