System and method for setting up a mesh network using a universal gateway node

By introducing mesh processors and supporting mesh access points in wireless gateway devices, establishing mesh connections, solving the problem of coverage and available capacity limitations of wireless gateway devices, achieving wider coverage and higher data throughput quantity.

CN113347651BActive Publication Date: 2024-11-22WIRELESS COMM & TECH CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110664560.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2017-01-20
Filing Date
2018-01-19
Publication Date
2024-11-22
Estimated Expiration
2038-01-19

AI Technical Summary

Technical Problem

Existing wireless gateway devices have limitations in terms of coverage and available capacity, especially under the IEEE 802.11ac standard, the coverage and available capacity of users away from gateways will be reduced, resulting in the impact of the entire wireless network.

Method used

Using a universal repeater (UR) or support mesh access point (MAP) combined with gateway devices, expand network coverage and improve data throughput by establishing mesh connections, reducing the connection complexity between different chipset platforms .

Benefits of technology

Improve network coverage and data throughput through mesh connections, reduce bottlenecks, achieve wider coverage and higher capacity utilization, and reduce the complexity of mesh setup and maintenance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113347651B_ABST
    Figure CN113347651B_ABST
Patent Text Reader

Abstract

A method for use in a mesh gateway of a mesh wireless local area network (WLAN), the method comprising: upon detecting a trigger event, sending a message to a mesh access point (MAP) indicating detection of a trigger event; establishing an AP-to-station (STA) mode connection with the MAP; sending a mesh advertisement message to the MAP including an indication that the mesh gateway is an alternate mesh gateway; receiving configuration information associated with the mesh WLAN from the MAP in STA mode; and establishing a mesh mode connection with the MAP using the configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of an invention patent application with an application date of January 19, 2018, application number 201880013026.6, and invention name “System and method for setting up a mesh network using a universal gateway node”.

[0002] Cross-references to related applications

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 448,718, filed January 20, 2017, the contents of which are incorporated herein by reference. Background Art

[0004] A mesh network is a communication network in which each node can communicate with one or more other nodes directly or through other nodes in the network. A hybrid mesh network is a mesh network in which all or some of the nodes have more than one interface to communicate with each other, where each interface can utilize a different communication medium.

[0005] Wireless networks are often used to give the last hop entry to a network. For example, consider a home network, where a fiber optic line brings the Internet to the home, and mobile stations (i.e. laptops, desktop computers, Internet appliances, mobile phones, etc.) connect to the network via wireless access points. Cellular systems are also examples of such networks, where the backhaul infrastructure utilizes high-capacity connections between base stations, and low-capacity end-user terminals connect to access points (APs) or base stations (APs) via their wireless interfaces. In such a network, a wireless access point can be considered as an entry point for wireless end-user terminals to access the Internet (or the network itself).

[0006] The disadvantage of this network structure is the limited wireless coverage of both the wireless access points and the end-user terminals. In a cellular system, the area to be covered is divided into cells (hence the name cell), each cell is separated in the frequency domain, and each cell is connected to other cells by a high-capacity dedicated wired or wireless connection. In a wireless network where the entry point to the network is provided by a Wi-Fi (based on the IEEE 802.11 protocol) AP, the coverage is limited not only due to the transmit power limitations of the AP, but also due to the transmit power limitations of the mobile end users.

[0007] In a typical home installation, a gateway (GW) device acts as an entry point for end-user terminals to the outside world. A GW device is typically a modem device that can modulate and demodulate signals from a landline or fiber optic cable, enabling end users to access the Internet. A GW device typically includes an Ethernet switch and a Wi-Fi interface. In a typical implementation, the end user is connected to the Internet via a wireless interface provided by the gateway device. The gateway device is typically provided, maintained, and controlled by an Internet Service Provider (ISP). ISPs provide gateway devices to their subscribers as part of the Internet services they provide.

[0008] The gateway devices provided by ISPs are usually equipped with the latest wireless technology, allowing them to keep up with the increasing number of wireless clients in the home and also with the available capacity provided by the broadband backbone network. Note that with the introduction of the IEEE802.11ac standard, multi-gigabit per second Wi-Fi communication has become possible. Gateway devices are high-capacity devices with increasing capacity on both the backbone side and the end-user side. However, although the end-user side (i.e., the wireless entrance of the gateway) is improving in terms of the maximum speed it can send, the coverage range of these gateway devices has not improved. In fact, the high speed that IEEE 802.11ac can achieve can only be achieved near the gateway device. Users far away from the gateway will not only be affected, but also reduce the total available capacity, causing the entire wireless network to be affected. Therefore, there is a need for improved gateway devices and other network nodes with extended operating ranges. Summary of the invention

[0009] One possible option for improving network coverage and also for optimal utilization of available wireless medium capacity is to use a universal repeater (UR) together with a gateway device. A UR is a device with concurrent AP and station (STA) capabilities. A UR connects to a gateway (or AP) via its STA interface and provides wireless services to wireless clients through its AP interface. That is, from the perspective of the gateway (or AP) to which the UR is connected, the UR is a station; and from the perspective of a wireless station, the UR is an AP that can be associated with it.

[0010] Another possible option for improving network coverage is to use mesh access points (MAPs), which are connected in a mesh network together with a gateway. Although MAPs have significant performance advantages over URs, MAPs are still not widely used in many networks due to the complexity involved in setting up, configuring, and maintaining mesh networks. In some aspects, it may be difficult to establish a mesh network between devices using different chipset platforms due to differences between protocol stack implementations in different chipset platforms. Therefore, there is a need for an improved design and implementation of a mesh network characterized by reducing the complexity of establishing connections between nodes using different chipset platforms.

[0011] According to various aspects of the present disclosure, a method is provided, including: sending a first notification message by at least one processor, the first notification message being sent to a first device; receiving a request message from the first device by at least one processor; sending a response message to the first device by at least one processor; establishing a first mesh connection with the first device by at least one processor; receiving one or more messages originated from a site in a local area network by at least one processor, the one or more messages being received from the first device via the first mesh connection, and the one or more messages having a destination outside the local area network; and forwarding the one or more messages to a destination outside the local area network by at least one processor.

[0012] According to various aspects of the present disclosure, a method for use in an IEEE 802.11 device is provided, the method comprising: wirelessly connecting, by the device, to a gateway that is part of a wireless local area network (WLAN), the gateway being configured to operate as an access point (AP) of the WLAN and bridge the WLAN to the Internet; receiving, by the device, an advertisement message from the gateway, the advertisement message including a network identifier (NI) of a subnet of the WLAN, the subnet including the gateway and a first node, the first node also being configured to operate as an AP of the WLAN; sending, by the device, a request message to join the subnet to the gateway; receiving, by the device, a response message from the gateway, the response message including a confidential credential for connecting to the subnet; establishing, by the device, a first connection to the first node based on the confidential credential and the NI, and starting to operate as an AP of the WLAN, the first connection being a single-hop data link layer connection; receiving, by the device, data originating from a station (STA) connected to the WLAN via the device, the data having a destination outside the WLAN; and forwarding, by the device, the data to the first node for forwarding to a destination outside the gateway and the WLAN.

[0013] According to various aspects of the present disclosure, an apparatus is provided, comprising: a transmitter; a receiver; and a processing circuit operably coupled to the transmitter and the receiver, wherein: the receiver is configured to receive an announcement message from a gateway device, the gateway device is arranged to operate as an access point (AP) of a wireless local area network (WLAN) and bridge the WLAN to the Internet, the announcement message includes a network identifier (NI) of a subnet of the WLAN, the subnet includes the gateway device and a first node, the first node is also configured to operate as an AP of the WLAN, the transmitter is configured to send a request message to join the subnet to the gateway device, the receiver is further configured to receive a response message including a confidential credential for connecting to the subnet from the gateway device, the processing circuit is configured to establish a first connection to the first node based on the confidential credential and the NI, and start operating as an AP of the WLAN, the first connection is a single-hop data link layer connection, the receiver is further configured to receive data originating from a station (STA) connected to the WLAN via the apparatus, the data having a destination outside the WLAN, and the transmitter is further configured to send the data to the first node for transmission to the destination outside the gateway device and the WLAN.

[0014] According to various aspects of the present disclosure, a method for use in a mesh gateway of a mesh wireless local area network (WLAN) is provided, the method comprising: upon detecting a trigger event, sending a message to a mesh access point (MAP) indicating detection of a trigger event; establishing an AP-to-station (STA) mode connection with the MAP; sending a mesh advertisement message to the MAP including an indication that the mesh gateway is an alternative mesh gateway; receiving configuration information associated with the mesh WLAN from the MAP in STA mode; and establishing a mesh mode connection with the MAP using the configuration information.

[0015] According to various aspects of the present disclosure, a mesh gateway is provided, including: a processor configured to detect a trigger event; a transmitter configured to send a message indicating that a trigger event has been detected to a mesh access point (MAP); the processor and the transmitter are configured to establish an AP-to-station (STA) mode connection with the MAP; the transmitter is configured to send a mesh notification message including an indication that the mesh gateway is an alternative mesh gateway; a receiver is configured to receive configuration information associated with the mesh WLAN from the MAP in STA mode; and the processor and the transmitter are configured to establish a mesh mode connection with the MAP using the configuration information. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described below are for illustration purposes only. The drawings are not intended to limit the scope of the present disclosure. In various embodiments, similar reference numerals shown in the drawings represent the same parts.

