NS2example.rar_无线传感器网络_wsn ns2_网络

<html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta charset="utf-8"> <meta name="generator" content="pdf2htmlEX"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <link rel="stylesheet" href="https://static.pudn.com/base/css/base.min.css"> <link rel="stylesheet" href="https://static.pudn.com/base/css/fancy.min.css"> <link rel="stylesheet" href="https://static.pudn.com/prod/directory_preview_static/622b367281ded46b7f569419/raw.css"> <script src="https://static.pudn.com/base/js/compatibility.min.js"></script> <script src="https://static.pudn.com/base/js/pdf2htmlEX.min.js"></script> <script> try{ pdf2htmlEX.defaultViewer = new pdf2htmlEX.Viewer({}); }catch(e){} </script> <title></title> </head> <body> <div id="sidebar" style="display: none"> <div id="outline"> </div> </div> <div id="pf1" class="pf w0 h0" data-page-no="1"><div class="pc pc1 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b367281ded46b7f569419/bg1.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">Implementing a New Manet Unicast Routing</div><div class="t m0 x2 h2 y2 ff1 fs0 fc0 sc0 ls0 ws0">Protocol in NS2</div><div class="t m0 x3 h3 y3 ff2 fs1 fc0 sc0 ls0 ws0">Francisco J. Ros</div><div class="t m0 x4 h3 y4 ff2 fs1 fc0 sc0 ls0 ws0">Pedro M. Ruiz</div><div class="t m0 x5 h4 y5 ff3 fs1 fc0 sc0 ls0 ws0">{fjrm, pedrom}@dif.um.es</div><div class="t m0 x6 h5 y6 ff5 fs1 fc0 sc0 ls0 ws0">Dept. of Information and Communications Engineering</div><div class="t m0 x7 h5 y7 ff5 fs1 fc0 sc0 ls0 ws0">University of Murcia</div><div class="t m0 x8 h5 y8 ff4 fs1 fc0 sc0 ls0 ws0">December, 2004</div><div class="t m0 x9 h6 y9 ff6 fs2 fc0 sc0 ls0 ws0">1</div></div><div class="pi" data-data='{"ctm":[1.611639,0.000000,0.000000,1.611639,0.000000,0.000000]}'></div></div> </body> </html>

<div id="pf2" class="pf w0 h0" data-page-no="2"><div class="pc pc2 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b367281ded46b7f569419/bg2.jpg"><div class="t m0 xa h6 ya ff6 fs2 fc0 sc0 ls0 ws0">Copyright (c) 2004 Francisco J. Ros and Pedro M. Ruiz.</div><div class="t m0 xa h6 yb ff6 fs2 fc0 sc0 ls0 ws0">Permission is granted to copy, distribute and/or modify this docu-</div><div class="t m0 xa h6 yc ff6 fs2 fc0 sc0 ls0 ws0">ment under the terms of the GNU Free Documentation License, Ver-</div><div class="t m0 xa h6 yd ff6 fs2 fc0 sc0 ls0 ws0">sion 1.2 or any later version published by the Free Software Foun-</div><div class="t m0 xa h6 ye ff6 fs2 fc0 sc0 ls0 ws0">dation; with no Invariant Sections, no Front-Cover Texts, and no</div><div class="t m0 xa h6 y2 ff6 fs2 fc0 sc0 ls0 ws0">Back-Cover Texts. A copy of the license is included in the section</div><div class="t m0 xa h6 yf ff6 fs2 fc0 sc0 ls0 ws0">entitled ”GNU Free Documentation License”.</div><div class="t m0 x9 h6 y9 ff6 fs2 fc0 sc0 ls0 ws0">2</div></div><div class="pi" data-data='{"ctm":[1.611639,0.000000,0.000000,1.611639,0.000000,0.000000]}'></div></div>

