Differences

This shows you the differences between two versions of the page.

--- etc:common_activities:olpc:mesh:definition_eng [2008/09/04 04:55] – kkv
+++ etc:common_activities:olpc:mesh:definition_eng [2008/09/20 21:52] (current) – raa
@@ Line 5: / Line 5: @@
 === Intro ===
-Nowadays mobile and ultramobile devices able to maintain a wireless connection with each other and to form a **client** mesh network are becoming more and more spred. The basic problem lies in optimal bandwidth sharing between a management traffic and a user one. On one hand it is necessary to provide effective routing and quick reaction on unit porting/disconnection, on the other hand a high-level service (QoS) of payload data transfer is extremely important too.
+Nowadays mobile and ultramobile devices able to maintain a wireless connection with each other and to form a **client** mesh network are becoming more and more spread. The basic problem lies in optimal bandwidth sharing between a management traffic and a user one. On one hand it is necessary to provide effective routing and quick reaction on unit porting/disconnection, on the other hand a high-level service (QoS) of payload data transfer is extremely important too.
 === Environments ===
@@ Line 17: / Line 17: @@
   * unefficiency of management traffic limitation algorithms in dynamic networks (dynamic both by their topology and data flows structure),
   * primitivity of topology changing algorithms for load balancing in Ad Hoc networks,
-  * absence of formal mesh networks behaviour models and therefore predominance of empiric network management rules above algoritmic ones.
+  * absence of formal mesh networks behaviour models and therefore predominance of empiric network management rules above algorithmic ones.
 === Research directions ===
@@ Line 25: / Line 25: @@
 One of research directions is an adequate mesh networks model development which would take into account the particular qualities of modern wireless devices and ways of their usage (content exchange, teleconferences, games etc). In the context of model development it is intended to observe current states of algorithms, standards and routing protocols realizations for Ad Hoc and Mesh networks. The model should include:
   * QoS control,
-  * dynamic topology recofiguration,
+  * dynamic topology reconfiguration,
   * management traffic volume control,
   * load balancing.
@@ Line 31: / Line 31: @@
 ** Routing algorithm development **
-Mesh network infrastructure model is intended to help in developing of a routing/controlling algoritm for client mesh network that would provide adaptive bandwidth sharing between management and user traffic with considering of network topology and the way of its usage.
+Mesh network infrastructure model is intended to help in developing of a routing/controlling algorithm for client mesh network that would provide adaptive bandwidth sharing between management and user traffic with considering of network topology and the way of its usage.
 ** Open source realization **