[0017] Figure 1A is a diagram of an example of a network according to aspects of the present disclosure;

[0018] Figure 1B is a diagram of an example of a network according to aspects of the present disclosure;

[0019] Figure 2A is a diagram of an example of an access point (MAP) module with mesh support according to aspects of the present disclosure;

[0020] Figure 2B depicts examples of forwarding rules employed by a mesh routing sub-processor according to aspects of the present disclosure;

[0021] Figure 2C According to the combination of various aspects of the present disclosure Figure 2A FIG. 1 is a diagram of an example of a MAP module supporting a mesh access point gateway (MAPGW);

[0022] Figure 2D According to the combination of various aspects of the present disclosure Figure 2A FIG. 1 is an example of an access point of a MAP module;

[0023] Figure 3A is a diagram of an example of a communication network according to aspects of the present disclosure;

[0024] Figure 3B is a sequence diagram of a process according to aspects of the present disclosure;

[0025] Figure 4 is a diagram illustrating an example of a process according to aspects of the present disclosure;

[0026] Figure 5 is a diagram illustrating an example of a process according to aspects of the present disclosure;

[0027] Figure 6 is a diagram illustrating an example of a process according to aspects of the present disclosure;

[0028] Figure 7 is a sequence diagram of an example of a process according to aspects of the present disclosure;

[0029] Figure 8 is a flowchart of an example of a process according to aspects of the present disclosure;

[0030] Fig. 9 It is to show that according to various aspects of the present disclosure Figure 3A Figure 2 shows a diagram of a network before and after a gateway in the network is replaced;

[0031] Fig.10 is a flowchart of an example of a process according to aspects of the present disclosure;

[0032] Fig.11 is a diagram of an example of a communication network according to aspects of the present disclosure; and

[0033] Fig.12 is a diagram of an example of a communication network in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0034] According to various aspects of the present disclosure, an improved mesh-enabled access point (MAP) is disclosed. In addition, a mesh processor capable of introducing mesh capabilities into a universal gateway device is disclosed. The mesh processor can be implemented in hardware (e.g., by using hardwired logic), software (e.g., by using one or more processor executable instructions), and / or a combination of hardware and software. When the mesh processor is executed by a universal wireless gateway device, the universal gateway device becomes a MAP-enabled gateway that handles mesh capabilities and is capable of connecting to other MAPs to form a mesh network. From the end user's perspective, the network may appear to consist of a single access point (AP), while the actual network may include multiple APs (e.g., one or more MAPs and MAP-enabled GW nodes). The network may be more advantageous than a network that uses a universal repeater (UR) to extend the range because it may have fewer bottlenecks and higher data throughput.

[0035] Figure 1A 1 is a diagram of an example of a communication network 100A that uses universal repeaters to extend the range of the network according to aspects of the present disclosure. The communication network 100A includes a gateway (GW) 102 and universal repeaters (URs) 112-116, which are used to extend the range of the GW 102. The network 100A is organized according to a tree topology, wherein the GW 102 is a root node, and the URs 112-116 are parent nodes of stations (STAs) 122-128. More specifically, URs 112 and 114 and STA 128 are directly connected to the GW 102. In addition, STA 122 is connected to the GW 102 via UR 112, UR 116 is connected to the GW 102 via UR 112, STA 124 is connected to the GW 102 via UR 114, and STA 126 is connected to the GW 102 via UR 116 and UR 116. As a result of this arrangement, all outgoing traffic from the STAs 122 - 128 must traverse the GW 102 , which may result in lower end-to-end throughput.

[0036] In some applications, URs are not the best choice for extending the range of a wireless GW. For example, consider the case where two URs are directly connected to a GW. Furthermore, consider a mobile station connected to one of the URs and attempting to stream video provided by a digital video recorder (DVR) connected to another UR. In this topology, packets must pass through the gateway because there is no direct connection between the URs, although they may be close enough to each other to allow direct communication (e.g., see Figure 1A , UR 116 cannot communicate directly with UR 114, but must communicate via UR 112 and GW 102). This limitation (lack of direct communication capability between URs) is inherent in the operation of the URs.

[0037] Figure 1B 1 is a diagram of an example of a communication network 100B according to aspects of the present disclosure, in which mesh-enabled access points (MAPs) are used instead of URs to extend the network range. MAPs are superior to URs because MAPs can form wireless connections between each MAP, thereby improving the data throughput of the network 100B. The network 100B includes MAPs 142-148 and a mesh-enabled access point gateway (MAP GW) 152. Figure 1B As shown, MAPs 142-148 have active connections with each other. These connections are referred to herein as "mesh connections". MAPs 142-148 are able to utilize these mesh connections for shortest path packet routing without always having to traverse GW 152 to communicate between different MAPs in communication network 100B. It should be noted that the routing discussed here is data link layer (i.e., layer 2) routing and should not be confused with network layer routing.

[0038] Figure 2A 2 is a diagram of an example of a mesh processor 200 according to aspects of the present disclosure. The mesh processor 200 can be implemented as software, hardware, and / or a combination of software and hardware. The mesh processor can be implemented in a remote server and can send its commands from the remote server to a MAP device via a communication interface. The mesh processor 200 can be integrated into a universal gateway and / or a wireless station (e.g., a wireless client). When the mesh processor 200 is integrated into a universal gateway, the gateway can become a MAP gateway.

[0039] In some embodiments, the mesh processor 200 may include one or more of an event handler 201, a mesh control subprocessor 203, a mesh routing subprocessor 204, custom daemons 205-206, an inter-MAP communication subprocessor 207, an abstraction layer 208, and an interface-specific driver 214. The mesh control subprocessor 203 is responsible for the establishment and maintenance of the mesh network. The mesh routing subprocessor 204 is responsible for packet routing in the data link layer. The mesh processor 200 may run several custom daemons, such as daemons 205, 206. A daemon is a software program that runs as a background process, rather than under the direct control of an interactive user. The custom daemons 205, 206 may run in a separate subprocessor, or more generally may be run by the mesh processor 200. In one embodiment, the client guidance daemon may be implemented as a custom subprocessor. In addition, the dynamic channel selection daemon may be used as a custom subprocessor. The event handler 201 binds events and commands generated by subprocessors such as the mesh control subprocessor 203, the mesh routing subprocessor 204, and the custom daemon (if any) to the interface-specific driver through the abstract layer 208. Similarly, events generated by the interface-specific driver 214 are passed to the subprocessors 202-207 through the event handler 201 via the abstract layer 208. In another embodiment, the event handler 201 can bind commands and events between the subprocessors 202-207 and the interface-specific driver 214 without using the abstract layer 208. The abstract layer 208 provides a common messaging platform between the interface-specific driver 214 and the subprocessors 202-207. Examples of interface-specific drivers are physical layer wireless air interface drivers based on IEEE 802.11 (e.g., 2.4 GHz wireless drivers, 5 GHz wireless drivers), power line communication (PLC) drivers, multiplexing over coaxial (MoCA) drivers, Ethernet drivers, etc. A driver hook 209 is a control point within the driver code that can dynamically (on the fly) change the operation of the code based on external input. Additionally, a driver hook 209 is a monitoring point within the driver code that facilitates monitoring the state of various variables during runtime. The above sub-processors may be implemented as different fabric processors or components, or more likely as software routines running on the mesh processor 200 in the gateway device.

[0040] To further illustrate the above situation, consider the wireless protected setup (WPS) event in the 5GHz wireless interface. Typically, the command associated with the WPS process is start, and the events associated with the WPS process are (1) timeout, (2) success, and (3) failure. The mesh control subprocessor 203 can trigger the WPS start command in the 5GHz wireless driver through the abstraction layer 208. In addition, the mesh control subprocessor 203 can monitor the timeout, success, and / or failure events of the corresponding wireless interface through the event handler 210 and the abstraction layer 208.

[0041] The event / command may trigger multiple combined events / commands, or the event / command may trigger consecutive events / commands, or the event / command may trigger multiple parallel events / commands. In addition, the command may contain a set of instructions to be executed by the recipient of the command. For example, the WPS start PIN command includes (1) the interface name of the basic service set (BSS), such as a 2.4 GHz wireless interface, (2) the BSSID (the node MAC address to be used to perform WPS), and (3) the PIN (personal identification number). The WPS start PIN command initiated by the mesh control subprocessor 203 notifies the wireless driver via the abstract layer 208 that the WPS command will be triggered on the wireless driver with the provided BSSID using the provided PIN. The wireless driver initiates the WPS command and again notifies the mesh control subprocessor 203 of the result (timeout, success or failure) via the abstract layer 208 and the event handler 210.

[0042] To further illustrate, consider a client steering daemon communicating with a 2.4 GHz wireless interface driver. The client steering daemon can request the current receive signal strength indicator (RSSI) for a particular client. To do this, the client steering daemon generates a "get client RSSI" command, which contains various information in its payload. Typical information in the payload includes the client's MAC address, the number of measurement samples requested, and the measurement period. For example, the client steering daemon can generate a "get client RSSI" command for a client to perform RSSI measurements at a frequency of 10 seconds within 1 minute. The corresponding function in the abstraction layer 208 is called, through which the driver hook is called. Note that a driver hook is a function that can be called externally through the abstraction layer 208, and it returns output to the event handler through the abstraction layer 208.