<div id="pf3" class="pf w0 h0" data-page-no="3"><div class="pc pc3 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b367281ded46b7f569419/bg3.jpg"><div class="t m0 xb h7 ya ff2 fs3 fc0 sc0 ls0 ws0">Contents</div><div class="t m0 xb h6 y10 ff7 fs2 fc0 sc0 ls0 ws0">1 Introduction 4</div><div class="t m0 xb h6 y11 ff7 fs2 fc0 sc0 ls0 ws0">2 Getting Started 4</div><div class="t m0 xb h6 y12 ff7 fs2 fc0 sc0 ls0 ws0">3 Packet Typ es 5</div><div class="t m0 xb h6 y13 ff7 fs2 fc0 sc0 ls0 ws0">4 The Routing Agent 7</div><div class="t m0 xc h6 y14 ff6 fs2 fc0 sc0 ls0 ws0">4.1 Tcl hooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10</div><div class="t m0 xc h6 y15 ff6 fs2 fc0 sc0 ls0 ws0">4.2 Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11</div><div class="t m0 xc h6 y16 ff6 fs2 fc0 sc0 ls0 ws0">4.3 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11</div><div class="t m0 xd h6 y17 ff6 fs2 fc0 sc0 ls0 ws0">4.3.1 Constructor . . . . . . . . . . . . . . . . . . . . . . . . . . 11</div><div class="t m0 xd h6 y18 ff6 fs2 fc0 sc0 ls0 ws0">4.3.2 command() . . . . . . . . . . . . . . . . . . . . . . . . . . 11</div><div class="t m0 xd h6 y19 ff6 fs2 fc0 sc0 ls0 ws0">4.3.3 recv() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13</div><div class="t m0 xd h6 y1a ff6 fs2 fc0 sc0 ls0 ws0">4.3.4 recv protoname pkt() . . . . . . . . . . . . . . . . . . . . 15</div><div class="t m0 xd h6 y1b ff6 fs2 fc0 sc0 ls0 ws0">4.3.5 send protoname pkt() . . . . . . . . . . . . . . . . . . . . 15</div><div class="t m0 xd h6 y1c ff6 fs2 fc0 sc0 ls0 ws0">4.3.6 reset protoname pkt timer() . . . . . . . . . . . . . . . . . 17</div><div class="t m0 xd h6 y1d ff6 fs2 fc0 sc0 ls0 ws0">4.3.7 forward data() . . . . . . . . . . . . . . . . . . . . . . . . 17</div><div class="t m0 xb h6 y1e ff7 fs2 fc0 sc0 ls0 ws0">5 The Routing Table 18</div><div class="t m0 xb h6 y1f ff7 fs2 fc0 sc0 ls0 ws0">6 Needed Changes 20</div><div class="t m0 xc h6 y20 ff6 fs2 fc0 sc0 ls0 ws0">6.1 Packet type declaration . . . . . . . . . . . . . . . . . . . . . . . 20</div><div class="t m0 xc h6 y21 ff6 fs2 fc0 sc0 ls0 ws0">6.2 Tracing support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21</div><div class="t m0 xc h6 y22 ff6 fs2 fc0 sc0 ls0 ws0">6.3 Tcl library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23</div><div class="t m0 xc h6 y23 ff6 fs2 fc0 sc0 ls0 ws0">6.4 Priority queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24</div><div class="t m0 xc h6 y24 ff6 fs2 fc0 sc0 ls0 ws0">6.5 Makeﬁle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25</div><div class="t m0 xb h6 y25 ff7 fs2 fc0 sc0 ls0 ws0">7 Receiving Information from Layer-2 Protocols 25</div><div class="t m0 xb h6 y26 ff7 fs2 fc0 sc0 ls0 ws0">8 Support for Wired-Cum-Wireless Simulations 27</div><div class="t m0 xb h6 y27 ff7 fs2 fc0 sc0 ls0 ws0">A GNU Free Documentation License 29</div><div class="t m0 xb h6 y28 ff7 fs2 fc0 sc0 ls0 ws0">1. APPLICABILITY AND DEFINITIONS 29</div><div class="t m0 xb h6 y29 ff7 fs2 fc0 sc0 ls0 ws0">2. VERBATIM COPYING 30</div><div class="t m0 xb h6 y2a ff7 fs2 fc0 sc0 ls0 ws0">3. COPYING IN QUANTITY 31</div><div class="t m0 xb h6 y2b ff7 fs2 fc0 sc0 ls0 ws0">4. MODIFICATIONS 31</div><div class="t m0 xb h6 y2c ff7 fs2 fc0 sc0 ls0 ws0">5. COMBINING DOCUMENTS 33</div><div class="t m0 xb h6 y2d ff7 fs2 fc0 sc0 ls0 ws0">6. COLLECTIONS OF DOCUMENTS 33</div><div class="t m0 xb h6 y2e ff7 fs2 fc0 sc0 ls0 ws0">7. AGGREGATION WITH INDEPENDENT WORKS 34</div><div class="t m0 xb h6 y2f ff7 fs2 fc0 sc0 ls0 ws0">8. TRANSLATION 34</div><div class="t m0 xb h6 y30 ff7 fs2 fc0 sc0 ls0 ws0">9. TERMINATION 34</div><div class="t m0 x9 h6 y9 ff6 fs2 fc0 sc0 ls0 ws0">3</div></div><div class="pi" data-data='{"ctm":[1.611639,0.000000,0.000000,1.611639,0.000000,0.000000]}'></div></div>

