Wireless MEMS Sensor Networks


[attachment=17014]
Mesh Networks

Edge Binding- J.W. Smith, Rand Corp.
In any network, much of the routing power of peripheral stations is wasted simply because peripheral links are unused. Thus, messages tend to reflect off the boundary into the interior or to move parallel to the periphery.


The Problem of Complexity


Communication Protocols in a network must be restricted and organized to avoid Complexity problems


e.g. in Manufacturing
The general job shop allows part flows between all machines
The Flow Line allows part flows only along specific Paths


We have shown that the job shop is NP-complete

but the reentrant flow line is of polynomial complexity


Ethernet
Ethernet was developed in the mid 1970's by the Xerox Corporation, and in 1979 Digital Equipment Corporation DEC) and Intel joined forces with Xerox to standardise the system. The Institute of Electrical and Electronic Engineers (IEEE) released the official Ethernet standard in 1983 called the IEEE 802.3 after the name of the working group responsible for its development, and in 1985 version 2 (IEEE 802.3a) was released. This second version is commonly known as "Thin Ethernet" or 10Base2, in this case the maximum length is 185m even though the "2" suggest that it should be 200m.


Fast Ethernet

Fast Ethernet was officially adopted in the summer of 1995, two years after a group of leading network companies had formed the Fast Ethernet Alliance to develop the standard. Operating at ten times the speed of regular 10Base-T Ethernet, Fast Ethernet - also known as 100BaseT - retains the same CSMA/CD protocol and Category 5 cabling support as its predecessor higher bandwidth and introduces new features such as full-duplex operation and auto-negotiation.


Client-Server

Client-server networking architectures became popular in the late 1980s and early 1990s as many applications were migrated from centralised minicomputers and mainframes to networks of personal computers. The design of applications for a distributed computing environment required that they effectively be divided into two parts: client (front end) and server (back end). The network architecture on which they were implemented mirrored this client-server model, with a user's PC (the client) typically acting as the requesting machine and a more powerful server machine - to which it was connected via either a LAN or a WAN - acting as the supplying machine.