[0043] The cloud control subprocessor 202 is capable of receiving instructions from a remote server, forwarding these instructions to the corresponding subprocessors and daemons in the mesh processor 200, and pushing logs (obtained from the corresponding subprocessors and daemons) back to the remote server. The cloud control subprocessor 202 can be used for the operation of customized subprocessors (e.g., mesh control subprocessor 203, mesh routing subprocessor 204, and various customized subprocessors). To better illustrate the use of the cloud control subprocessor 202, consider the following example: the cloud control subprocessor 202 receives a client authentication request event from a wireless interface and received signal strength indication (RSSI) information from a corresponding driver hook through the abstraction layer 208 and the event handler 201. In addition, the cloud control subprocessor 202 receives RSSI information of each associated client from the corresponding driver hook through the abstraction layer 208, or through a customized daemon (such as a client guidance daemon), which has the MAC address of the corresponding client and the timestamp of the measurement. The cloud control subprocessor 202 sends this information to the cloud server. The cloud control subprocessor 202 can push the information when it is created, or it can wait for a predetermined time period before pushing the information along with other information collected during that time period (it can send a bundle of information), or it can wait for a request from a remote cloud server and, in response to the request, provide the information to the cloud server.

[0044] The remote cloud server collects information from multiple GWs, APs, and homes. Therefore, the remote cloud server is able to perform complex analysis on the collected data (which may be spread over days, months, or even years, and a number of clients (on the order of millions or more)). The details of the actions taken by the remote cloud server are not within the scope of this disclosure. However, the cloud control sub-processor 202 is compatible with the cloud control server, so that the commands issued by the cloud server can be understood by the cloud control sub-processor 202, and similarly, the logs / information provided by the cloud control sub-processor 202 can be understood by the cloud server.

[0045] In an example implementation, the cloud server instructs the cloud control sub-processor 202 to change the frequency of data collection for a particular client in the mesh network or for all clients in the network. In addition, the cloud server instructs the cloud control sub-processor 202 to instruct the client steering daemon to exempt a particular client (STA) from the actions of the client steering daemon (i.e., to disable steering only for that particular STA). Alternatively, the cloud server may instruct the cloud control sub-processor 202 to instruct the client steering daemon to use a different set of parameters (which controls the behavior of the client steering daemon) when executing steering decisions.

[0046] Essentially, the remote cloud server is able to control the behavior of all sub-processors and daemons, and in fact controls the behavior of the GW and / or AP, thereby achieving complete control of the network by utilizing the cloud control sub-processor 202. In order to achieve this, the remote cloud server and the cloud control sub-processor 202 need to know the capabilities (and characteristics) of the sub-processors and daemons running on the mesh processor 200 so that the cloud server can communicate with them and instruct them as needed.

[0047] In one embodiment, the sub-processors and daemons resident in the mesh processor 200 may be individually upgraded. For example, additional capabilities may be introduced to, for example, the mesh routing sub-processor 204 or the client guidance daemon without requiring an upgrade of the entire firmware or firmware.

[0048] In one embodiment, the subprocessors and daemons residing in the mesh processor 200 can communicate with other subprocessors and daemons residing in another mesh processor 200 in another MAP via the inter-MAP communication subprocessor 207. The subprocessors in a MAP can communicate with the corresponding subprocessors in another MAP using their specific communication protocols. However, the inter-MAP communication subprocessor 207 provides a unified and universal inter-MAP communication platform for any subprocessor residing in a MAP. The subprocessors can communicate with the inter-MAP communication subprocessor 207 through the abstraction layer 208. The subprocessors subscribe to the inter-MAP communication subprocessor 207 for transmitting and receiving their messages according to the payload. For example, the subprocessor transmits its message to the inter-MAP communication subprocessor 207 in the form of a payload chunk to be delivered to one or more specific nodes in the network, and the subprocessor requests the inter-MAP communication subprocessor 207 to forward any payload addressed to itself.

[0049] The inter-MAP communication subprocessor 207 can use various encryption methods; therefore, the subprocessors and daemons attached to it do not need to use their own encryption methods, or they can use the encryption provided by the subprocessor for additional protection. The inter-MAP communication subprocessor 207 fragments the payload into multiple smaller payloads on the sending side so that they do not exceed the maximum transmission payload allowed by the transmission medium, and defragments the payloads on the receiving side to form the original payload. The inter-MAP communication subprocessor 207 can use positive confirmation-based messaging; because unconfirmed messages are retransmitted a certain number of times until they are confirmed or the maximum number of retransmissions is reached.

[0050] The inter-MAP communication subprocessor 207 relieves subprocessors and daemons of the burden of implementing their own message platforms. However, the inclusion of the inter-MAP communication subprocessor 207 in the mesh processor 200 does not require other subprocessors to use the inter-MAP communication subprocessor 207 for their own communications. Other subprocessors can communicate with corresponding subprocessors in other GWs and / or MAPs using their own communication protocols. Therefore, in the remainder of this article, when it is mentioned that a subprocessor or daemon communicates with another subprocessor or daemon residing in another MAP by sending / receiving messages, this can be interpreted in two possible ways. First, communication between subprocessors / daemons of different MAPs is performed by using the inter-MAP communication subprocessor. Second, communication between subprocessors / daemons of different MAPs does not use the inter-MAP communication subprocessor, but directly communicates between corresponding subprocessors / daemons via their own communication protocols.

[0051] Data link layer packet routing in the mesh network is handled by the mesh routing subprocessor 204 residing within the mesh processor 200. The mesh routing subprocessor 204 implements a method for determining the best route to each node in the network. Based on the discovered routes, the mesh routing subprocessor 204 specifies forwarding rules for incoming and outgoing packets. In one embodiment, the mesh routing subprocessor 204 implements a periodic or on-demand route discovery mechanism to determine the cost of packet delivery between nodes. In one embodiment, path discovery uses the cost of each connection on the path from the source node to the destination node to calculate the end-to-end cost.

[0052] The mesh routing subprocessor 204 implements methods for evaluating the quality of a connection between a node pair. These methods may utilize the following parameters to evaluate the quality of a connection: packet error rate (PER), achievable physical rate, achievable modulation and coding scheme (MCS), RSSI, delay, jitter, etc. The evaluated quality is represented by a cost metric. The cost metric may be a function of various quality parameters. In one embodiment, the cost metric may be inversely proportional to the achievable physical rate, so as the achievable physical rate on a connection increases, the cost of using the connection decreases.

[0053] The mesh routing subprocessor 204 generates connection monitoring commands to understand the status of the connection. The connection monitoring commands can be periodic or on-demand. The connection monitoring command prompts the driver to return the current connection quality metric of the queried interface with the queried receiver. For example, the connection monitoring command can ask the 5GHz wireless driver to return the physical rate of the last packet sent on the wds0.1 connection (for which an acknowledgment was received) (see Figure 2B ). Note that a wds0.1 connection specifies a specific receiving node attached to a 5GHz wireless interface. Therefore, the quality of a wds0.1 connection is nothing more than the quality of communicating with the corresponding node connected on the 5GHz wireless interface. As previously mentioned, the connection monitoring command can contain a payload that specifies to the driver what type of information is being requested. For example, the payload can include RSSI, physical rate, PER observed on the connection.

[0054] The mesh routing subprocessor 204 uses the individual connection costs to determine the end-to-end path cost. The end-to-end path can be determined by an on-demand type of route discovery protocol, such as AODV (ad hoc on demand distance vector routing), which calculates the path cost when route discovery and route response messages are exchanged between the source node and the destination node via intermediate nodes. The end-to-end path can also be determined by a centralized approach, in which the connection cost metric information of the entire network is collected at each node or a master node, which calculates the shortest path for each possible source-destination pair in the network. Based on the determined routes, the mesh routing subprocessor 204 defines interfaces for different packet flows. For example, if the shortest path between GW and MAP2 is through MAP1, where the GW-MAP1 connection is Ethernet (eth0.1) and the MAP1-MAP2 connection is 5GHz wireless (through wds0.1), the mesh routing sub-processor 204 on MAP1 defines that packets from MAP2 destined for GW are delivered on wds0.1 and they will be forwarded to eth0.1.

[0055] The mesh routing subprocessor 204 sets the packet forwarding rules in the interface-specific driver. In one embodiment, the packet forwarding rules can be given based on the source MAC address, the destination MAC address, the MAC address of the next hop node, and one or more interfaces for packet forwarding, and the rule will be interpreted as: the packet originated from the source and used to be delivered to the destination will be forwarded to the next hop node on the specified one or more interfaces. In another embodiment, the forwarding rules can only specify the MAC address and interface of the destination and next hop node. In another embodiment, the packet forwarding rules can be combined with flows and quality of service (QoS)-based metrics to distinguish and route different flows on different paths.

[0056] For example, a forwarding rule may specify that packets originating from node A and destined for node Z will be forwarded via the wireless 5 GHz interface to node F. The forwarding rule may specify further details, such as packets originating from node A with a video label and destined for node Z will be forwarded via the Ethernet interface to node K, and packets originating from node A with a BestEffort label and destined for node Z will be forwarded via the wireless 5 GHz interface to node Y. The forwarding rule may specify further details, such as constraints on delay requirements for packets, etc.

