Architecture of Mobile Ad-hoc network

Client/Network Relationships:

·        Mobile units can move freely in a geographic mobility domain, an area that is circumscribed by wireless network coverage.

·        To manage the mobility of units, the entire geographic mobility domain is divided into one or more smaller domains called cells, each of which is supported by at least one base station.

·        The mobile discipline requires that the movement of mobile units be unrestricted throughout the cells of a geographic mobility domain, while maintaining information access contiguity—i.e., movement, especially intercell movement, does not negatively affect the data retrieval process.

Explanation:

• In a MANET, co-located mobile units do not need to communicate via a fixed network, but instead, form their own using cost-effective technologies such as Bluetooth.
• In a MANET, mobile units are responsible for routing their own data, effectively acting as base stations as well as clients.
• Moreover, they must be robust enough to handle changes in the network topology, such as the arrival or departure of other mobile units.
• MANET applications can fall under the peer-to-peer paradigm, meaning that a mobile unit is simultaneously a client and a server.
• Transaction processing and data consistency control become more difficult since there is no central control in this architecture.
• Resource discovery and data routing by mobile units make computing in a MANET more complicated.