Relaying devices for wireless mesh network

The present disclosure relates to relaying devices for data communications, and more particularly to wireless relaying devices such as routers. This disclosure also relates to wireless backbone network of wireless mesh networks.

Wireless mesh networks (WMN) are useful in many applications because of their low up-front costs, flexibility in incremental deployment and ease of maintenance. For example, WMN are widely used in community networks, enterprise networks, video surveillance, voice communications and localization services. Wireless mesh network architecture is often seen as a first step towards providing cost effective and dynamic high-bandwidth networks over a specific coverage area. A wireless mesh network can be seen as a special type of a wireless ad-hoc network using IEEE 802.11 ad-hoc protocol for backbone infrastructure. A wireless mesh network often has a more ‘planned’ configuration, and may be deployed to provide dynamic and cost effective connectivity over a certain geographic area. An ad-hoc network, on the other hand, is formed ad hoc when wireless devices come within communication range of each other.

It is known that almost all mesh nodes in existing wireless mesh networks (WMNs) run with the Independent Basic Service Set, or IBSS (also known as ad-hoc) mode defined in the 802.11 standard. Since the development of IBSS is well behind the infrastructure mode counterpart of the same 802.11 version, performance of commercially available WMNs are always well behind the latest 802.11 technology.

When a WMN is to be expanded, the expansion is required to be running with the compatible IBSS mode feature set as the existing WMN (the IBSS mode is even required not to enable some new features such as HT40). As a result, newer technologies cannot be integrated into the existing WMNs at all.

Furthermore, as most modern wireless mesh backbone networks adopt the IEEE 802.11 a/g/n standards and use a rate of 54 Mbps for network communication using ad-hoc protocol, network through-put would be degraded to below 54 Mbps. As a result, work in ad hoc routing protocols for wireless networks has focussed on coupling with scalability or finding high-quality paths in the face of lossy wireless links.

It is also noted that while the infrastructure mode of the 802.11n standard has been available for years, there is still no real 802.11n based WMN mode products available in the market and this has caused unnecessary degrade in performance.

Therefore, it would be advantageous if there can be provided relaying devices for WMN which mitigates the known shortcomings.

There is provided a relaying device for forming a wireless mesh network, the relaying device comprising a first wireless frontend and a second wireless frontend which are to communicate with each other to facilitate data communication between a first external device and a second external device, wherein the first wireless frontend is to communicate wirelessly with the first external device and the second wireless frontend is to communicate with the second external device using IEEE 802.11 infrastructure mode transmission protocol.

A wireless relaying device having first and second wireless frontends which are adapted to communicate wirelessly with external devices using the infrastructure mode protocol is advantageous because this facilitates the building of wireless mesh network backbones using infrastructure mode protocol. In other words, the backbone building wireless routers will use infrastructure mode protocol for inter-router communications. It will be appreciated that the use of the infrastructure mode protocol for inter-router communication is contrary to standard or established practice in wireless mesh networking, but is highly advantageous in that because the infrastructure mode protocol is already ready whenever there is an upgrade in standards so that there is no need to wait for the “ad hoc” protocols, and that the current infrastructure mode protocols are about 6 times faster than the current ‘ad hoc’ protocol WMN products in the market.

For example, a WMN backbone network comprising a plurality of wireless relaying devices adopting the currently state-of-the-art IEEE 802.11n infrastructure mode transmission protocol as the inter-router communication protocol can support a data rate as set by IEEE 802.11n, namely 300 Mbps. This is highly advantageous compared to a wireless backbone built using conventional technology from wireless relaying devices which is limited by the state-of-the-art ‘ad hoc’ mode data rate, which is currently 54 Mbps. A further advantage of wireless relaying devices utilizing the infrastructure mode transmission protocol as the inter-router or inter-relaying devices communication protocol is that the infrastructure mode will be available when a new standard is introduced and well before the ‘ad hoc’ mode. This means the speed of wireless relaying devices utilizing the present disclosure can deploy and operate at a speed stipulated by a new infrastructure mode protocol whenever the new protocol is introduced.