[0057] The mesh routing subprocessor 204 sets forwarding rules for the interface-specific drivers. For example, in one embodiment, if the forwarding rules specify that if a packet is destined for node D, it will be forwarded to node E on the wireless 5 GHz interface, the mesh routing subprocessor 204 programs the driver for the wireless 5 GHz interface to forward packets destined for node D to the WDS connection associated with node E.

[0058] Figure 2B An example of a forwarding rule employed by the mesh routing subprocessor 204 is depicted. Note that a forwarding rule can specify a destination, a next hop node, and an interface. The amount of detail that can be specified in a forwarding rule depends in part on the capabilities of the driver, since drivers can also implement their own forwarding tables. For example, if a driver expects destination MAC address information to check which logical connection to forward a packet to, the mesh routing subprocessor 204 cannot instruct the driver to distinguish between sources attempting to send packets to the same destination node, since the driver does not implement a method to distinguish between source addresses.

[0059] When a new connection is established between nodes, the packet routing subprocessor updates the forwarding rules. For example, if an Ethernet connection is enabled between two MAPs, the Ethernet interface of each MAP generates an interface up event. The Ethernet up event is passed to the mesh control subprocessor 203 and the mesh routing subprocessor 204 via the abstraction layer 208. The mesh control subprocessor 203 starts using the newly available Ethernet interface for mesh advertisement messages, join request / join response messages, configuration request / configuration response messages, etc.; the mesh routing subprocessor 204 starts path discovery for each mesh peer. In some aspects, using the newly available Ethernet connection, possible path alternatives can be increased.

[0060] In the event that a MAP node is shut down, connections terminating and originating from the MAP node are disconnected. In this case, the mesh routing sub-processor 204 of the adjacent MAP identifies the broken connection and updates the corresponding broken connection cost metric to infinity (or to the highest cost that can be assigned to the connection). Since the cost of using the broken connection reaches infinity, the shortest path discovery method used will not choose a path that passes through the broken connection(s). As a result of the updated connection metric, a new shortest path that avoids the broken connection(s) is found, and thus the forwarding rules are updated accordingly.

[0061] Furthermore, when a MAP node is turned off, the MAP remains in the mesh peer list, although it has been removed from the forwarding rules of other nodes in the mesh network. The GW node keeps announcing the turned off MAP in its mesh peer list (WDS peer list). Therefore, if a new MAP is added to the mesh network while the above MAP is turned off, the new MAP adds the turned off MAP to its mesh peer list. When the turned off MAP is turned back on, it connects to the GW or MAP in STA mode, obtains the configuration that also includes the mesh peer list, switches to AP mode, and establishes a mesh connection with the nodes in the mesh peer list.

[0062] In some embodiments, the mesh control subprocessor 203 can control which wireless channel the mesh network operates in. The mesh control subprocessor 203 can request channel availability measurements in any wireless channel from the wireless driver based on airtime statistics, interference statistics. In some embodiments, the mesh control subprocessor 203 of the first device can also request the same measurements from the mesh control subprocessor 203 of the second device. The request can be performed by the inter-MAP communication subprocessor 207 of the first device. Based on the provided results, the mesh control subprocessor 203 of the first device can select another operating Wi-Fi channel (frequency) for the network.

[0063] Figure 2C250 . As shown in the figure, MAP250 includes a processing circuit 251, a memory 253 and (multiple) communication interfaces 255. According to various aspects of the present disclosure, the processing circuit 251 may include any suitable type of processing circuit. For example, the processing circuit 251 may include one or more of a general-purpose processor (e.g., an ARM-based processor), a communication interface chipset, an application-specific integrated circuit (ASIC), and a field-programmable gate array (FPGA). The memory 253 may include any suitable type of volatile and non-volatile memory, such as random-access memory (RAM), read-only memory (ROM), flash memory, cloud storage, or network accessible storage (NAS). The communication interface 255 may include any suitable type of communication interface, such as a Wi-Fi interface, an Ethernet interface, a Long-Term Evolution (LTE) interface, a Bluetooth interface, an infrared interface, a power line communication (PLC) interface, a multiplex over coaxial (MoCA) interface, etc.

[0064] According to aspects of the present disclosure, MAP 250 may be combined with the above reference Figure 2A-2B Examples of mesh processor 200 discussed. Examples of mesh processor 200 in MAP 250 may be implemented in hardware (eg, using hardwired logic), software (eg, using one or more processor-executable instructions), and / or a combination of hardware and software.

[0065] Figure 2D2 is a diagram of an example of a MAP GW 260 according to aspects of the present disclosure. As shown, the MAP GW 260 includes a processing circuit 261, a memory 263, and (multiple) communication interfaces 265. According to aspects of the present disclosure, the processing circuit 261 may include any suitable type of processing circuit. For example, the processing circuit 261 may include one or more of a general-purpose processor (e.g., an ARM-based processor), a communication interface chipset, an application-specific integrated circuit (ASIC), and a field-programmable gate array (FPGA). The memory 263 may include any suitable type of volatile and non-volatile memory, such as a random access memory (RAM), a read-only memory (ROM), a flash memory, a cloud storage device, or a network accessible storage device (NAS). The communication interface 265 may include any suitable type of communication interface, such as a Wi-Fi interface, an Ethernet interface, a long-term evolution (LTE) interface, a Bluetooth interface, an infrared interface, a power line communication (PLC) interface, a multiplex over coaxial (MoCA) interface, etc.

[0066] According to various aspects of the present disclosure, the MAP GW 260 may be combined with the above reference Figure 2A-2B Instances of the mesh processor 200 discussed. Instances of the mesh processor 200 in the MAP GW 260 may be implemented in hardware (eg, by using hardwired logic), software (eg, by using one or more processor-executable instructions), and / or a combination of hardware and software.

[0067] The operation of the MAP 250 and the MAP GW 260 will now be described in further detail. More specifically, in operation, the MAP GW 260 periodically sends "mesh advertisement" messages. In a typical embodiment, the period of the advertisement is 1 second. These messages are broadcast in the data link layer through all available interfaces of the MAP GW 260. For example, if the MAP GW 260 includes PLC, Ethernet, 2.4 GHz Wi-Fi, and 5 GHz Wi-Fi interfaces, it broadcasts the "mesh advertisement" message through each of these interfaces. In a further embodiment, the MAP GW 260 may choose to limit the advertisement to some or only one interface. It should be noted that the mesh advertisement message is sent in broadcast mode, and the recipient of the message also forwards the same message in broadcast mode. Therefore, the mesh advertisement message sent by the MAP GW 260 reaches every MAP in the network.

[0068] Using the "mesh advertisement" message, the MAP GW 260 notifies other nodes in the network of its capabilities and non-confidential mesh configuration. The non-confidential mesh configuration includes at least the following: device capabilities, configuration universally unique identifier (CUUID), GW MAC address on which the mesh network will be established, and a list of MAC addresses of WDS (mesh) peers. In one embodiment, the mesh network can be established with a 5GHz interface, so the MAPGW 260 advertises the MAC address of its 5GHz interface as the mesh interface. Similarly, the list of WDS peers is given based on the 5GHz interface MAC address of the WDS peer. When the MAP GW 260 provides information about its capabilities, it can provide an indication of the protocols supported by the MAP GW 260 (e.g., IEEE 802.11a / b / g / n / ac / ax), an indication of the frequency at which the MAP GW 260 can operate, an indication of the supported bandwidth, etc. In one embodiment, the device capabilities provided in the mesh advertisement are the same as the capability information provided in the beacon and probe response messages in accordance with the corresponding IEEE 802.11 standards supported by the wireless interface of the MAP GW 260 .

[0069] In one embodiment, the CUUID is a 24-byte value, 16 bytes of which are used as the network identifier (NI) and 8 bytes of which are used as the configuration sequence number (CSN). For a given mesh network, the NI is unique and does not change. Two mesh networks that obtain different NIs will not establish a mesh communication connection between each other. For mesh networks with the same NI, the CSN indicates the freshness of the configuration. If a mesh-enabled node receives a mesh configuration with a CSN higher than its current CSN, it updates its mesh configuration with the configuration represented by the latest CSN.

[0070] In another embodiment, any MAP that wants to form a mesh connection with the MAP GW 260 first needs to establish a connection with the MAP GW 260 through one of the interfaces so that it can receive the "mesh advertisement" message. For example, the MAP node 250 can be connected to the MAP GW 260 via Ethernet. In this case, the MAP node 260 receives the "mesh advertisement" from the Ethernet interface.

[0071] In another embodiment, the wireless connection between the MAP GW 260 and the MAP 250 can be established by utilizing the Wireless Protection System (WPS) protocol. Specifically, a standard push button WPS event can be triggered at the MAP GW 260 and the MAP node, thereby generating an AP-STA connection between the MAP GW 260 and the MAP node. In particular, the WPS button of the MAP GW 260 and the WPS button of the MAP 250 can be pressed to trigger a WPS transaction between the MAP GW 260 and the MAP 250. Note that in this scenario, the MAP GW 260 is the registrant and the MAP 250 is the participant, i.e., the MAP GW 260 is the node that distributes the credentials, and the MAP 250 obtains the credentials from the MAP GW 260.

