Method for enabling the efficient operation of arbitrarily interconnected mesh networks

METHOD FOR ENABLING THE EFFICIENT OPERATION OF ARBITRARILY INTERCONNECTED MESH NETWORKS

BACKGROUND

[0001] Field: Advancements in routing protocols for bridging networks are needed to provide improvements in performance, efficiency, and utility of use. Embodiments described elsewhere herein enable the improvements.

[0002] Related Art: Unless expressly identified as being publicly or well known, mention herein of techniques and concepts, including for context, definitions, or comparison purposes, should not be construed as an admission that such techniques and concepts are previously publicly known or otherwise part of the prior art. All references cited herein (if any), including patents, patent applications, and publications, are hereby incorporated by reference in their entireties, whether specifically incorporated or not, for all purposes.

Nothing herein is to be construed as an admission that any of the references are pertinent prior art, nor does it constitute any admission as to the contents or date of actual publication of these documents.

SUMMARY

[0003] The invention can be implemented in numerous ways, including as a process, an article of manufacture, an apparatus, a system, a composition of matter, and a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. An exposition of one or more embodiment? of the invention is provided in the Detailed Description. The Detailed Description includes an Introduction to facilitate the more rapid understanding of the remainder of the Detailed Description. The Introduction includes Illustrative Combinations that tersely summarize illustrative systems and methods in accordance with the concepts taught herein. As is discussed in more detail in the Conclusions, the invention encompasses all possible modifications and variations within the scope of the issued claims, which are appended to the very end of the issued patent.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

[0005] Fig. 1 illustrates selected details of various embodiments of techniques to reduce (or eliminate) loops, and to optimize unicast and broadcast packet flows of a multimesh.

[0006] Fig. 2 illustrates selected details of hardware aspects of an embodiment of a node.

