Embedded Linux Design And Implementation Of The Ad-hoc Routing Protocols

The Ad-Hoc network is used more and more extensive in temporary communication circumstances such as emergency communication, during to its own property. The research of routing protocol of ad-hoc networks has always been the hotspot in the field of ad-hoc research. The embedded system has been passed through four stages of development; it has permeated impregnate into every area of our life. Because of open-source and configurable, Linux has gradually become the mainstream in embedded OS. Combining the ad-hoc networks and embedded system, it will bring new applied value to design a routing protocol that can run in the embedded system, discovery route faster, perceive the network topology dynamically.This paper is unfolded rounding the research of ad-hoc routing protocol based on embedded system. Combining the Ad-Hoc network and the features of the embedded system a routing protocol named smallest load first is put forward. The research background and status is provided in paper. The conception and feature of ad-hoc network are given. The design issues are raised and the Embedded Linux OS is summarized. The paper elaborates the working principle including route discovery and route maintenance in detail and gives the message-format of the protocol. The finite state machine is given in order to verify the protocol. The Embedded development platform is constructed for realize the protocol. The related principle is introduced. Referring to the OSI model, this route protocol is designed in modularization and stratification. Each processing flow chart and parts of kernel code. The protocol is tested in appropriate circumstance. The tested items include route discovery, route maintenance, data forward and protocol expense. The result indicates that this protocol discover routes exactly and quickly, selects the route of min load as the optimal route, perceive the network topology dynamically, update the route information timely and forward data well. Moreover, this route protocol cost small bandwidth and take a little of CPU and memory resource.