[0072] It should be noted that the wireless connection formed by using the WPS button event before the mesh connection is established between the MAP GW 260 and the MAP 250 is an AP-STA type connection. That is, the MAP 250 is connected to the MAP GW 260 as a station, not as an AP. Unless the MAP 250 establishes a mesh connection with the MAP GW 260, the MAP 250 operates as a station wirelessly connected to the MAPGW 260. In a further embodiment, before the mesh connection is established with the MAP GW 260, the MAP 250 may operate as a UR connected to the MAP GW 260.

[0073] After the MAP 250 node has established a connection with the MAP GW 260 through at least one of its interfaces, the MAP 250 receives the mesh advertisement message broadcasted by the MAP GW 260. In addition, an alternative embodiment is possible in which the MAP 250 establishes a mesh connection with the MAP GW 260 without first establishing another connection. In this case, the MAP 250 sends a "join request" message to the MAP GW 260 through each of its communication interfaces in unicast mode. For example, if the MAP 250 is connected to the MAP GW 260 through both Ethernet and Wi-Fi interfaces, the MAP 250 sends the "join request" message through the Ethernet and Wi-Fi interfaces with the MAC addresses of the corresponding interfaces of the MAP GW 260 as the destination address.

[0074] In response to the "Join Request" message sent by the MAP 250, the MAP GW 260 sends confidential credentials to the MAP 250 in an encrypted "Join Response" message. As described above, the confidential credentials may include a trusted PIN associated with the MAP 250. The confidential credentials provided in the "Join Response" message are the trusted PINs, SSIDs, and passwords (if any) for some or all interfaces (e.g., Wi-Fi 2.4GHz and 5GHz interfaces, and PLC interfaces). The Join Response message is encrypted in order to avoid security vulnerabilities that may be encountered due to an unencrypted connection between the MAP 250 and the MAP GW 260. That is, even if the connection between the MAP 250 and the MAPGW 260 is not protected by any encryption method (such as an encryption method defined in WPA2, etc.), the Join Response message is encrypted to protect the confidential credentials and, most importantly, the trusted PIN.

[0075] If the "join response" message is sent on every possible interface between the MAP 250 and the MAP GW 260, encryption is particularly important because it prevents nodes attached to the network (via Ethernet) from decoding confidential credentials by eavesdropping on the communication between the MAP 250 and the MAP GW 260. In further embodiments, the MAP GW 260 can limit the interfaces through which it sends the join response message. For example, the MAP GW 260 can choose to send the join response message using only the wireless 5 GHz interface, even though it has an Ethernet interface and / or other interfaces that can be used to reach the MAP GW 260.

[0076] As described above, in some embodiments, the MAP 250 may connect to the MAP GW 260 as a station (e.g., a wireless client) and exchange "join request" and "join response" messages through a connection established as a result of the MAP 250 connecting to the MAP GW 260 as a station. When the MAP 250 connects to the MAP GW 260 as a station, it operates in STA mode, and the connection between the MAP 250 and the MAP GW 260 is referred to as a station mode connection. When the MAP 250 receives credentials from the MAP GW 260 in STA mode, it changes its operation mode to AP and applies the credentials: updates its SSID and password according to the received credentials, creates WDS connections according to the mesh peer list shared by the MAP GW 260, adds these WDS connections to its bridge interface, sets the configuration UUID, and adds a vendor information element (IE) to its management group.

[0077] If a mesh connection is established on the 5GHz wireless interface, both the MAP 250 and the MAP GW 260 set the CCMP (Counter Mode Cipher Block Chaining Message Authentication Code Protocol) key derived from the primary SSID password of the 5GHz interface to the WDS connection. After this process, the MAP GW 260 and the MAP 250 form a mesh network, and wireless communication between the MAP 250 and the MAP GW 260 is performed on the WDS connection.

[0078] Figure 3A 300 is a diagram of an example of a network 300 according to various aspects of the present disclosure. The network 300 can be any suitable type of network. In some embodiments, the network 300 can include a wireless network (e.g., an 802.11a / b / g / ac network). Additionally or alternatively, in some embodiments, the network 300 can include a wired network (e.g., Ethernet). As shown, the network 300 can include a mesh-enabled access point gateway (MAPGW) 302, a mesh-enabled access point (MAP) 304, and a MAP 306 configured to operate as an access point of the network 300. In addition, the MAP GW 302 and the MAPs 304 and 306 can be connected to each other via a mesh connection (e.g., a WDS link) to form a mesh network 310. The mesh network 310 can be a subnet of the network 300. In some embodiments, the mesh network 310 can include only nodes configured to operate as access points of the network 300. Additionally or alternatively, in some implementations, mesh network 310 may include other nodes besides nodes configured to operate as access points of network 300 .

[0079] The network 300 includes stations (STA) 314 and 316. STA 314 is connected to MAP 304 via a station mode connection. STA316 is connected to MAP 306 via a station mode connection. In other words, the stations in the network 300 are connected to the nodes in the mesh network 310 via a station mode connection, and the nodes within the mesh network 310 are connected via mesh connections. In some embodiments, any mesh connection can be a WDS connection and / or any other suitable type of connection that allows MAP 304 to connect to MAP 306 and perform at least some of the routing functions described throughout the specification. The present disclosure is not limited to any particular type of protocol for establishing a mesh connection. In addition, although in this example, the network 310 is a mesh network, alternative embodiments in which the network 310 has any other suitable type of topology are also possible. Therefore, the present disclosure is not limited to any particular topology of the network 310.

[0080] Figure 3B is a sequence diagram of an example of a process 350 performed by the MAP GW 302 and the MAP 304 when a mesh connection connecting the MAP GW 302 and the MAP 304 is established.

[0081] At step 351, MAP 304 establishes a wireless station mode connection with MAP GW 302 through any of its interfaces, such as Ethernet, PLC, or Wi-Fi interfaces. It should be noted that for MAP 304 to establish a wireless station mode connection with MAP GW 302, it may first be associated with MAP GW 302 as a station node. To this end, MAP 304 may utilize various methods. For example, MAP 304 may be associated with MAP GW 302 or any MAP (e.g., MAP 306) through a WPS button method. Specifically, once the WPS buttons of MAP 304 and MAP GW 302 are pressed, a WPS transaction is initiated between the two nodes. At the end of the transaction, MAP 304 establishes a station mode connection to MAP GW 302. When MAP 304 operates as a STA connected to MAP GW 302, it is referred to as operating in STA mode (e.g., IEEE 802.11 STA mode).

[0082] At step 352, the MAP 304 receives the “mesh advertisement” message sent by the MAP GW 302. In some embodiments, the “mesh advertisement” message may include a CCUID corresponding to the mesh network 310. As described above, the CUUID may be a 24-byte value, 16 bytes of which are used to represent a network identifier (NI) corresponding to the mesh network 310, and 8 bytes of which are used to represent a configuration sequence number (CSN) identifying the configuration of the mesh network 310.

[0083] At step 353, upon receiving the "Mesh Advertisement" message, MAP 304 sends a "Join Request" message to MAP 302. The "Join Request" message is unicast, and it may include a destination address field set to the MAC address of MAP GW 302, a source address field set to the MAC address of MAP 304, and a sender / transmitter address field both set to the MAC address of MAP 304.

[0084] At step 354, upon receiving the Join Request message sent by MAP 304, MAP GW 302 sends the confidential credentials of network 300 to MAP 304 via an encrypted Join Response message. As described above, the confidential credentials may include a trusted PIN for connecting to mesh network 310 and / or one or more nodes in mesh network 310.

[0085] At step 355, following receipt of the "join response" message, MAP 304 applies the configuration parameters and sets up a mesh connection (e.g., a WDS connection) with MAP GW 302, as well as additional mesh connections (e.g., WDS connections) with other MAPs that are part of mesh network 310 (e.g., mesh peers), such as an additional mesh connection with MAP 306, if MAP 306 is already connected. In some embodiments, any mesh connection may be a single-hop data link layer connection. After the mesh connection(s) are established, MAP 302 may transition to AP mode (e.g., IEEE 802.11 AP mode) and begin operating as an AP of network 300.

[0086] In some embodiments, the station mode connection established at step 351 may be terminated after one or more mesh connections are established at step 355. In this case, the MAP 302 may exit the STA mode and begin operating in the AP mode. Alternatively, in some embodiments, the station mode connection established at step 351 may be maintained after one or more mesh connections are established at step 355. In this case, the MAP 302 may operate in both the STA mode and the AP mode. It can be easily understood that when the MAP 302 operates in both the AP mode and the STA mode, the station mode connection may be used to send data to the MAP GW 302 and / or nodes in the network 320, the data being transmitted from the STA (e.g., the STA) connected to the network 300 via the MAP 302. Figure 4 Additionally or alternatively, when the MAP 302 operates in both AP mode and STA mode, the station mode connection can be used to receive data directed to the STA.

[0087] Figure 4is a diagram of an example of a process 400 for adding an additional node to a network 300 in accordance with aspects of the present disclosure. At step 410, a MAP 306 connects to the network 300 as a station by establishing a station mode connection with the MAP 304. For example, when the station mode connection is an IEEE 802.11ac connection, the MAP 306 can connect to the MAP 304 in the same manner that any device can connect to a home wireless router or a commercial access point. In some implementations, the station mode connection can be a direct connection (e.g., a single-hop data link layer connection) between the MAP 306 and the MAP 304. When the MAP 306 is connected to the network 300 as a station, it is referred to as operating in station (STA) mode (e.g., IEEE 802.11 station mode). When operating in STA mode, the MAP 306 can be an end node (or leaf) in a graph defined by the network 300 topology.