The application of the infrastructure mode protocol as the WMN protocol for wireless routers is contrary to conventional wisdom because infrastructure mode protocol is not considered for conventional “Multi-hop” applications such as WMN. Traditionally, 802.11's infrastructure mode is designed to allow one or more Wi-Fi stations (STA) to connect to a Wi-Fi access point (AP) in a Single-Hop manner, the AP then in turn connects to the LAN backbone, or eventually to the Internet, through an Ethernet cable. Such an established application of the infrastructure mode protocol is apparently not compatible to support Multi-hop WMN operations.

Example wireless routers for WMN operation will be described below by way of example below with reference to the accompanying drawings, in which:

<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram of a router suitable for use in a WMN,

<figref idref="DRAWINGS">FIG. 2</figref> is a schematic diagram depicting a plurality of routers of <figref idref="DRAWINGS">FIG. 1</figref> in operation,

<figref idref="DRAWINGS">FIGS. 3, 3A and 3B</figref> are schematic diagrams depicting a first WMN, a second WMN and a third WMN each including a plurality of wireless routers according to the present invention with reference to the OSI model,

<figref idref="DRAWINGS">FIGS. 4 and 4A</figref> are schematic diagrams depicting a first and a second example network topologies,

<figref idref="DRAWINGS">FIG. 5</figref> is a schematic diagram depicting an example application of a WMN according to the present invention, and

<figref idref="DRAWINGS">FIG. 6</figref> is a schematic diagram depicting example data flow in a 6-hop WMN.

A wireless router <b>800</b> of <figref idref="DRAWINGS">FIG. 1</figref> comprises a first wireless frontend <b>810</b> and a second wireless frontend <b>820</b>. The first wireless frontend <b>810</b> comprises a WiFi radio module <b>812</b> which is connected to a first antenna <b>814</b> and controlled by a microprocessor <b>830</b>. The second wireless frontend <b>820</b> comprises a WiFi radio module <b>822</b> which is connected to a first antenna <b>824</b> and also controlled by the same microprocessor <b>830</b> to enhance cost effectiveness.

The first <b>810</b> and second <b>820</b> wireless frontends are interconnected in a back-to-back manner by means of a router board so that data can flow between the first and second wireless frontends when received from one antenna for transmission by another antenna to the ambience under the control of the microprocessor when the microprocessor executes instructions stored in the memory.

The first wireless frontend <b>810</b>, as an example of a first wireless interface, is adapted to communicate with an external wireless device using infrastructure mode routing protocol. Likewise, the second wireless frontend <b>820</b>, as an example of a second wireless interface, is adapted to communicate with an external wireless device also using the infrastructure mode routing protocol. In one router example <b>860</b>, the first wireless frontend is configured as an access point and the second wireless frontend is configured as a client. In another router example <b>870</b>, both the first and second wireless frontends are configured as access point. In yet another router example <b>880</b>, both the first and second wireless frontends are configured as client. The terms ‘client’, ‘access point’, and ‘infrastructure mode’ herein are terms well known to persons skilled in the art and defined in IEEE 802.11 standards which are incorporated herein and without loss of generality.

As depicted in <figref idref="DRAWINGS">FIG. 1</figref>, the wireless router <b>800</b> comprises a first WiFi radio module <b>812</b> which is configured to operate as the first wireless frontend, a second WiFi radio module <b>822</b> which is configured to operate as the second wireless frontend, and a microprocessor <b>830</b> which connects the first and the second wireless frontends in a back-to-back manner to facilitate internal data communication between the first and second wireless frontends. The first <b>812</b> and the second WiFi <b>822</b> modules are connected respectively to a first antenna <b>814</b> and a second antenna <b>824</b> to facilitate wireless data communications Specifically, the first antenna <b>814</b> is adapted to cooperate with the first WiFi module <b>812</b> and the second antenna <b>824</b> is adapted to cooperate with the second WiFi modules <b>822</b> when under the control of the microprocessor <b>830</b> to facilitate wireless data communications with external data devices using infrastructure mode protocol. To mitigate radio interference, the first and second WiFi radio modules <b>812</b>, <b>822</b> run on different frequencies.

