13.07.2015 Views

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

92 P.M. Ruiz et al.MIGAccess NetworkMMARP_3MMARP_2MMARP_1WWRWRSenderFig. 3. Topology of the testbedthe network depicted <strong>in</strong> Fig. 3, <strong>in</strong> which every MMARP node is switched off, sothat there is a dedicated IEEE 802.11b wireless l<strong>in</strong>k between the receiver and theWWR. The wired part of the network is runn<strong>in</strong>g the PIM-SM rout<strong>in</strong>g protocolto create the multicast path between the source and the WWR, which acts as anIGMP designated router forward<strong>in</strong>g multicast datagrams to the receiver whenit jo<strong>in</strong>s the source.The multihop tests are exactly the same regard<strong>in</strong>g the wired part of thenetwork. However, we deploy a self-organis<strong>in</strong>g ad hoc network extension withnodes runn<strong>in</strong>g MMARP rather than a s<strong>in</strong>gle-hop l<strong>in</strong>k between the receiver andthe WWR. The receiver jo<strong>in</strong>s the multicast source <strong>in</strong> the fixed network throughthis multihop access network.We use CBR traffic generator to measure the end-to-end bandwidth andpacket delivery ratio. This application generates UDP packets with a payload of900 <strong>by</strong>tes (i.e. 942 <strong>by</strong>tes <strong>in</strong>clud<strong>in</strong>g the IPv4 and UDP headers) which are thenaccounted at the dest<strong>in</strong>ation. For each of the tests we have performed severalmeasurements at <strong>in</strong>creas<strong>in</strong>g distances (7m, 15m, 24m, 30m, 42m) between thereceiver and the WWR. At each distance, we have repeated the measurementsus<strong>in</strong>g three different data rates of 100 packets/s (753.6 Kb/s), 50 packets/s (376.8Kb/s) and 25 packets/s (188.4 Kb/s) respectively. The results of the differenttrials are described <strong>in</strong> the next section.As expected, <strong>in</strong> our <strong>in</strong>door scenario the performance depends not only on thedistance but on the node’s position as well. This is ma<strong>in</strong>ly due to random noisecaused <strong>by</strong> travers<strong>in</strong>g walls, obstacles, etc. The results are calculated as the meanvalues over quite a huge number of measurements per experiment. In addition,the measurements are performed <strong>in</strong> the same positions for each distance. So,random noise is expected to be nearly the same <strong>in</strong> all the trials, not affect<strong>in</strong>gthe validity of our experiments.4.3 Experimental ResultsTo be sure about the cause of the packet losses <strong>in</strong> our analysis, we empiricallychecked that there were not packet losses with<strong>in</strong> the wired part of the network.So, all the packet losses perceived at the receiver will occur <strong>in</strong> the wireless partof the network.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!