[0088] At step 420, one or more mesh connections (eg, WDS connections) are established between the MAP 306 and the nodes in the mesh network 310. The mesh connections may be based on the reference Figure 3B 304). In some embodiments, one or more mesh connections may be single-hop data link layer connections. More specifically, MAP 306 may receive a "mesh advertisement" message sent by MAP GW 302 (or another node in network 300) through a site mode connection and send a "join request" message in response. Thereafter, MAP 306 may receive a "join response" message from MAP GW 302 (or another node in mesh network 310), the "join response" message containing configuration parameters for establishing a mesh connection (e.g., a WDS connection) with MAP GW 302. The configuration parameters may also be used to establish a mesh connection with other nodes (e.g., MAP 304) in mesh network 310. Other nodes in mesh network 310 may be identified by MAP 306 based on a peer list provided to MAP 306 by MAP GW 302. When step 420 is executed, the peer list may identify one or more devices that are part of the mesh network 310, and it may include an identifier (e.g., an address, such as a MAC address) corresponding to at least one corresponding communication interface of each of the devices that are currently part of the mesh network 310.

[0089] It should be noted that before the mesh connection is established, the MAP 306 is only connected to the MAP node 304, and it is connected to the MAP GW 302 via the MAP 304. However, after it successfully establishes its mesh connection (e.g., WDS connection), it becomes part of the mesh network 310, and thus it obtains a direct mesh connection (e.g., WDS connection) to the MAP GW 302. This direct mesh connection (e.g., WDS connection) to the MAP GW 302 provides an alternative path to the MAP GW 302, which would not be an option if the MAP 306 remained connected to the MAP 304 in STA or UR mode. According to aspects of the present disclosure, a direct connection between two devices may be a connection that allows data to be transmitted in a single hop between the two devices without passing through any intermediate nodes.

[0090] In some aspects, when the MAP 306 is connected to the mesh network 310 via one or more mesh connections, the MAP 306 is referred to as operating in AP mode (e.g., IEEE 802.11 AP mode). When operating in AP mode, the MAP 306 can be an intermediate node in a graph defined by the topology of the network 300. Thus, when operating in AP mode, the MAP 306 can be located on any network path that connects the MAP GW 302 to another node (e.g., STA 316) in the network 300. In addition, when operating in AP mode, the MAP 306 can operate as an access point of the network 300.

[0091] At step 430, STA 316 connects to network 300 via MAP 306. After connecting to network 300, STA 316 may send a message (or data) to a destination located outside network 300 via MAP GW 302 and MAPs 304 and 306. MAP 306 may receive the message and route it to MAP 304. Upon receiving the message from MAP 306, MAP 304 may forward the message to MAP GW 302. Upon receiving the message, MAP GW 302 may further forward the message to a node located outside network 300. For example, MAP GW 302 may send a message to a node located in network 320. Network 320 may be the Internet and / or any other suitable type of network, such as a wide area network.

[0092] According to aspects of the present disclosure, the configuration of the mesh network 310 may change during its operation. For example, a user may change the SSID and / or password of the network 300, or a user may change the operating channel of the Wi-Fi interface, or a user may even replace the MAP GW 302 with another gateway node. For situations where a mesh configuration update is required, examples of methods for maintaining connectivity in the mesh network 310 are further disclosed below.

[0093] According to aspects of the present disclosure, due to government regulations, an AP operating in a radar channel must be able to detect radar with at least a given probability and, in the event of detection, change its operating channel and not return to its previous operating channel for a specified duration. This is called dynamic frequency selection (DFS); channels that require radar detection capabilities are called DFS channels, and other available channels are called non-DFS channels. Local authorities manage regulations for devices operating in the 5GHz band, for example, ETSI in Europe and FCC in the United States. For example, according to ETSI, channels falling within the range of 5150-5250MHz are called non-DFS channels, while channels falling within the ranges of 5250-5350MHz and 5490-5725MHz are called DFS channels. In the case where the mesh network operates in a DFS channel in the 5GHz band (i.e., the mesh connection is on a 5GHz DFS channel), if the MAP node detects a radar, it notifies the gateway node of the presence of the radar. Note that due to regulations, a node that detects a radar must stop transmitting in that DFS channel for a predetermined period of time and then switch to a radar-free channel. The AP is only allowed to transmit for a small portion of the allowed time period before ceasing transmission in the DFS channel upon detecting radar.

[0094] Figure 5 is a diagram illustrating an example of a process 500 for changing a channel used by a network 300 in response to detecting that the channel is being used by one or more systems (e.g., a radar system) that have a higher priority for use of the channel than a device in the network 300.

[0095] At step 510, the network 300 is operating in a current channel (e.g., channel 100), and the MAP 306 detects that the current channel is used by a radar. In response to detecting the presence of the radar, the MAP 306 sends two messages to its mesh peers: (i) a channel switch announcement (CSA) message specifying a candidate channel to switch to is sent to each node in the network 300, including the MAP GW 302, the MAP 306, and the site nodes, and (ii) a radar-detected message is broadcast to each MAP (e.g., MAP 304), and the MAP GW 302 in the mesh network 310. If the node (e.g., the MAP GW 302 and the MAP 304) successfully receives the CSA message, the network switches to the channel specified in the CSA message; thereby re-establishing the WDS connection in the switched channel. However, if the CSA message is not successfully delivered, the node that cannot receive the CSA will not be able to switch to the specified channel. In one embodiment, the radar detection message includes an indication of an alternative channel to switch to or a list of alternative channels to switch to. In another embodiment, the radar detection message may be used only to inform other MAPs (e.g., MAP 304) or MAP GW 302 in the network 300 that the current channel is being used by a higher priority system without indicating or suggesting an alternative channel. In a further embodiment, an Extended Channel Switch Announcement (ECSA) may be used instead of a CSA.

[0096] At step 520, MAP GW 302 successfully receives the CSA message, but MAP 304 does not. Thereafter, MAP GW 302 and MAP 306 switch to use the alternative channel specified in the CSA message. However, because MAP 304 does not receive the CSA message, it continues to operate in the same channel. As a result, the mesh connection between MAP 304 and MAP GW 302 is lost, and the mesh connection between MAP 304 and MAP 306 is also lost. MAP 304 recognizes that it has lost its mesh connection because it cannot receive periodic "mesh advertisement" messages through the mesh connection. It should be noted that if MAP 304 and MAPGW 302 are connected through another interface (e.g., an Ethernet interface), MAP 304 can learn updated channel information via the "mesh advertisement" messages received on the other interface. However, if the only connection option between the MAP and the gateway is the lost mesh connection, then the MAP 304 loses its connection to the MAP GW 302 as the MAP GW 302 switches channels.

[0097] At step 530, when the MAP 304 loses its connection to the MAP GW 302, it returns to STA mode and scans available channels to find the MAC address of the MAP GW 302 that is already known to the MAP 304. The scan can be a passive scan (meaning that the scanning node listens for messages, such as beacons), an active scan (meaning that the scanning node sends a probe request message to a broadcast address or a previously known MAC address), or a combination of both.

[0098] At step 540, MAP 304 reconnects to mesh network 310 and reestablishes the mesh connection with MAP 306 and MAP GW 304 that was lost when MAP 306 and MAP 304 changed channels. More specifically, upon finding MAP GW 302, MAP 304 switches to AP mode and changes its operating channel to the channel in which MAP GW 302 and MAP 304 are found.

[0099] The above process is also followed in the case where the MAP GW 302 does not receive the CSA message but successfully receives the radar detection message, in which case the MAP GW 302 changes its operating channel. The MAP GW 302 sends a mesh advertisement in the newly switched channel with the updated channel information and with the incremented CSN. If the MAPs 304 and 306 successfully receive the CSA message, the mesh network 310 switches to the channel specified in the CSA message; thereby re-establishing the WDS connection in the switched channel.

[0100] Figure 6 6 is a diagram illustrating an example of a process 600 for changing a channel used by a network 300 in response to detecting that the channel is being used by one or more systems (e.g., a radar system) that have a higher priority for using the channel than a device in the network 300. In both process 500 and process 600, the MAP 306 detects that the current channel occupied by the mesh network 310 is being used by one or more systems that have a higher priority for using the channel, and sends a CSA message and a radar detection message in response. However, unlike process 500, in process 600, the CSA message and / or the radar detection message cannot be delivered to the MAP GW 302. In this regard, process 600 illustrates steps performed by the mesh network 310 when the MAP GW 302 fails to receive a CSA message and / or a radar detection message sent by a MAP node in the network.

[0101] At step 610, MAP 306 detects that the first channel is used by a radar. In response to detecting the presence of the radar, MAP 306 transmits (e.g., broadcasts) two messages to its mesh peers: (i) a CSA message specifying a candidate channel to switch to is sent to each node in the network 300, including MAP GW 302, MAP 304, and site nodes, and (ii) a radar detection message is broadcast to each MAP (e.g., MAP 304), and MAP GW 302 in the mesh network 310.

