Saturday, January 26, 2008

sonic wireless mesh

A wireless mesh networks is a communications network made up of radio nodes in which there are at least two pathways of communication to each node. The coverage area of the radio nodes working as a single network becomes a mesh cloud. Access to this mesh cloud is dependent on the radio nodes working in harmony with each other to create a radio network. A mesh network is reliable and offers redundancy. When one node can no longer operate, all the rest can still communicate with each other, directly or through one or more intermediate nodes. The diagrams below illustrate how wireless mesh networks can self form and self heal.

Wireless mesh builds routes between nodes only as desired by originating nodes. It maintains these routes as long as they are needed by the originating node. Wireless mesh nodes forms paths in term of hops which connect together to form the wireless mesh network. Hops are the number of nodes between two a receiving and transmitting client i.e. Laptop, PC, Wi-Fi telephone, IP appliance, etc. Symbolically a Wireless Mesh network is represented by a network cloud.

Mesh nodes uses sequence numbers to ensure the freshness of routes (please note that various protocols may differ.) It is loop-free, self-starting, and scales to large numbers of nodes. Wireless Mesh Nodes builds routes using a route request, route reply query cycle. When a node desires a route to a destination for which it does not already have a route, it broadcasts a route request packet across the network. Nodes receiving this packet update their information for the source node and set up backwards pointers to the source node in the route tables. The wireless nodes also collect other active modes including IP address, current sequence number, and broadcast ID, and contains the most recent sequence number for the destination of which the source node is aware. A node receiving a route request may send a route reply when it is either the destination or if it has a route to the destination with corresponding sequence number greater than or equal to that contained in the route request. Nodes keep track of the route request through source IP address and broadcast ID. The nodes know when they receive a route request which they have already processed; they discard it and will not forward it.

As the backward pointers propagates back to the originating node, it then sets up forward pointers to the destination. Once the source node receives the backward pointers, it may begin to forward data packets to the destination. When the source later receives a backwards pointer containing a greater sequence number or contains the same sequence number with a smaller hop count, it may update its routing information for that destination and begin using the better route.

As long as the route remains active, it will continue to be maintained. A route is considered active as long as there are data packets periodically travelling from the source to the destination along that path. Once the source stops sending data packets, the links will time out and eventually be deleted from the intermediate node routing tables. Most wireless mesh nodes maintain routes for as long as the route is active. This includes maintaining hops for the life of the cloud. Because the network nodes can be mobile or shut down, it is likely that many link breakages along a route will occur during the lifetime of that route.

2 comments:

SSAJ- said...

WHAT A FUCKING BLOG IS THAT? THE WORST N UGLIEST BLOG I HAVE EVER SEEN!! SHOVE IT INTO YOUR MOM AND SISTER'S ASS!! RIGHT AWAY!! SUCK MY COCK N SWALLOW MY CUM!! INVITE YOUR SISTER N MOM TOO.. THEY WILL LIKE ITS TASTE TOO! CYA!! _|_ SIT WITH THEM ON IT N ROTATE! MUAAH!!

Anonymous said...

jkk