<div id="pf4" class="pf w0 h0" data-page-no="4"><div class="pc pc4 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b367281ded46b7f569419/bg4.jpg"><div class="t m0 xb h6 ya ff7 fs2 fc0 sc0 ls0 ws0">10. FUTURE REVISIONS OF THIS LICENSE 34</div><div class="t m0 xb h7 y31 ff2 fs3 fc0 sc0 ls0 ws0">1 Introduction</div><div class="t m0 xb h6 y32 ff6 fs2 fc0 sc0 ls0 ws0">During the last year, we have witnessed a lot of people asking for the same</div><div class="t m0 xb h6 y33 ff6 fs2 fc0 sc0 ls0 ws0">question in the ns-users mailing list. How do I develop my own protocol for</div><div class="t m0 xb h6 y34 ff6 fs2 fc0 sc0 ls0 ws0">NS2? By writing this document we hope to help those researchers who need to</div><div class="t m0 xb h6 y35 ff6 fs2 fc0 sc0 ls0 ws0">add a manet routing protocol for NS-2.27. We focus our document in unicast</div><div class="t m0 xb h6 y36 ff6 fs2 fc0 sc0 ls0 ws0">protocols. The document is aimed to those people who are somehow familiar</div><div class="t m0 xb h6 y37 ff6 fs2 fc0 sc0 ls0 ws0">with performing simulations in ns-2, and they want to go one step forward to</div><div class="t m0 xb h6 y38 ff6 fs2 fc0 sc0 ls0 ws0">implement their own protocols. Everything we describe in this text is related</div><div class="t m0 xb h6 y39 ff6 fs2 fc0 sc0 ls0 ws0">to version 2.27 of NS2, but it might be useful for other versions as well.</div><div class="t m0 xc h6 y3a ff6 fs2 fc0 sc0 ls0 ws0">We assume that the reader is familiar with the NS2 basics. That means hav-</div><div class="t m0 xb h6 y3b ff6 fs2 fc0 sc0 ls0 ws0">ing read and at least mostly understood “Marc Greis’ Tutorial” [1]. It would be</div><div class="t m0 xb h6 y3c ff6 fs2 fc0 sc0 ls0 ws0">very useful if you also take a look at “The ns Manual” [2], specially chapters 3-5,</div><div class="t m0 xb h6 y3d ff6 fs2 fc0 sc0 ls0 ws0">10-12, 15-16, 23, 25 and 29. We will refer to them several times throughout this</div><div class="t m0 xb h6 y3e ff6 fs2 fc0 sc0 ls0 ws0">text and encourage you to read them. Before coding your own routing protocol,</div><div class="t m0 xb h6 y3f ff6 fs2 fc0 sc0 ls0 ws0">you should know how to perform simulations with other implemented protocols</div><div class="t m0 xb h6 y40 ff6 fs2 fc0 sc0 ls0 ws0">and you are expected to feel familiar and comfortable with simulator. This will</div><div class="t m0 xb h6 y41 ff6 fs2 fc0 sc0 ls0 ws0">avoid lots of misunderstandings and doubts while reading this do cument.</div><div class="t m0 xc h6 y42 ff6 fs2 fc0 sc0 ls0 ws0">Besides this tutorial is about programming. You need knowledge about C++</div><div class="t m0 xb h6 y43 ff6 fs2 fc0 sc0 ls0 ws0">and (a little) Tcl programming. If you aren’t enough experienced with these</div><div class="t m0 xb h6 y44 ff6 fs2 fc0 sc0 ls0 ws0">programming lenguages, you should ﬁrstly read any of the excellent resources</div><div class="t m0 xb h6 y45 ff6 fs2 fc0 sc0 ls0 ws0">about them which are freely available in the Internet.</div><div class="t m0 xb h7 y46 ff2 fs3 fc0 sc0 ls0 ws0">2 Getting Started</div><div class="t m0 xb h6 y47 ff6 fs2 fc0 sc0 ls0 ws0">We are going to implement a new manet routing protocol called protoname</div><div class="t m0 xb h6 y48 ff6 fs2 fc0 sc0 ls0 ws0">step by step. This protocol does nothing useful, but it is general enough to</div><div class="t m0 xb h6 y49 ff6 fs2 fc0 sc0 ls0 ws0">have several common points with other routing protocols. As you likely know</div><div class="t m0 xb h6 y4a ff6 fs2 fc0 sc0 ls0 ws0">(if not, please read ﬁrstly what we told you!) we are going to implement routing</div><div class="t m0 xb h6 y4b ff6 fs2 fc0 sc0 ls0 ws0">protocol using C++ and then we will do simulations describing scenarios with</div><div class="t m0 xb h6 y4c ff6 fs2 fc0 sc0 ls0 ws0">Tcl scripts.</div><div class="t m0 xc h6 y4d ff6 fs2 fc0 sc0 ls0 ws0">To allocate our code we will ﬁrstly create a new directory called protoname</div><div class="t m0 xb h6 y4e ff6 fs2 fc0 sc0 ls0 ws0">inside your NS2 base directory. We will create ﬁve ﬁles there:</div><div class="t m0 xb h6 y4f ff7 fs2 fc0 sc0 ls0 ws0">protoname.h This is the header ﬁle where will be deﬁned all necessary timers</div><div class="t m0 xa h6 y50 ff6 fs2 fc0 sc0 ls0 ws0">(if any) and routing agent which performs protocol’s functionality.</div><div class="t m0 xb h6 y51 ff7 fs2 fc0 sc0 ls0 ws0">protoname.cc In this ﬁle are actually implemented all timers, routing agent</div><div class="t m0 xa h6 y52 ff6 fs2 fc0 sc0 ls0 ws0">and Tcl hooks.</div><div class="t m0 xb h6 y53 ff7 fs2 fc0 sc0 ls0 ws0">protoname pkt.h Here are declared all packets protoname protocol needs to</div><div class="t m0 xa h6 y54 ff6 fs2 fc0 sc0 ls0 ws0">exchange among nodes in the manet.</div><div class="t m0 xb h6 y55 ff7 fs2 fc0 sc0 ls0 ws0">protoname rtable.h Header ﬁle where our own routing table is declared.</div><div class="t m0 xb h6 y56 ff7 fs2 fc0 sc0 ls0 ws0">protoname rtable.cc Routing table implementation.</div><div class="t m0 x9 h6 y9 ff6 fs2 fc0 sc0 ls0 ws0">4</div></div><div class="pi" data-data='{"ctm":[1.611639,0.000000,0.000000,1.611639,0.000000,0.000000]}'></div></div>