[0102] At step 620, the MAP 304 receives the CSA message and / or the radar detection message sent at step 610. However, the MAP GW 302 fails to receive the CSA message and the radar detection message sent at step 610. As a result, the MAPs 304 and 306 switch to use the alternate channel specified in the CSA message and / or the radar detection message, while the MAP GW 302 fails to do so.

[0103] At step 630, following the switch to the designated channel, MAPs 304 and 306 detect that they have lost their respective mesh connections to MAP GW 302 and switch back to STA mode. MAPs 304 and 306 establish respective station mode connections with MAP GW 302 and resend CSA messages and / or radar detection messages that include an indication of an alternate channel. Upon receiving one or more of the messages, MAP GW 302 switches to use the alternate channel.

[0104] At step 640, MAPs 304 and 306 reconnect to mesh network 310 at the alternate channel and reestablish the mesh connection lost at step 630. Figure 3B As discussed, to reconnect to the mesh network 310, each of the MAP 304 and the MAP 306 may perform a handshake with the MAP GW 302 involving an exchange of "Join Request" and "Join Response" messages.

[0105] Figure 7 302 is a flow chart of an example of a process 700 for reconfiguring a mesh network 310 in response to a change in a password for connecting to a MAP GW 302 in accordance with aspects of the present disclosure. For purposes of this example, it will be assumed that the mesh connection between the MAP GW 302 and the MAPs 304 and 306 is established using a 5 GHz interface that is part of the MAP GW 302.

[0106] At step 710, the MAP GW 302 detects a reconfiguration event that specifies a new password for the wireless 5 GHz interface password. The event may be detected in response to the MAP GW 302 receiving a user input specifying a new password. When the wireless 5 GHz interface password is changed at the MAP GW 302, the key (e.g., WDS key) used to establish a mesh connection between the MAP GW 302 and the MAPs 304 and 306 also needs to be updated because it is derived from the updated password. In one embodiment, the key is always derived from the password of the primary SSID, and therefore, the key automatically changes when the password of the primary SSID changes. In another embodiment, the key may be derived and set once, and the key is not updated when the primary SSID password of the 5 GHz interface is changed. In a further embodiment, the key (e.g., WDS key) may be derived from a separate password dedicated to a mesh connection (e.g., a WDS connection). In this example, the change in password requires a key update.

[0107] At step 720, MAP GW 302 announces the password update in a sent "Mesh Advertise" message. "Mesh Advertise" messages do not need to state that the password is to be updated or they do not need to specify which parameter is to be updated, but by using an incremented CSN in the "Mesh Advertise" message, MAP GW 302 notifies its mesh peers (e.g., MAPs 304 and 306) of the configuration update.

[0108] At step 730, MAPs 304 and 306 receive one or more "mesh advertisement" messages and detect that the primary SSID password has changed.

[0109] At step 740, in response to detecting that the password has changed, MAPs 304 and 306 request updated configurations by sending encrypted configuration request messages to MAP GW 302. In one embodiment, each configuration request message includes an identification of the current configuration of the MAP that has sent the configuration request message.

[0110] At step 750, in response to the configuration request messages sent by MAP 304 and 306, MAP GW 302 sends a corresponding encrypted configuration response message to each of MAP 304 and MAP 306. Each corresponding configuration response message includes the updated password. In one embodiment, each corresponding configuration response message contains all configuration parameters of MAP GW 302.

[0111] At step 760, the MAP GW 302 applies the new password. In some embodiments, the MAP GW 302 may apply the password only after the MAP GW 302 has received confirmation from each MAP node in the mesh network 310 that the configuration response message has been received. In one embodiment, the MAP GW 302 updates the password only after it has received the configuration request message from all active mesh peers (e.g., both MAPs 304 and 306 in this example) and has responded to all active mesh peers with configuration response messages. In another embodiment, the MAP GW 302 waits for a predetermined number of mesh advertisements before it applies the password update. For example, in one embodiment, the MAP GW 302 waits for 5 mesh advertisement periods, where each advertisement has a period of 1 second. After receiving the updated password, the MAPs (e.g., MAPs 304 and 306) in the mesh network 310 update the WDS key according to the new password information. After the MAP GW 310 applies the new password, all WDS connections become active using the WDS keys derived from the new password.

[0112] Figure 8 is a flow diagram of an example of a process 800 performed by the MAP 306 after a reboot in accordance with aspects of the present disclosure.

[0113] At step 810, after boot-up, MAP 306 (the former peer of mesh network 310) operates in STA mode and attempts to establish a connection with MAP GW 302 via the WPS-PIN method defined in the IEEE 802.11 standard. According to aspects of the present disclosure, MAP GW 302 stores two PINs in memory: (1) a default PIN of MAP GW 302, which is used for PIN-based WPS connections with devices that do not support MAP, and (2) a trusted PIN, which is used for PIN-based WPS connections with devices that support MAP. When MAP 306 attempts to establish a connection with MAP GW 302 via the WPS-PIN method using the trusted PIN, MAP GW 302 detects whether the requested MAP belongs to a WDS peer list stored in the memory of MAP GW 302, and the list identifies one or more MAPs that have been authenticated to establish a mesh connection with MAP GW 302. If MAP 302 is not identified in the WDS peer list, MAP GW 302 does not initiate the WPS-PIN method using a trusted PIN. In some implementations, a node that is not identified in the WDS peer list of MAP GW 302 may initiate a WPS-PIN using a default PIN of MAP GW 302. On the other hand, if MAP 306 is identified in the mesh peer list, a mesh connection between MAP 306 and other nodes in the mesh network (e.g., MAP 304) may be established.

[0114] At step 820, MAP 306 detects whether the attempt to establish a WPS-PIN connection with MAP GW 302 is successful. If the attempt is successful, the process ends. Otherwise, if the attempt is unsuccessful, the process proceeds to step 830.

[0115] At step 830, if MAP 306 does not have a direct connection with MAP GW 302, it establishes a connection to MAP 304. MAP 306 uses the trusted PIN it acquired during the initial connection with MAP GW 302 to establish a PIN-based site mode connection with MAP 304. After MAP 306 establishes a STA site mode connection with MAP 304 (or another MAP), it receives one or more “mesh advertisement” messages via the site mode connection with MAP 304, and uses those “mesh advertisement” messages to establish a mesh connection with MAP GW 302 and / or MAP 304.

[0116] In some embodiments, if the MAP 306 node is connected to the MAP GW 302 via an Ethernet connection, it receives the "mesh advertisement" message via the Ethernet connection. For example, in the case where the MAP 306 is connected to the MAP GW 302 via an Ethernet connection, the MAP 306 does not need to use the WPS-PIN method defined in the IEEE 802.11 standard to establish a station mode connection with the MAP GW 302.

[0117] Fig. 9 3 is a diagram of a network 300 illustrating an example of a replacement gateway node in accordance with aspects of the present disclosure. As shown, at time t0, MAP GW 302 is a gateway node in network 300, and MAPs 304 and 306 are connected to MAP GW 302, as shown. At time t1, MAP GW 302 is replaced by MAP GW 902, and MAPs 304 and 306 are connected to MAP GW 902 via a new mesh connection.

[0118] Fig.10 1 is a flow chart of an example of a process 1000 for incorporating a MAP GW 902 into a mesh network 310 after the MAP GW 302 has been replaced by a MAP GW 902. At step 1010, the MAP GW 902 detects a trigger event and sends a message containing an indication of the trigger event. Because the MAP GW 902 has no previous connection to the mesh network 310, it requires a trigger event to initiate a connection. The trigger event may be a WPS button event, which may be achieved by pressing a WPS button on the MAP GW 902 and the MAP 304, or the trigger event may be another event initiated through a user interface of the MAP GW 902, or the trigger event may be generated using a user application running on a smart phone or tablet, etc., which may send a trigger event command to the MAP GW 902 and any one of the MAPs 304 and 306 for starting a WPS transaction.

[0119] At step 1020, MAP 304 receives the message including the indication of the triggering event and establishes a station mode connection with MAP GW 902, while also transitioning from AP mode to STA mode. At step 1030, MAP GW 902 sends a "mesh advertisement" message including the first CUUID, and in particular including the first NI (which is part of the first CUUID) that is different from the second NI associated with the mesh network 310, of which MAP GW 302 is a part.

[0120] At step 1040, MAP 304 detects whether MAP GW 902 is a replacement gateway. According to aspects of the present disclosure, a "replacement gateway" may include a gateway that has never been part of a mesh network before, or a gateway that has been reset to delete some or all information associated with a mesh network of which the gateway was already a part.

[0121] In some embodiments, MAP 304 can detect that MAP GW 902 is an alternate gateway by comparing a first NI contained in the “mesh advertisement” message with a second NI stored in a memory of MAP 304 (and previously used by MAP GW 302 to identify mesh network 310). As described above, the second NI is associated with mesh network 310, and in particular, MAPGW 302. When the first NI and the second NI do not match, MAP 304 infers from the NI that the source of the “mesh advertisement” message (i.e., MAP GW 902) is an alternate gateway.

[0122] In addition, when the "mesh advertisement" message does not include a mesh peer list identifying a previous mesh configuration with other MAPs, the MAP 304 can determine that the MAP GW 302 is an alternate gateway. As described above, the mesh peer list can include a list of MAPs that have previously been connected to the MAP GW 902 (and / or the mesh network 310) via a mesh connection. Therefore, when the "mesh advertisement" message does not include a WDS peer list, the MAP 304 can again infer that the MAP GW 902 is an alternate gateway because no MAP node was previously connected to it.

