|
Municipalities worldwide have either installed or are in the process of deploying Wi-Fi mesh networks. The user interface of a mesh network is standard Wi-Fi, but the interconnections between mesh nodes are proprietary. This limits the deployment of mesh networks in a particular area to a single vendor. 802.11s, however, should help make these networks more interoperable. With strong benefits of a municipality acquiring mesh nodes from a single vendor anyway, is 802.11s really worthwhile?
The deployment of Wi-Fi throughout municipalities has led to the development of specialized “mesh” Wi-Fi routers that mount on light poles and traffic lights to provide coverage in outdoor areas. This equipment, offered by vendors such as Tropos, BelAir, Cisco, Motorola and Strix, provide a Wi-Fi interface to users while also linking together (“meshing”) using vendor-proprietary protocols. If one particular mesh node can’t connect to the backbone of the network via a backhaul radio, that mesh node will connect to a nearby mesh node in order to hop packets through the network. This architecture allows the deployment of Wi-Fi throughout large municipalities by simply attaching the mesh nodes to light poles and supplying electrical power to them.
The mesh protocols go well beyond what the 802.11 /Wi-Fi standards define. As a result, interoperability (the meshing protocols) between mesh nodes from different vendors doesn’t exist. Thus, the 802.11 Working Group kicked off Task Group S in July 2004 to develop the 802.11s standard for mesh networking. 802.11s will provide topology discovery and path selection, something beyond the scope of traditional 802.11 access points. As of April 2007, the current state of the draft 802.11s standard is the D1.02 document, with ratification likely in 2008
There’s no indication yet which Wi-Fi mesh vendors will support 802.11s. In order to avoid a level playing field in the market, mesh vendors will likely always have proprietary routing enhancements beyond what 802.11s will provide. If you want to take full advantage of these additional functions, similar to 802.11b/g access points, then you’ll still need to use mesh nodes from the same vendor regardless of the adoption of 802.11s.
Acquisition of a single vendor for the entire mesh network is certainly beneficial. It means one contract and the ability to support common hardware. In this case, do we really need 802.11s? Please post your thoughts.
|