<div id="pf5" class="pf w0 h0" data-page-no="5"><div class="pc pc5 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b367281ded46b7f569419/bg5.jpg"><div class="t m0 xc h6 ya ff6 fs2 fc0 sc0 ls0 ws0">You can organize your code as you want to. That is, you can create more or</div><div class="t m0 xb h6 y57 ff6 fs2 fc0 sc0 ls0 ws0">less ﬁles, with those names or with others; this is only a hint. Our advice is to</div><div class="t m0 xb h6 y58 ff6 fs2 fc0 sc0 ls0 ws0">use at least those ﬁles and to create more as they are needed.</div><div class="t m0 xc h6 y59 ff6 fs2 fc0 sc0 ls0 ws0">Now we have our “physical” structure (ﬁles), let’s continue with the “logical”</div><div class="t m0 xb h6 y5a ff6 fs2 fc0 sc0 ls0 ws0">one (classes). To implement a routing protocol in NS2 you must create an agent</div><div class="t m0 xb h6 y5b ff6 fs2 fc0 sc0 ls0 ws0">by inheriting from Agent class. At the very beginning of chapter 10 [2] we can</div><div class="t m0 xb h6 y5c ff6 fs2 fc0 sc0 ls0 ws0">read “Agents represent endpoints where network-layer packets are constructed or</div><div class="t m0 xb h6 y5d ff8 fs2 fc0 sc0 ls0 ws0">consumed, and are used in the implementation of protocols at various layers”.</div><div class="t m0 xb h6 y5e ff6 fs2 fc0 sc0 ls0 ws0">As you can ﬁgure out, this is the main class we will have to code in order to</div><div class="t m0 xb h6 y5f ff6 fs2 fc0 sc0 ls0 ws0">implement our routing protocol. In addition, this class oﬀers a linkage with Tcl</div><div class="t m0 xb h6 y60 ff6 fs2 fc0 sc0 ls0 ws0">interface, so we will be able to control our routing protocol through simulation</div><div class="t m0 xb h6 y61 ff6 fs2 fc0 sc0 ls0 ws0">scripts written in Tcl.</div><div class="t m0 xc h6 y62 ff6 fs2 fc0 sc0 ls0 ws0">Our routing agent will maintain an internal state and a routing table (which</div><div class="t m0 xb h6 y63 ff6 fs2 fc0 sc0 ls0 ws0">is not always needed). Internal state can be represented as a new class or as a</div><div class="t m0 xb h6 y64 ff6 fs2 fc0 sc0 ls0 ws0">collection of attributes inside the routing agent. We will treat routing table as</div><div class="t m0 xb h6 y65 ff6 fs2 fc0 sc0 ls0 ws0">a new class, protoname rtable.</div><div class="t m0 xc h6 y66 ff6 fs2 fc0 sc0 ls0 ws0">Also our new protocol must deﬁne at least one new packet type which will</div><div class="t m0 xb h6 y67 ff6 fs2 fc0 sc0 ls0 ws0">represent the format of its control packets. As we said these packet types are</div><div class="t m0 xb h6 y68 ff6 fs2 fc0 sc0 ls0 ws0">deﬁned in protoname/protoname pkt.h. When the protocol needs to send pack-</div><div class="t m0 xb h6 y69 ff6 fs2 fc0 sc0 ls0 ws0">ets periodically or after some time from the occurrence of an event, it is very</div><div class="t m0 xb h6 y6a ff6 fs2 fc0 sc0 ls0 ws0">useful to count on a Timer class. We show an example in which we code our</div><div class="t m0 xb h6 y1f ff6 fs2 fc0 sc0 ls0 ws0">own timers for sending these packets at regular intervals. Timers are also useful</div><div class="t m0 xb h6 y20 ff6 fs2 fc0 sc0 ls0 ws0">in lots of other cases. Imagine protoname needs to store some sort of internal</div><div class="t m0 xb h6 y21 ff6 fs2 fc0 sc0 ls0 ws0">information which must be erased at a certain time. The best solution is to</div><div class="t m0 xb h6 y22 ff6 fs2 fc0 sc0 ls0 ws0">create a custom timer capable of doing such job. A timer should also be used to</div><div class="t m0 xb h6 y23 ff6 fs2 fc0 sc0 ls0 ws0">specify timelife of an entry in the routing table. In general, we will use a timer</div><div class="t m0 xb h6 y24 ff6 fs2 fc0 sc0 ls0 ws0">whenever we have to schedule a task at a given time.</div><div class="t m0 xc h6 y6b ff6 fs2 fc0 sc0 ls0 ws0">There is another important class we must know before going into details.</div><div class="t m0 xb h6 y6c ff6 fs2 fc0 sc0 ls0 ws0">The Trace class is the base for writing log ﬁles with information about what</div><div class="t m0 xb h6 y6d ff6 fs2 fc0 sc0 ls0 ws0">happened during the simulation.</div><div class="t m0 xc h6 y6e ff6 fs2 fc0 sc0 ls0 ws0">And the last hint for now: when you want to print a debug message in your</div><div class="t m0 xb h6 y6f ff6 fs2 fc0 sc0 ls0 ws0">code, it is helpful to use the debug() function as it is suggested in chapter 25 [2].</div><div class="t m0 xb h6 y70 ff6 fs2 fc0 sc0 ls0 ws0">This allows you to turn debugging on or oﬀ from your simulation scripts and is</div><div class="t m0 xb h6 y71 ff6 fs2 fc0 sc0 ls0 ws0">easier to read for other programmers.</div><div class="t m0 xb h7 y72 ff2 fs3 fc0 sc0 ls0 ws0">3 Packet Types</div><div class="t m0 xb h6 y73 ff6 fs2 fc0 sc0 ls0 ws0">Now that you already know the basics, let’s create a new ﬁle and call it proton-</div><div class="t m0 xb h6 y74 ff8 fs2 fc0 sc0 ls0 ws0">ame/protoname pkt.h. Here we are going to put all data structures, constants</div><div class="t m0 xb h6 y75 ff6 fs2 fc0 sc0 ls0 ws0">and macros related to our new packet(s) type. See next example.</div><div class="t m0 xb h8 y76 ff9 fs2 fc0 sc0 ls0 ws0">protoname/protoname_pkt.h</div><div class="t m0 xb h8 y77 ff9 fs2 fc0 sc0 ls0 ws0">1: #ifndef __protoname_pkt_h__</div><div class="t m0 xb h8 y78 ff9 fs2 fc0 sc0 ls0 ws0">2: #define __protoname_pkt_h__</div><div class="t m0 xb h8 y79 ff9 fs2 fc0 sc0 ls0 ws0">3:</div><div class="t m0 xb h8 y7a ff9 fs2 fc0 sc0 ls0 ws0">4: #include <packet.h></div><div class="t m0 xb h8 y7b ff9 fs2 fc0 sc0 ls0 ws0">5:</div><div class="t m0 xb h8 y7c ff9 fs2 fc0 sc0 ls0 ws0">6: #define HDR_PROTONAME_PKT(p) hdr_protoname_pkt::access(p)</div><div class="t m0 x9 h6 y9 ff6 fs2 fc0 sc0 ls0 ws0">5</div></div><div class="pi" data-data='{"ctm":[1.611639,0.000000,0.000000,1.611639,0.000000,0.000000]}'></div></div>