[0123] When MAP 304 detects that MAP GW 902 is not a substitute gateway, the process proceeds to step 1050. At step 1050, MAP 304 sends a first "join request" to MAP GW 902, and MAP GW 902 responds to MAP 304 with a "join response" message and with a reference to Figure 3B The discussed approach establishes a mesh connection between the MAP 304 and the MAP GW 902 .

[0124] When the MAP 304 detects that the MAP GW 902 is the substitute gateway, the process proceeds to step 1060. At step 1060, the MAP GW 902 transfers its mesh configuration, that is, its peer list (e.g., the WDS peer list corresponding to the mesh network 310) to the MAP GW 902. More specifically, at step 1060, the MAP 304 sends a second "join request" message to the MAP GW 902, in which the mesh configuration (e.g., the mesh peer list of the mesh network 310 and / or the second NI used by the MAPGW 302 to identify the mesh network 310) is included. Different from the first "join request" message, the second "join request" message may include at least one of the second NI of the mesh network 310 and the mesh peer list of the mesh network 310. At step 1070 , the MAP GW 902 sends a “Join Response” message to the MAP 304 , and a mesh connection is established between the MAP 304 and the MAP GW 902 .

[0125] At step 1080, the MAP GW 902 adopts the configuration information of the mesh network 310. More specifically, the MAP GW 902 begins to advertise the mesh peer list of the mesh network 310 in its "mesh advertisement" message. In addition, the MAP GW 902 begins mesh advertisement with the adopted second NI and the incremented CSN. In this way, MAPs having the NI (e.g., the second NI) of the mesh network 300 can receive the "mesh advertisement" message through their mesh connections (e.g., WDS connections) and update their configurations accordingly.

[0126] At step 1090, the MAP GW 902 establishes a mesh connection with one or more other MAPs (e.g., MAP 306) by using the configuration settings adopted by the MAP GW 302. When the MAP GW 302 is replaced by the MAP GW 902, the MAP 306 retains the configuration settings of the mesh network 310 and performs a scan for the missing GW (i.e., the MAP GW 302). Note that when the MAP GW 302 is shut down, all MAPs (e.g., MAP 306) in the mesh network 310 revert to STA mode in an effort to find the MAP GW 302. Since the MAP GW 302 is shut down, the MAPs (e.g., MAP 306) remain in STA mode searching for the MAP GW 302. This search stops when the MAP GW 302 is turned on or when the MAP receives a "mesh advertisement" message from a new GW node (e.g., MAP GW 902) with the same NI. A MAP (e.g., MAP 306) in the mesh network 310 may receive a “mesh advertisement” message on an interface of a gateway node (e.g., MAP GW 902) that connects the MAP to the mesh network 310. The new gateway node (e.g., MAP GW 902) may obtain the interface address of the MAP (e.g., MAP 306) in the mesh network 310 from the peer list sent in step 1060. A MAP that has switched to STA mode may receive mesh advertisements, for example, if it is connected to the MAP GW 902 via Ethernet.

[0127] The remaining MAPs (e.g., MAP 306) in the mesh network 310 and the MAP GW 902 establish the mesh network using the confidentiality credentials of the mesh network 310 that were used before the MAP GW 302 was replaced by the MAP GW 902. In one embodiment, the MAP GW 902 and the MAPs (e.g., MAP 306) in the mesh network 310 may adopt and maintain the confidentiality credentials of the mesh network 310, such as SSID, password, trusted PIN. In another embodiment, the MAP GW 902 may temporarily use the confidentiality credentials of the mesh network 310 to connect to the MAP nodes in the mesh network 310, and it may update these credentials with its default credentials immediately after the connection. The MAP GW 902 notifies the mesh network of the new confidentiality credentials by incrementing the CSN. In one embodiment, any MAP in the mesh network 310 that receives a "mesh advertisement" message with a CSN higher than its current CSN state sends a configuration request message to the MAP GW 902. MAP GW 902 responds with an encrypted Configuration Response message with new confidentiality credentials.

[0128] Fig.11An example of a network 1100 is depicted in which the mesh processor 200 is incorporated into the MAP GW 1103, and a hybrid mesh network is set up using MAPs 1107, 1112, and 1117. The dashed lines represent 2.4 GHz or 5 GHz Wi-Fi connections, and the solid lines represent Ethernet or PLC. More specifically, connections 1110b and 1116b are PLC connections, connection 1117b is an Ethernet connection, and network 1101 represents the Internet. According to this example, if MAPs 1107, 1112, and 1117 employ a communication technology that is not supported by MAP GW 1103, such as PLC, they can utilize the communication medium to transmit between each other; thereby increasing the available capacity outside of the common communication medium. MAPs 1107, 1112, and 1117 utilize all available communication mediums in the hybrid network while creating their forwarding tables and making routing decisions.

[0129] Fig.12 An example of a network 1200 divided into mesh partitions 1220 and 1221 is depicted. Partition 1220 includes MAP GW 1203 and MAP 1212, and partition 1221 includes MAPs 1207 and 1217. Mesh partitions 1220 and 1221 operate in separate wireless channels; therefore, nodes belonging to these partitions do not compete for access to the wireless medium. Communication between partitions 1220 and 1221 is achieved through connection 1216b; therefore, the hybrid network remains fully connected.

[0130] Figure 1A-Figure 12 Provided only as examples. At least some of the steps described in the examples provided throughout the specification may be performed simultaneously, in a different order, or omitted entirely. It should be understood that the provision of examples described herein and the phrases "such as," "for example," "including," "in some aspects," "in some embodiments," etc. should not be construed as limiting the disclosed subject matter to specific examples.

[0131] Having described the embodiments in detail, those skilled in the art will appreciate that, given the present disclosure, modifications may be made to the embodiments without departing from the spirit of the inventive concepts described herein. Therefore, it is not intended that the scope of the embodiments be limited to the specific embodiments illustrated and described.

Claims

1. A method for use in a mesh gateway of a mesh wireless local area network (WLAN), the method comprising: In case a triggering event is detected, sending a message indicating detection of the triggering event to the mesh access point MAP; Establishing a station mode connection with the MAP and switching from access point AP mode to station STA mode; sending a mesh advertisement message to the MAP including an indication that the mesh gateway is a replacement mesh gateway, wherein the indication that the mesh gateway is a replacement mesh gateway includes a network identifier (NI) that is different from a network identifier (NI) associated with the mesh WLAN, or the indication that the mesh gateway is a replacement mesh gateway is that a mesh peer list is not present in the mesh advertisement message; receiving configuration information associated with the mesh WLAN from the MAP in STA mode; establishing a mesh mode connection with the MAP using the configuration information by sending a join response message to the MAP; and The mesh peer list of the mesh WLAN is advertised in the mesh advertisement message.

2. The method according to claim 1, further comprising: At least one other mesh mode connection is established with at least one other MAP using the configuration information.

3. The method according to claim 1, wherein The mesh gateway is a replacement mesh gateway when the mesh gateway has never been part of the mesh WLAN.

4. The method according to claim 1, wherein When the mesh gateway has been reset, the mesh gateway is a replacement mesh gateway.

5. The method according to claim 1, wherein The configuration information includes a peer list associated with the MAP.

6. The method according to claim 1, wherein The configuration information is received from the MAP in a Join Request message.

7. The method according to claim 1, wherein The triggering event includes a Wireless Protected Setup (WPS) button activation at least at the mesh gateway.

8. A mesh gateway comprising: a processor configured to detect a triggering event; a transmitter configured to send a message indicating detection of a triggering event to a mesh access point MAP; The processor and transmitter are configured to establish a station mode connection with the MAP and simultaneously switch from an access point AP mode to a station STA mode; The transmitter is configured to send a mesh advertisement message including an indication that the mesh gateway is a replacement mesh gateway, wherein the indication that the mesh gateway is a replacement mesh gateway includes a network identifier (NI) that is different from a network identifier (NI) associated with the mesh WLAN, or the indication that the mesh gateway is a replacement mesh gateway is that a mesh peer list is absent in the mesh advertisement message; a receiver configured to receive configuration information associated with the mesh WLAN from the MAP in STA mode; The processor and the transmitter are configured to establish a mesh mode connection with the MAP using the configuration information by sending a join response message to the MAP; and The sender is configured to advertise a mesh peer list of the mesh network in a mesh advertisement message.

9. The mesh gateway according to claim 8, wherein: The processor and the transmitter are configured to establish at least one other mesh mode connection with at least one other MAP using the configuration information.

10. The mesh gateway according to claim 8, wherein: The mesh gateway is a replacement mesh gateway when the mesh gateway has never been part of the mesh WLAN.

11. The mesh gateway according to claim 8, wherein: When the mesh gateway has been reset, the mesh gateway is a replacement mesh gateway.

12. The mesh gateway according to claim 8, wherein: The configuration information includes a peer list associated with the MAP.

13. The mesh gateway according to claim 8, wherein: The configuration information is received from the MAP in a Join Request message.

14. The mesh gateway according to claim 8, further comprising: Wireless Protected Setup (WPS) button, wherein the triggering event comprises WPS button activation at least at the mesh gateway.