The microprocessor <b>830</b>, or CPU in short, includes peripheral circuits which are mounted on a printed circuit board (PCB) to form a CPU module or router board as is commonly known to persons skilled in the art. Usually, the WiFi modules, the CPU and peripheral circuits and the first and second antennae are all mounted on a rigid housing <b>840</b> for easy deployment. In an example use as shown in <figref idref="DRAWINGS">FIG. 2</figref>, the wireless routers <b>860</b> are arranged in cascade.

As the first and second WiFi modules are arranged in a back-to-back manner, this router will also be referred to as a Back-N router herein.

An example wireless network of <figref idref="DRAWINGS">FIG. 3</figref> comprises a plurality of wireless routers <b>860</b> (WMR-<b>1</b> &amp; WMR-<b>2</b>) in cascade between a Sender and a Receiver. In this cascaded network, each of the cascaded wireless routers <b>860</b> comprises an access point (AP) interface and a client interface. Specifically, the AP interface of WMR-<b>1</b> is connected to the client interface of the Sender, the client interface of WMR-<b>1</b> is connected to the AP interface of WMR-<b>2</b>, and the client interface of WMR-<b>2</b> is connected to the AP interface of the Receiver to form a cascade mesh network.

When a user wants to send data from the Sender to the Receiver through the wireless mesh network, the Sender will be a client in the 802.11 infrastructure mode, and the Sender will establish data connection with the AP interface of WMR-<b>1</b> using the 802.11 protocol. When the Sender is connected to the AP interface of WMR-<b>1</b>, a multi-hop Wi-Fi connection is setup between the Sender and the Receiver.

In a wireless mesh network built with this methodology (‘Back-N’) as described herein, every Wi-Fi interface is associated with an IP address. In the examples shown in <figref idref="DRAWINGS">FIG. 3</figref>, the following exemplary IP addresses are assigned for the Wi-Fi interfaces as convenient examples:

<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="21pt" align="left" /><colspec colname="1" colwidth="35pt" align="left" /><colspec colname="2" colwidth="84pt" align="left" /><colspec colname="3" colwidth="77pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>a</entry><entry>Sender:</entry><entry>101.101.101.2</entry></row><row><entry /><entry>b</entry><entry>AP of WMR-1</entry><entry>101.101.101.1</entry></row><row><entry /><entry>c</entry><entry>Client of WMR-1</entry><entry>102.102.102.2</entry></row><row><entry /><entry>d</entry><entry>AP of WMR-2:</entry><entry>102.102.102.1</entry></row><row><entry /><entry>e</entry><entry>Client of WMR-2:</entry><entry>103.103.103.2</entry></row><row><entry /><entry>f</entry><entry>Receiver:</entry><entry>103.103.103.1</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