[000η Fig. 3 illustrates selected details of software aspects of an embodiment of a node.

DETAILED DESCRIPTION

[0008] The invention can be implemented in numerous ways, including as a process, an article of manufacture, an apparatus, a system, a composition of matter, and a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention.

[0009] A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.

INTRODUCTION

[0010] This introduction is included only to facilitate the more rapid understanding of the Detailed Description. The invention is not limited to the concepts presented in the introduction, as the paragraphs of any introduction are necessarily an abridged view of the entire subject and are not meant to be an exhaustive or restrictive description. For example, the introduction that follows provides overview information limited by space and organization to only certain embodiments. There are in fact many other embodiments, including those to which claims will ultimately be drawn, which are discussed throughout the balance of the specification. As is discussed in more detail in the Conclusions, the invention encompasses all possible modifications and variations within the scope of the issued claims, which are appended to the very end of the issued patent.

[0011] Various embodiments relate to low overhead and low complexity techniques for enabling arbitrarily interconnected mesh networks to communicate information efficiently, enabling scalability and interoperability. A network formed as a result of interconnecting a set of mesh networks is referred to as a multi-mesh. Each of the mesh networks of the multi-mesh may have a respective (and possibly unique) internal configuration and operational modes. The techniques provide for all unicast packets to travel a corresponding best path across the interconnected meshes, and for avoiding forwarding loops of unicast and broadcast packets. The techniques further provide for forwarding packets along best paths across the multi-mesh when considered as a whole. Routing information and processing thereof are constrained to and are specific to each respective mesh of the multi-mesh, thus reducing routing processing and memory requirements compared to scenarios having all nodes in a single mesh.

Terms

[0012] Elsewhere herein terms are used to describe selected elements and aspects of various embodiments and implementations. Examples for selected terms follow.

[0013] Node: An example of a node is an electronic device.

[0014] Packet An example of a packet is that nodes communicate information to each other that is subdivided into packets.

[001S] Link: An example of a link is a conceptual representation of the ability of two (or more) nodes to communicate with each other. A link may be wired (the nodes being connected by a physical medium for carrying information such as electrical or optical interconnect) or wireless (the nodes being connected without a physical medium, e.g., via radio technology).

[0016] Path/Route: An example of a path/route is a sequence of one or more links.

[0017] Path Metric: An example of a path metric is a number that reflects the desirability of a path. For example, the number of links, e.g., the hop count of a path, is one possible metric. Paths with a lower hop count have advantages over paths with a higher hop count. The advantages include less resource usage (as there is reduced forwarding) and less likelihood of lost packets (as there are fewer chances for loss before packets reach respective destinations).

[0018] Best Path: An example of a best path is an ordered list of nodes that when transited (in order) by a packet result in an efficient traversal from a source to a destination, according to predetermined criteria. Since parameters and operating conditions vary over time, any best path is also a “known” best path; e.g. it is based on criteria evaluated at a particular point in time, and at a different point in time a different best path may be available. Best paths may also be considered to be “most nearly optimal” according to one or more metrics as measured with respect to a routing protocol responsible for determining the best paths.

[0019] Network: An example of a network is a set of nodes that are enabled to communicate with each other via any combination of wired and wireless links.

[0020] Mesh Network: An example of a mesh network is a set of nodes that selforganize into a multi-hop network In some usage scenarios the mesh network has limited resources (e.g. available bandwidth, available computational power, and available energy).

[0021] Multi-Mesh Network: An example of a multi-mesh network is a set of interconnected meshes appearing to operate as a single network from a perspective of a user of resources provided by the multi-mesh network.

[0022] Shared Access Network: An example of a shared access network is a network such that a packet transmitted by any node is overheard by all other nodes in the network. An example implementation of such a network is an 802.3 LAN.

[0023] Ingress Mesh: An example of an ingress mesh is a mesh where a packet enters a multi-mesh.

[0024] Egress Mesh: An example of an egress mesh is a mesh where a packet exits (or leaves) a multi-mesh.

[0025] Ingress Mesh Node: An example of an ingress mesh node is a node where a packet enters a mesh; e.g. the node forwarding the packet from a non-mesh link onto a mesh link/network.

[0026] Egress Mesh Node: An example of an egress mesh node is a node where a packet exits a mesh; e.g. the node forwarding the packet from a mesh link onto a non-mesh link/network.

[0027] Mesh Bridge (Node): An example of a mesh bridge is a node that is simultaneously participating in more than one mesh network at a time; e.g. the node is coupled to at least two mesh networks at once. Bridge nodes enable nodes connected on a first mesh (or that are part of the first mesh) to communicate with nodes connected on a second mesh (or that are part of the second mesh).

[0028] (Mesh) Bridge Link: An example of a mesh bridge link is a link between two bridge nodes (each being coupled to a respective mesh) used to forward traffic between the two meshes.

[0029J Ingress Bridge Node: An example of an ingress bridge node is the mesh bridge where a packet exits (or leaves) an ingress mesh.

[0030J Egress Bridge Node: An example of an egress bridge node is the mesh bridge where a packet enters an egress mesh.

[0031] Mesh Portal: An example of a mesh portal is a node that is part of a mesh network and is also connected to another (shared access) network. Mesh portals enable nodes connected to the mesh, or that are part of the mesh, to communicate with nodes that are part of the shared access network, or that may be reached through the shared access network. In some embodiments the mesh network appears to outside networks as a transparent layer-2 transport, i.e. a packet injected into the mesh at one portal exits the mesh at another portal unmodified.

[0032] Ingress Mesh Portal: An example of an ingress mesh portal is the portal at which a packet enters a mesh, e.g., the portal that forwards the packet from a non-mesh link/network onto a mesh link/network.

[0033] Egress Mesh Portal: An example of an egress mesh portal is the portal at which a packet exits the mesh, e.g., the portal that forwards the packet from a mesh link/network onto a non-mesh link/network.

[0034] Mesh Client Interface: An example of a mesh client interface is an interface (that is part of a node of a mesh network) for coupling to a client device.

[0035] Mesh Network Gateway Interface (mesh NGi): An example of a mesh NGI is a node that is part of a mesh network (e.g., has an interface configured to be part of the mesh network) and is also connected to another network (e.g., has an interface configured to be on the other network). Mesh NGIs enable nodes connected to a mesh network, or that are part of the mesh, to communicate with nodes that are part of a shared access network, or that may be reached through the shared access network. In some embodiments the mesh network appears to outside networks as a transparent layer 2 transport: a packet injected into the mesh at one NGI exits the mesh at another NGI or Client Interface unmodified.

[0036] Ingress Mesh Interface: An example of an ingress mess interface is an interface at which a packet enters a mesh, e.g., the interface that forwards the packet from a non-mesh link onto a mesh link/network.

[0037] Egress Mesh Interface: An example of an egress mesh interface is the interface at which a packet exits the mesh, e.g., the interface that forwards the packet from a mesh link onto a non-mesh link/network.

[0038] Unicast: An example of unicast is communication between two nodes.

[0039] Broadcast: An example of broadcast is communication from one node intended to reach a plurality of nodes. In some usage scenarios the plurality of nodes includes all nodes on a network. In some scenarios a broadcast may not reach all intended nodes (due to packet loss, for example).

[0040] Flood: An example of a flood is a broadcast sent by a node that is in turn rebroadcast by every other node receiving the broadcast, thus potentially reaching all nodes in a network.

[0041] Routing Protocol: An example of a routing protocol is a set of mechanisms implemented on each node in a mesh network, wherein the mechanisms serve to discover information about the network and enable each node on the network to communicate with other nodes of the network, even when the other nodes are multiple hops away from the respective node.

[0042] Path Accumulation: An example of path accumulation is when each node forwarding a packet adds its respective address to the packet.

ILLUSTRATIVE COMBINATIONS

[0043] The following is a collection of paragraphs that tersely summarize illustrative systems and methods in accordance with the concepts taught herein. Each of the paragraphs highlights various combinations of features using an informal pseudo-claim format. These compressed descriptions are not meant to be mutually exclusive, exhaustive, or restrictive and the invention is not limited to these highlighted combinations. As is discussed in more detail in the Conclusion section, the invention encompasses all possible modifications and variations within the scope of the issued claims, which are appended to the very end of the patent.

[0044] A first embodiment comprising a method comprising operating first and second wireless mesh networks, via a bridge link coupling the wireless mesh networks, forming a multi-mesh network by forwarding packets between the wireless mesh networks; and eliminating redundant broadcast flooding within each respective wireless mesh network. The aforementioned embodiment wherein the eliminating of redundant broadcast flooding comprises assigning identifiers to packets. The aforementioned embodiment wherein each identifier comprises a source address field based on a source address of the packet corresponding to the identifier. The aforementioned embodiment wherein each identifier comprises an identification field uniquely identifying each respective packet in a context of an associated entry point into the multi-mesh network. The aforementioned embodiment wherein the identifiers are included in pre-existing control packets.

[0045] A first comparative example comprising a method comprising operating first and second wireless mesh networks; via a bridge link coupling the wireless mesh networks, forming a multi-mesh network by forwarding packets between the wireless mesh networks; and preventing forwarding loops between the wireless mesh networks. The aforementioned comparative example wherein the preventing of forwarding loops comprises assigning identifiers to packets. The aforementioned comparative example wherein the packets include broadcast packets. The aforementioned comparative example wherein each identifier comprises a source address field based on a source address corresponding to a node generating the identifier. The aforementioned comparative example wherein each identifier further comprises an identification field uniquely identifying each respective packet in a context of an associated entry point into the multi-mesh network. The 5 aforementioned comparative example wherein the associated entry point is an ingress mesh node. The aforementioned comparative example wherein the identifiers are included in preexisting control packets. The first comparative example wherein the preventing of forwarding loops comprises assigning identifiers to broadcast and unicast packets.

[0046] The first comparative example comprising forwarding a unicast packet 10 according to a best path. The aforementioned example wherein the best path is determined according to paths learned from accumulated path cost information. The aforementioned example wherein the determining of the best path is at least partially in response to forwarding a packet. The aforementioned example wherein the accumulated path cost information is accumulated in at least one of a pre-existing control packet and a pre-existing 15 data packet. The aforementioned example wherein the accumulated path cost information is a cost of forwarding a packet through each mesh the packet has traversed.

[0047] A second comparative example comprising a method comprising operating first and second wireless mesh networks, via a bridge link coupling the wireless mesh networks, forming a multi-mesh network by forwarding packets between the wireless mesh 20 networks; and forwarding packets according to efficient routes based at least in part on route cost information. The aforementioned example wherein the route cost information is accumulated in packets during bridge link traversal. The aforementioned example wherein the route cost information is included in pre-existing control packets.

[0048] The first embodiment wherein the bridge link is a wireless link. The first 25 embodiment wherein the bridge link is a plurality of wireless links. The first embodiment wherein the bridge link is a wired link. The first embodiment wherein the bridge link comprises at least one wireless link and at least one wired link.

[0049] The first embodiment wherein the first and the second wireless mesh networks operate according to frequency diversity. The first embodiment wherein the 30 frequency diversity comprises operating the first and the second wireless mesh networks according to distinct frequency spectra. The first embodiment wherein the first and the second wireless mesh networks operate according to respective first and second frequency allocations. The first embodiment wherein the first and the second wireless mesh networks operate according to respective first and second frequency allocations and at least one of the frequency allocations corresponds to an 802.11 compatible channel. The first embodiment wherein the first and the second wireless mesh networks operate according to respective first and second frequency allocations and at least one of the frequency allocations corresponds to at least one of an 802.1 la, an 802.1 lb, and an 802.11g compatible channel. The first embodiment wherein the first and the second wireless mesh networks operate according to partially overlapping or interfering frequency allocations. The first embodiment wherein the first and the second wireless mesh networks operate according to identical frequency allocations. The first embodiment wherein the first and the second wireless mesh networks operate according to non-overlapping or non-interfering frequency allocations.

[0050] The first embodiment wherein the first and the second wireless mesh networks operate according to respective first and second internal routing protocols. The first embodiment wherein the first and the second wireless mesh networks operate according to identical internal routing protocols. The first embodiment wherein the first and the second wireless mesh networks operate according to respective distinct routing options. The first embodiment wherein the first and the second wireless mesh networks operate according to respective distinct routing parameters. The first embodiment wherein the first and the second wireless mesh networks operate according to identical internal routing protocols and each internal routing protocol is operable according to respective distinct routing options. The first embodiment wherein the first and the second wireless mesh networks operate according to identical internal routing protocols and each internal routing protocol is operable according to respective distinct routing parameters. The first embodiment wherein the first and the second wireless mesh networks operate according to identical media access control layers. Any of the first, second, and third embodiments wherein the first and the second wireless mesh networks operate according to distinct media access control layers. The first embodiment wherein the first and the second wireless mesh networks operate according to identical physical layers. The first embodiment wherein the first and the second wireless mesh networks operate according to distinct physical layers.

[0051] A second embodiment comprising all of the elements, respectively of the first embodiment wherein the bridge link is a first bridge link; and further comprising via a second bridge link, coupling the first and the second wireless mesh networks, extending the multi-mesh network by forwarding packets between the first and the second mesh networks;

and wherein the second bridge link coupling is interfaced to the first and the second wireless mesh networks via respective third and fourth mesh bridge nodes. The second embodiment wherein the first and second bridge link couplings are operable according to a load balancing technique. The second embodiment wherein the first and second bridge link couplings are operable according to a redundancy/failover technique.

[0052] A third comparative example comprising all of the elements of the first embodiment wherein the bridge link is operable in conjunction with a bridge link protocol. The third comparative example wherein there are no packets dedicated for use by the bridge link protocol.

[0053] A fourth comparative example comprising a method comprising operating first and second wireless mesh networks, via first and second bridge links coupling the wireless mesh networks, forming a multi-mesh network by forwarding packets between the wireless mesh networks; and operating the bridge links according to a load balancing technique. The aforementioned example further comprising preventing forwarding loops between the wireless mesh networks. The aforementioned example wherein the preventing of forwarding loops comprises assigning identifiers to packets. The aforementioned example wherein the packets include broadcast packets. The aforementioned example wherein each identifier comprises a source address field based on a source address corresponding to a node generating the identifier. The aforementioned example wherein each identifier further comprises an identification field uniquely identifying each respective packet in a context of an associated entry point into the multi-mesh network. The aforementioned example wherein the associated entry point is an ingress mesh node. The aforementioned example wherein the identifiers are included in pre-existing control packets. [0054] A third embodiment comprising a method comprising operating first and second wireless mesh networks, via first and second bridge links coupling the wireless mesh networks, forming a multi-mesh network by forwarding packets between the wireless mesh networks; and operating the bridge links according to a load balancing technique and further comprising eliminating redundant broadcast flooding within each respective wireless mesh network. The aforementioned embodiment wherein the eliminating of redundant broadcast flooding comprises assigning identifiers to packets. The aforementioned embodiment wherein each identifier comprises a source address field based on a source address of the packet corresponding to the identifier. The aforementioned embodiment wherein each identifier comprises an identification field uniquely identifying each respective packet in a context of an associated entry point into the multi-mesh network. The aforementioned embodiment wherein the identifiers are included in pre-existing control packets.

[0055] As a fifth comparative example; the third embodiment further comprising forwarding packets according to efficient routes based at least in part on route cost information. The aforementioned example wherein the route cost information is accumulated in packets during bridge link traversal. The aforementioned example wherein the route cost information is included in pre-existing control packets.

[0056] A sixth comparative example comprising a method comprising operating first and second wireless mesh networks; via first and second bridge links coupling the wireless mesh networks, forming a multi-mesh network by forwarding packets between the wireless mesh networks; and operating the bridge links according to a redundancy/failure technique. The aforementioned example further comprising preventing forwarding loops between the wireless mesh networks. The aforementioned example wherein the preventing of forwarding loops comprises assigning identifiers to packets. The aforementioned example wherein the packets include broadcast packets. The aforementioned example wherein each identifier comprises a source address field based on a source address corresponding to a node generating the identifier. The aforementioned example wherein each identifier further comprises an identification field uniquely identifying each respective packet in a context of an associated entry point into the multi-mesh network. The aforementioned example wherein the associated entry point is an ingress mesh node. The aforementioned example wherein the identifiers are included in pre-existing control packets. [0057] A fourth embodiment comprising a method comprising operating first and second wireless mesh networks; via first and second bridge links coupling the wireless mesh networks, forming a multi-mesh network by forwarding packets between the wireless mesh networks; and operating the bridge links according to a redundancy/failure technique and further comprising eliminating redundant broadcast flooding within each respective wireless mesh network. The aforementioned embodiment wherein the eliminating of redundant broadcast flooding comprises assigning identifiers to packets. The aforementioned embodiment wherein each identifier comprises a source address field based on a source address of the packet corresponding to the identifier. The aforementioned embodiment wherein each identifier comprises an identification field uniquely identifying each respective packet in a context of an associated entry point into the multi-mesh network. The aforementioned embodiment wherein the identifiers are included in pre-existing control packets.

[0058] As a seventh comparative example; the fourth embodiment further comprising forwarding packets according to efficient routes based at least in part on route cost information. The aforementioned example wherein the route cost information is accumulated in packets during bridge link traversal. The aforementioned example wherein the route cost information is included in pre-existing control packets.

[0059] A fifth embodiment of a computer readable medium having a set of instructions stored therein which when executed by a processing element causes the processing element to perform functions comprising any of the first through fourth embodiments.

[0060] A sixth embodiment of a system comprising a processor and a memory adapted to store instructions to be executed by the processor, the instructions implementing any of the first through fourth embodiments.

MESH SCALING AND INTEROPERABILITY

[0061] As the size of a wireless mesh increases, using a single radio frequency in the entire mesh may become a limitation as wireless device transmissions interfere with each other. As a result, bandwidth available for nodes in the mesh decreases. Some embodiments reduce same-frequency interference effects by breaking up relatively larger meshes into smaller meshes. Each of the smaller meshes is then configured to operate at a respective unique (e.g. non-interfering) radio frequency, thus reducing interference from nodes operating in physically neighbouring meshes.

[0062] Also as the size of the wireless mesh increases, memory and processing requirements associated with mesh routing protocol operating increase. Such routing protocol operations include storing information describing how to reach selected nodes of the wireless mesh and determining a next node address to send a packet to in order to proceed with forwarding the packet. Some embodiments reduce large-mesh routing protocol resource requirements by breaking up relatively larger meshes into smaller meshes. Each of the smaller meshes then operates routing protocols according to constraints associated with the respective smaller mesh. Thus splitting relatively larger meshes into smaller meshes improves scalability of mesh performance and operating resource cost.

[0063] In some usage scenarios, as mesh technology evolves, relatively newer mesh network installations may be unable to interoperate with relatively older installations. Similarly, even when a new installation and an old installation are built of the same of substantially similar technology, differing user requirements may lead to the new and the old installations being of unique configurations, capabilities, or both. Some embodiments enable interconnection of dissimilar meshes (i.e. provide for communication between meshes of differing internal configuration or operation).

[0064] As an example usage scenario, consider a mesh network deployed in a large city. The mesh network may have more than 1000 mesh nodes, and may be broken up into smaller meshes of approximately 50 nodes each. Each small mesh (or collections thereof) may be deployed independently by a different vendor, but the overall network remains operable as a multi-mesh. Various portions of the deployment may be configured for residential access, while other portions of the deployment may be configured for business access.

MESH INTERCONNECTIONS AND BRIDGING

[0065] In some embodiments a wireless mesh may be divided into smaller (sub)meshes interconnected through Mesh Bridge nodes operated in part according to a bridging protocol. A first Mesh Bridge in a first mesh network is coupled via a point-topoint (wire or wireless) link to a second Mesh Bridge in a second mesh network. The pointto-point link coupling the Mesh Bridges is referred to as a bridge link. In some embodiments a bridge link includes a plurality of point-to-point links, and in some embodiments a plurality of bridge links may enable communication between a pair of meshes. The pluralities of links and bridge links provide higher overall throughput between meshes and also optionally enable load balancing within meshes. In some embodiments nodes in each respective (sub)mesh may be configured to operate at corresponding unique/non-interfering frequencies, such that nodes in physically nearby (or adjacent) meshes operate with reduced interference. In some embodiments nodes in selected (sub)meshes may be configured to operate at identical or overlapping/interfering frequency bands if interference is not an issue. For example, a bridge link coupling (sub)meshes operating at identical or overlapping frequency bands may provide for a large enough physical separation of the coupled (sub)meshes to prevent substantial interference.

Multiple Mesh Operation

[0066] Efficient operation of interconnected multiple meshes includes techniques for reducing (or eliminating) loops, as well as optimized unicast and broadcast packet 5 forwarding. For a first example, if meshes are interconnected through bridge links that form a loop, then in some usage scenarios packets passed from one mesh to another are augmented with control information used to prevent the packets from being passed around the loop multiple times or in some scenarios indefinitely (and thus potentially leading the network into congestion collapse). In some usage scenarios one or more loop 10 interconnections may be used to provide redundancy or may be an installation mistake, such as when multiple customers own various meshes in a multi-mesh and the customers lack coordination with each other.

[0067] As a second example, if multiple connections between two meshes of a multi-mesh exist, then overall multi-mesh efficiency is increased by enabling unicast 15 packets to follow an overall best path through the multi-mesh. In other words, bandwidth, latency, and resource utilization are improved by determining a path that is most efficient with respect to the entire multi-mesh network, rather than with respect to each individual mesh.

[0068] As a third example, in usage scenarios where individual meshes of a multi20 mesh distribute broadcast packets via flooding, control information is included in the broadcast packets when the packets enter the mesh (e.g. before sending across any bridge link). The control information enables reduction or elimination of redundant broadcast packet flooding that would otherwise occur when equivalent copies of a broadcast packet enter one of the individual meshes via a plurality of different bridge links, with each of the 25 copies being treated as a distinct broadcast packet to be flooded. The control information enables suppression of the otherwise superfluous multiple floods.

[0069] As a fourth example, in some usage scenarios where loops between individual meshes of a multi-mesh are possible (such as via bridge links), control information is included in packets before sending across a bridge link. The control 30 information enables reduction or elimination of otherwise potentially infinite looping behaviour between the individual meshes that may otherwise lead to a congestion collapse.

[0070] Fig. 1 illustrates selected details of various embodiments of techniques to reduce (or eliminate) loops, and to optimise unicast and broadcast packet flows of a multi15 mesh in part according to a bridging protocol. In some usage scenarios the techniques operate with no additional control packet overhead, relatively minimized control byte overhead, and reduced protocol complexity. The illustrated multi-mesh includes individual meshes Mesh 1121, Mesh 2 122, Mesh 3 123, and Mesh 4 124. The meshes are bridged via -5 several bridges, illustrated as Bridges 1-12 (101-112, respectively). Bridges 1 and 3 bridge

Meshes 1 and 2, respectively, as do Bridges 2 and 4. Bridges 9 and 7, respectively, bridge Meshes 4 and 3, as do Bridges 10 and 8. Bridges 12 and 11 bridge Meshes 1 and 4, respectively. Bridges 5 and 6, respectively, bridge Meshes 2 and 3 via Wireless Link 130. Ingress Mesh Node 1141 provides a portal for packets to enter the multi-mesh, for example 10 from the Internet, a Local Area Network (LAN), a Wide Area Network (WAN), or any other suitable network. Egress Mesh Nodes 1 and 2 (151 and 152, respectively) provide portals for packets to exit the multi-mesh, for example to the Internet, a LAN, a WAN, or any other suitable network. In some embodiments a node may operate simultaneously as an Ingress Mesh Node and an Egress Mesh Node, providing portals for packet entry to and exit 15 from the multi-mesh.

[0071] As an example of operation, when a Mesh Bridge receives a broadcast packet from one mesh (e.g. Mesh 1), the Mesh Bridge forwards the packet across a bridge link to another mesh (e.g. Mesh 2). Before forwarding the packet, the Mesh Bridge strips the packet of any routing information specific to the mesh that was just traversed mesh (e.g. 20 Mesh 1). The stripped information includes path cost information associated with traversal of the packet through the just-traversed mesh (e.g. Mesh 1). The path cost information is appended to the packet in preparation for the forwarding. The broadcast packet is subsequently forwarded to other meshes.

[0072] Thus information relating to path cost is accumulated as the broadcast 25 packet traverses the multi-mesh. Accumulated path cost information corresponds to the cost of forwarding a packet through each mesh the packet has traversed up to the point that the accumulated path cost information is computed (or updated). In some examples, a mesh hop-count metric is incremented for each traversed mesh. In some examples a mesh-cost metric is computed and stored for each traversed mesh. In some examples a mesh metric30 type, describing a type of cost metric associated with a mesh, is stored for each traversed mesh. In some examples, a minimum link metric over all links is used as a path metric. Paths are compared based on the metrics. In some examples the comparison is based on part of the metric value, and in some examples the comparison is based in part on the mesh metric-type. In some examples, the mesh metric-type serves as an (implicit) metric value (such as a “High Bandwidth” and a “Low Bandwidth” mesh metric-type context).

[0073] In some examples there is a bridge table having one entry for each bridge node. Each entry includes an address and a status for a destination bridge, and a next hop bridge address list. Each element of the next hop bridge address list includes a cost to the destination bridge via a bridge identified by the respective next hop bridge address, and a status of a bridge link coupling to the respective next hop bridge.

[0074] An Egress Mesh Node receiving (redundant) copies of the broadcast packet (for example due to multiple paths to the Egress Mesh Node) compares respective path 10 costs in the copies and determined a path with a relatively best overall cost for future use.

In examples where mesh metrics are accumulated separately and one or more metric types are unknown, portions of paths taken through a mesh may be compared.

[0075] Mesh Bridges and Egress Mesh Nodes receiving and forwarding a broadcast packet learn about a best path through each respective mesh (in the sequences of meshes the 15 packet has traversed) by examining and processing control information included in the packet. The best path learned includes a best path between the Ingress Mesh Node of the broadcast and the respective Mesh Bridge and Egress Mesh Node forwarding the broadcast packet. The control information includes path cost information added as the packet has been forwarded across bridge links, a next bridge to forward a packet to along a path, and optionally Mesh Bridge nodes traversed so far along the path. In some examples learning about best paths through the sequence of meshes traversed is performed without knowledge of how packets are routed within each mesh (i.e. information concerning bridge links traversed is sufficient). In some examples learning about best paths through the sequence of meshes traversed is performed using metrics associated with the meshes traversed and a metric associated with a next bridge a packet is to be forwarded across. In some examples the metric is a hop-count metric, and the best path is the route having the smallest hopcount. Other metrics for best path determination may be used based on implementation dependent criteria, as the techniques discussed elsewhere herein are independent of best path determination details.

[0076] A unicast packet is forwarded by an Ingress Mesh Node to a next Mesh Bridge along the best path learned during a previous forwarding of a broadcast packet in the opposite direction (e.g.., from the destination of the unicast packet). A Mesh Bridge forwards the unicast packet across a bridge link to a neighboring mesh if the packet came from a mesh the Mesh Bridge is included in. If the packet came from a neighboring mesh (e.g., across a bridge link), then the Mesh Bridge forwards the packet to a Mesh Bridge along the best path to the destination, or to an Egress Mesh Node if the mesh the Mesh Bridge is included in also includes the destination (e.g. the packet has entered the final mesh it is to traverse). A unicast packet to an unknown destination is forwarded as a broadcast flood (similar to layer-2 switch flooding) thus enabling learning bridge forwarding information for use in forwarding subsequent packets.

[0077] A unique ID is assigned to each broadcast packet by the Ingress Mesh Node where the broadcast packet enters the multi-mesh and the ID is preserved as the packet is forwarded across bridge links. The ID may be used for duplicate detection at each mesh node and at each Mesh Bridge, thus preventing loops within each mesh and also among meshes. The ID includes two elements. A first element is an address associated with the node generating the ID, and thus the first element is unique throughout the multi-mesh. A second element is a sequence number (or similar field) unique to the broadcast packet with respect to other broadcast packets identified by the node generating the ID, and thus the second element may be non-unique with respect to second elements of IDs generated by other nodes. Therefore the second element (and hence the entire ID) may be generated independently by nodes. In other words, no inter-node communication is required to generate IDs that are unique in the context of the entire multi-mesh).

[0078] In some operating scenarios identifiers are assigned to broadcast packets and in other operating scenarios identifiers are assigned to unicast and broadcast packets. Unicast packets may receive identifiers when, for example, a packet is initially sent as a unicast packet, but the unicast packet reaches a mesh bridge not having state to forward the unicast packet (for example the forwarding state may have expired). The unicast packet is then treated as a packet to an unknown destination and is flooded (like a broadcast packet) inside the mesh the mesh bridge is forwarding the unicast packet into. Subsequently the unicast packet is treated as a broadcast packet, including receiving an identifier assignment, in order to prevent looping.

[0079] Individual meshes of a multi-mesh may operate according to various characteristics, including routing protocols, routing options, Media Access Control (MAC) layers, and PHYsical access (PHY) layers. Characteristics of each mesh of the multi-mesh may be varied independently of characteristics of other meshes in the multi-mesh. For example, a first mesh may operate with a first routing protocol, while all other meshes may operate with a different routing protocol. For another example, each mesh may operate with a respective distinct routing protocol. For another example, every mesh may operate with the same routing protocol. Similar variations may be made for the other characteristics (routing options, MAC layers, and PHY layers).

[0080] Although the link enabling communication between Bridge 5 and Bridge 6 is illustrated as a wireless link (e.g. a radio link such as an 802.11 link), in some embodiments the link may be a wired link (such as an Ethernet link). In some embodiments the illustrated link is representative of a single link, while in other embodiments the illustrated link is representative of two or more links (wireless, wired, or both together). In embodiments having two or more links coupling the same two meshes, the two or more links may be operated in a load balancing manner, a failover/redundancy manner, or both.

NODE HARDWARE AND SOFTWARE

[0081] Fig. 2 illustrates selected details of hardware aspects of an embodiment of a node. The illustrated node includes Processor 205 coupled to various types of storage, including volatile read/write memory “Memory Bank” elements 201.1-2 via DRAM Memory Interface 202, and non-volatile read/write memory FLASH 203 and EEPROM 204 elements. The processor is further coupled to Ethernet Interface 206 providing a plurality of Ethernet Ports 207 for establishing wired links, and Wireless Interface 209 providing radio communication of packets for establishing wireless links. In some embodiments the Wireless Interface is compatible with an IEEE 802.11 wireless communication standard (such as any of 802.11a, 802.1 lb, and 802.11g). In some embodiments the Wireless Interface operates (in conjunction with any combination of hardware and software elements) to collect statistics with respect to neighboring nodes of a mesh. The statistics may include any combination of signal strength and link quality. In some embodiments the Wireless Interface is configurable to drop all packets below a settable Received Signal Strength Indicator (RSSI) threshold. The illustrated partitioning is only one example, as other equivalent embodiments of a node are possible.

[0082] The illustrated node may function as any one of the nodes illustrated in Fig.

1, including an Ingress Mesh Node, an Egress Mesh Node, and a Bridge. The Wireless Interface of Fig. 2 may enable communication with nodes internal to the mesh (not explicitly illustrated in Fig. 1, but understood to be elements of each of Meshes 1,2,3, and 4). The Wireless Interface may also provide a wireless Bridge Link when a node in accordance with Fig. 2 is used as a Bridge Node, for example any of Bridges 1 through 12 of Fig. 1. The Ethernet Interface of Fig. 2 may provide Ethernet ports for wired bridge links (including loadbalancing or redundancy/failover Bridge Links) in embodiments in accordance with Fig. 1 having one or more wired links. One or more of the Ethernet ports provided by the Ethernet Interface may also be used to provide pathways for packets entering (exiting) the mesh when a node according to Fig. 2 is operated as an Ingress (Egress) Mesh Node. Any combination of the storage elements (DRAM, FLASH, and EEPROM) may store one or more bridge tables, according to various usage scenarios.

[0083] In operation the processor fetches instructions from any combination of the storage elements (DRAM, FLASH, and EEPROM) and executes the instructions. Some of the instructions correspond to software associated with operating the Bridge Links in conjunction with a bridge link protocol. Portions of the bridge link protocol control operation of any combination of the Wireless Interface and the Ethernet Interface. Accumulated path ^:cost information may be stored in any combination of the storage elements according to instructions executed during processing associated with the bridge link protocol.

[0084] Fig. 3 illustrates selected details of software aspects of an embodiment of a node. The illustrated software includes Network Management System (NMS) Manager 301 interfacing to Network Interface Manager 302 and Fault, Configuration, Accounting, Performance, and Security (FCAPS) Manager 303. In some embodiments the NMS interfaces between management software operating external to the node and software operating internal to the node (such as various applications and FCAPS). The Network Interface Manager manages physical network interfaces (such as the Ethernet and Wireless Interfaces of a node). The Network Interface Manager assists the NMS in passing dynamic configuration changes (as requested by a user) through the management software to FCAPS. In some embodiments FCAPS includes functions to store and retrieve configuration information, and FCAPS functions serve all applications requiring persistent configuration information. FCAPS may also assist in collecting fault information and statistics and performance data from various operating modules of the node. FCAPS may pass any portion of the collected information, statistics, and data to the NMS.

[0085] Kernel Interface 310 interfaces the Managers to Routing and Transport Protocols layer 311 and Flash File System module 313. The Routing Protocols include the bridge link protocol and portions of software relating to maintenance of and reference to a bridge table. The Transport Protocols include TCP and UDP. The Flash File System module interfaces to Flash Driver 316 that is illustrated conceptually coupled to FLASH hardware element 323 that is representative of a flash file system stored in any combination of the FLASH and EEPROM elements of Fig. 2. Layer-2 Abstraction Layer 312 interfaces the Routing and Transport Protocols to Ethernet and Radio Drivers 314 and 315, respectively.

The Ethernet Driver is illustrated conceptually coupled to Ethernet Interface 326 that is representative of the Ethernet Interface of Fig. 2. The Radio Driver is illustrated conceptually coupled to Wireless Interface 329 that is representative of the Wireless Interface of Fig. 2. In some embodiments the software may also include a serial driver. The software is stored on a computer readable medium (e.g. any combination of the DRAM, FLASH, and EEPROM elements), and is executed by the processor. The illustrated partitioning is an example only, as many other equivalent arrangements of layers are possible.

CONCLUSION

[0086] Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided.

There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive. It will be understood that many variations in construction, arrangement and use are possible consistent with the teachings and within the scope of the claims appended to the issued patent. For example, interconnect and function-unit bit-widths, clock speeds, and the type of technology used may generally be varied in each component block. The order and arrangement of flowchart and flow diagram process and function elements may generally be varied. Also, unless specifically stated to the contrary, the value ranges specified, the maximum and minimum values used, or other particular specifications (such as integration techniques and design flow technologies), are merely those of the illustrative embodiments, can be expected to track improvements and changes in implementation technology, and should not be construed as limitations.

[0087] Functionally equivalent techniques known to those of ordinary skill in the art may be employed instead of those illustrated to implement various components, sub-systems, functions, operations, routines, and sub-routines. The names given to interconnect, logic, functions, and routines are merely illustrative, and should not be construed as limiting the concepts taught. It is also understood that many design functional aspects may be carried out in either hardware (i.e., generally dedicated circuitry) or software (i.e., via some manner of programmed controller or processor), as a function of implementation dependent design constraints and the technology trends of faster processing (which facilitates migration of functions previously in hardware into software) and higher integration density (which facilitates migration of functions previously in software into hardware). Specific variations may include, but are not limited to: differences in networking technology (such as wired/wireless, protocols, and bandwidths); and other variations to be expected when implementing the concepts taught herein in accordance with the unique engineering and business constraints of a particular application.

[0088] The embodiments have been illustrated with detail and environmental context well beyond that required for a minimal implementation of many of aspects of the concepts taught. Those of ordinary skill in the art will recognize that variations may omit disclosed components without altering the basic cooperation among the remaining elements. It is thus understood that much of the details disclosed are not required to implement various aspects of the concepts taught. To the extent that the remaining elements are distinguishable from the prior art, omitted components are not limiting on the concepts taught herein.

[0089] All such variations in design comprise insubstantial changes over the teachings conveyed by the illustrative embodiments. It is also understood that the concepts taught herein have broad applicability to other networking and communication applications, and are not limited to the particular application or industry of the illustrated embodiments. The invention is thus to be construed as including all possible modifications and variations encompassed within the scope of the claims appended to the issued patent.