Changes between Version 5 and Version 6 of 802.11/wlan_exp/app_notes/ibss_multiple_flows


Ignore:
Timestamp:
Oct 1, 2014, 2:27:18 PM (10 years ago)
Author:
chunter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • 802.11/wlan_exp/app_notes/ibss_multiple_flows

    v5 v6  
    33This application is an extension to the [wiki:802.11/wlan_exp/app_notes/dcf_with_multiple_flows Investigating Physical Carrier Sensing in the DCF with Multiple Traffic Flows] application note. Instead of a network of 1 AP and 2 STA nodes, this example shows how to run an experiment with 3 IBSS nodes.
    44
    5 The standard AP/STA flavors of 802.11 have a fundamental limitation: The AP is capable of transmitting to any of its association stations, but the STA devices can ''only'' directly transmit to the AP. STA devices cannot directly communicate with other STA devices on the BSS without first hopping through the AP.
     5The standard AP/STA flavors of 802.11 have a fundamental topological limitation: The AP is capable of transmitting to any of its association stations, but the STA devices can ''only'' directly transmit to the AP. STA devices cannot directly communicate with other STA devices on the BSS without first hopping through the AP.
    66
    7 IBSS devices are different. The "Independent Basic Service Set" allows for any device to communicate to any other device, allowing for more general mesh configurations. Unlike the [wiki:802.11/wlan_exp/app_notes/dcf_with_multiple_flows Investigating Physical Carrier Sensing in the DCF with Multiple Traffic Flows] application note, we are not limited to a total of 4 possible flows. In this application note, we extend the network to a total of 6 flows while still only using 3 IBSS nodes.
     7IBSS devices are different. The "Independent Basic Service Set" allows for any device to communicate to any other device, allowing for more general mesh configurations. Unlike the [wiki:802.11/wlan_exp/app_notes/dcf_with_multiple_flows Investigating Physical Carrier Sensing in the DCF with Multiple Traffic Flows] application note, we are not limited to a total of 4 possible flows. In this application note, we extend the network to a total of 6 flows while only using 3 IBSS nodes.
    88
    99== Experiment Details ==
    … …  
    3333
    3434The above figures show 300 seconds of data from the experiment. In the first figure, the black line shows the total sum throughput that was sustained in the network. The ~12.5Mbps that was achieved is just slightly below the [wiki:802.11/Benchmarks/Throughput#Throughputvs.PayloadLength theoretical max] throughput that can be achieved at the 14Mbps PHY rate. The slight reduction is due to the overhead of the DCF along with unavoidable collisions among the 6 traffic flows.
     35
     36The IBSS project is very useful in research applications in that there is no topological requirement for flow connectivity. Any device can establish a wireless link to any other device on the same IBSS. All source code used to generate the data and figures in this application note is available below.
     37
     38----
     39
     40= Resources =
     41
     42== Python Scripts ==
     43
     44Download: [raw-attachment:multi-flow_ibss_python_scripts_v_0_96.zip multi-flow_ibss_python_scripts_v_0_96.zip]
     45 * Requirements:
     46  * 3 WARP v3 Kits, each configured as an IBSS CPU_HIGH and DCF CPU_LOW
     47  * [wiki:802.11/Changelog#a0.96BetaRelease Mango 802.11 Reference Design v0.96]
     48
     49Zip Contents:
     50 * '''multi-flow_experiment_ibss.py''' - This script will run the experiment and write the log files from each board to the directory in which this script is executed.
     51 * '''multi-flow_plotter_ibss.py''' - This script will open the generated log files and produce the plots used in the application note.
     52 * '''log_analysis_util.py''' - Utility script that is used by multi-flow_plotter.py. This should not be run directly. Instead, it should be in the same directory as multi-flow_plotter.py