Assuming that the Sender (a) now sends an IP packet to the Receiver (f), the destination field of the IP packet will be 103.103.103.1. When the packets travel down from the Application layer to the Wi-Fi layer (or MAC layer in OSI terms) of the Sender according to the OSI layering definition, the packet will be directly sent to the AP interface of WMR-<b>1</b> using infrastructure mode protocol. (To be more exact, the packet will also go through the PHY layer of the Sender. For the sake of simplicity, let's ignore the PHY layer, and take Wi-Fi layer as the bottom layer of OSI). In the 802.11 Infrastructure mode, packets leaving the Sender's Client interface will have to go to the AP interface of WMR-<b>1</b>.

The packet will then traverse up the OSI layer of WMR-<b>1</b> to the IP layer of the AP side. Noting that the packet is not destined to itself, it will then route the packet to an appropriate interface inside WMR-<b>1</b> according to a pre-configured routing table using pseudo-codes like below:

<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="56pt" align="left" /><colspec colname="1" colwidth="161pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP == 101.101.101.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to Client of WMR-1</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables><br /> As a result, the packet will be routed to the Client interface of WMR-<b>1</b>. When the packet reaches the Client Wi-Fi interface of WMR-<b>1</b>, again, it has no option but will be sent to the AP Wi-Fi interface of WMR-<b>2</b> by way of infrastructure mode protocol. Similarly, the packet will then traverse up the OSI layer of WMR-<b>2</b> to the IP layer of the AP side. Noting that the packet is not destined to itself, it will then route the packet to an appropriate interface inside WMR-<b>2</b> according to the example routing table below:

<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="56pt" align="left" /><colspec colname="1" colwidth="161pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP == 102.102.102.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to Client of WMR-2</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

In this example, the packet will be routed to the Client interface of WMR-<b>2</b> using infrastructure mode interface. When the packet reaches the Client Wi-Fi interface of WMR-<b>2</b>, it again has no option but being sent to the AP Wi-Fi interface of Receiver, also by way of infrastructure mode protocol. Since the Receiver is indeed the destination of the packet, its IP layer will accept the packet and forward it up according to the OSI model to its application below:

<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="63pt" align="left" /><colspec colname="1" colwidth="154pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP == 103.103.103.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to the Internet</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

If the destination address of the packet were not 103.103.103.1, it would have been routed to the interface leading to the Internet.

The wireless mesh network depicted in <figref idref="DRAWINGS">FIG. 4</figref> is a 2-dimensional generalization of the cascaded WMN of <figref idref="DRAWINGS">FIG. 3</figref> and comprises a plurality of WMR-<b>1</b>, or wireless mesh routers <b>860</b>, in mesh network connection. In this 2-dimensional mesh network connection deployment, the data transport mechanism is identical in substance to that depicted in <figref idref="DRAWINGS">FIG. 3</figref> and the descriptions above are incorporated herein mutatis mutandis by reference where appropriate. In particular, all inter-router or inter-WMR-<b>1</b>, or inter-wireless-mesh-routers <b>860</b> data communications as indicated by the dotted router interconnection lines are by way infrastructure mode protocol.

The cascade network of <figref idref="DRAWINGS">FIG. 3A</figref> is substantially identical to that of <figref idref="DRAWINGS">FIG. 3</figref>, except that WMR-<b>1</b> is replaced with an AP-AP wireless mesh router <b>870</b> and WMR-<b>2</b> is replaced with a client-client wireless mesh router <b>880</b>. The data transport mechanism in this cascade deployment is identical in substance to that depicted in <figref idref="DRAWINGS">FIG. 3</figref> and the descriptions above are incorporated herein mutatis mutandis by reference where appropriate.

The 2-dimensional wireless mesh network configuration of <figref idref="DRAWINGS">FIG. 4A</figref> is an example WMN comprising a mixture of wireless mesh routers <b>860</b>, <b>870</b>, and <b>880</b>. The data transport mechanism is in this cascade deployment is identical in substance to that depicted in <figref idref="DRAWINGS">FIG. 3</figref> and the descriptions above are incorporated herein mutatis mutandis by reference where appropriate. In particular, all inter-router or inter-wireless mesh routers <b>860</b>, <b>870</b>, <b>880</b> data communications as indicated by the dotted router interconnection lines are by way infrastructure mode protocol.

The cascade network of <figref idref="DRAWINGS">FIG. 3B</figref> is also substantially identical to that of <figref idref="DRAWINGS">FIG. 3</figref>, except that WMR-<b>1</b> and WMR-<b>2</b> having 2 Wi-Fi radio interfaces are replaced with wireless mesh router <b>890</b> having 2 virtual Wi-Fi radio interfaces. Wireless mesh router <b>890</b> have only one Wi-Fi radio interface. However, by using some software technique such as multi-threading, the single Wi-Fi radio interface of wireless router <b>890</b> behaves as an AP and as a client simultaneously. The virtual AP and client even have their own IP address. The data transport mechanism in this cascade deployment is identical in substance to that depicted in <figref idref="DRAWINGS">FIG. 3</figref> and the descriptions above are incorporated herein mutatis mutandis by reference where appropriate.

It is appreciated that the configuration of interfaces in a Wireless mesh router is fully flexible. Specifically, all Back-N compatible wireless mesh routers have 2 or more Wi-Fi interfaces (physical or virtual), and all interfaces must be configured as either AP or client.

To provide compatibility with existing ad-hoc MWN, a ‘mesh network adaptor’ is provided as depicted in <figref idref="DRAWINGS">FIG. 5</figref>. The mesh network adaptor <b>860</b> is a wireless router that is capable of interfacing both existing MWN and new MWN running different 802.11 standards. The old WMN is expanded with the latest 802.11 standard without replacing any old equipment.

The wireless mesh network of <figref idref="DRAWINGS">FIG. 6</figref> is similar to that of <figref idref="DRAWINGS">FIG. 3</figref>, except that two more Wireless Mesh Routers are included between Sender and Receiver. The data flow from Sender to Receiver depicted in <figref idref="DRAWINGS">FIG. 6</figref> is also similar to the data flow of <figref idref="DRAWINGS">FIG. 3</figref>. Assuming that the following exemplary IP addresses are assigned for the Wi-Fi interfaces as convenient examples:

<tables id="TABLE-US-00005" num="00005"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="28pt" align="left" /><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="84pt" align="left" /><colspec colname="3" colwidth="63pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>a</entry><entry>Sender:</entry><entry>1.1.1.2</entry></row><row><entry /><entry>b</entry><entry>AP of MN1</entry><entry>1.1.1.1</entry></row><row><entry /><entry>c</entry><entry>Client of MN1</entry><entry>1.1.2.2</entry></row><row><entry /><entry>d</entry><entry>AP of MN2</entry><entry>1.1.2.1</entry></row><row><entry /><entry>e</entry><entry>Client of MN2</entry><entry>1.1.3.2</entry></row><row><entry /><entry>f</entry><entry>AP of MN3</entry><entry>1.1.3.1</entry></row><row><entry /><entry>g</entry><entry>Client of MN3</entry><entry>1.1.4.2</entry></row><row><entry /><entry>h</entry><entry>AP of MN4</entry><entry>1.1.4.1</entry></row><row><entry /><entry>i</entry><entry>Client of MN4</entry><entry>1.1.5.2</entry></row><row><entry /><entry>j</entry><entry>Receiver</entry><entry>1.1.5.1</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

Since a client interface of one WMR must be wirelessly connected to an AP interface of another WMR before sending any data through 802.11, Client interface of Sender and the AP interface of the mesh node MN<b>1</b> are wirelessly associated. When data is sent from Sender's Client interface, the data will be directly sent to AP of MN<b>1</b> by way of infrastructure mode WiFi. The data will then traverse up the OSI layer of MN<b>1</b> to the IP layer of the AP interface. Noting that the packet is not destined to itself, it will then route the data to an appropriate interface using internal wired connection inside MN<b>1</b> according to a pre-configured routing table using pseudo-codes like below:

<tables id="TABLE-US-00006" num="00006"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="63pt" align="left" /><colspec colname="1" colwidth="154pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP == 1.1.1.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to Client of MN1</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

As a result, the data will be routed to Client interface of MN<b>1</b> using IP routing inside MN<b>1</b>. Client interface of MN<b>1</b> and AP interface of MN<b>2</b> will be wirelessly associated. When the data reaches the Client interface of MN<b>1</b>, it will be transmitted to AP interface of MN<b>2</b> by way of infrastructure mode WiFi. Similarly, the data will then traverse up the OSI layer of MN<b>2</b> to the IP layer of the AP side. Noting that the packet is not destined to itself, it will then route the data to an appropriate interface using internal wired connection inside MN<b>2</b> according to the example routing table below:

<tables id="TABLE-US-00007" num="00007"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="63pt" align="left" /><colspec colname="1" colwidth="154pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP == 1.1.2.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to Client of MN2</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

In this example, the data will be routed to Client interface of MN<b>2</b> using IP routing inside MN<b>2</b>. Client interface of MN<b>2</b> and AP interface of MN<b>3</b> are wirelessly associated. When the data reaches the Client Wi-Fi interface of MN<b>2</b>, it will be sent to the AP Wi-Fi interface of MN<b>3</b> by way of infrastructure mode WiFi. The data will then traverse up the OSI layer of MN<b>3</b> to the IP layer of the AP side. Noting that the data is not destined to itself, it will then route the data to an appropriate interface using internal wired connection inside MN<b>3</b> according to the example routing table below:

<tables id="TABLE-US-00008" num="00008"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="63pt" align="left" /><colspec colname="1" colwidth="154pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP == 1.1.3.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to Client of MN3</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

Accordingly, the data will be routed to Client interface of MN<b>3</b> using IP routing inside MN<b>3</b>. Client interface of MN<b>3</b> and AP interface of MN<b>4</b> are wirelessly associated. When the data reaches the Client Wi-Fi interface of MN<b>3</b>, it will be sent to the AP Wi-Fi interface of MN<b>4</b> by way of infrastructure mode WiFi. The data will then traverse up the OSI layer of MN<b>4</b> to the IP layer of the AP side. Noting that the data is not destined to itself, it will then route the data to an appropriate interface using internal wired connection inside MN<b>4</b> according to the example routing table below:

<tables id="TABLE-US-00009" num="00009"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="63pt" align="left" /><colspec colname="1" colwidth="154pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP == 1.1.4.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to Client of MN4</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

In this example, the data will be routed to Client interface of MN<b>4</b> using IP routing inside MN<b>4</b>. Client interface of MN<b>4</b> and AP interface of Receiver are wirelessly associated. When the data reaches the Client Wi-Fi interface of MN<b>4</b>, it will be sent to the AP Wi-Fi interface of Receiver by way of infrastructure mode WiFi. The data will then traverse up the OSI layer of Receiver to the IP layer of the AP side. Since the Receiver is indeed the destination of the data, its IP layer will accept the data and forward it up according to the OSI model to its application below:

<tables id="TABLE-US-00010" num="00010"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="offset" colwidth="63pt" align="left" /><colspec colname="1" colwidth="154pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>If (IP ==1.1.5.1)</entry></row><row><entry /><entry>  Send it to Application</entry></row><row><entry /><entry>Else</entry></row><row><entry /><entry>  Send it to the Internet</entry></row><row><entry /><entry namest="offset" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

If the destination address of the data were not 1.1.5.1, it would have been routed to the interface leading to the Internet.

When data are sent from Receiver to Sender, the data will traverse in a similar way. Specifically, data is transmitted between different routers by way of infrastructure mode WiFi and routed inside a router using IP routing.

In the above examples, a data rate of 300 Mbps is chosen because this is the highest speed rate stipulated by the state-of-the-art WiFi standard. It will be appreciated that the actual data rate can be any data rate between 54 Mbps to 300 Mbps without loss of generality. For example, the inter-router data rate can be set as 60, 80, 100, 120, 150, 200, 250, 300, etc. Furthermore it wil be appreciated that the maximum data rate will be determined by the data rate set by the latest WiFi standard and can be well above 300 Mbps in the future.

While the present disclosure is with reference to the above examples, it would be appreciated by persons skilled in the art that the examples are only provided as illustrations to assist understanding and are not meant to restrict scope of invention. For example, each interface of a Wireless mesh router is flexible to be configured as AP or Client only if a Client of a router can be wirelessly connected to an AP of another router before sending data and all the interfaces of a wireless mesh router are connected using IP routing. Also, there can be any number of interfaces inside a wireless mesh router. Furthermore, when routers are used an examples herein, the disclosure above are applicable to other relaying devices such as forwarding devices and switches without loss of generality.