CRAWDAD intel/home

Measurements reflect connectivity and UDP/TCP throughput data collected from a grid of six nodes placed within three different houses.date/time of measurement start: 2005-06-29date/time of measurement end: 2005-07-03collection environment: Measurements reflect connectivity and UDP/TCP throughput  data collected from a grid of six nodes placed within three different houses, 2 in the United States (denoted ushome1 and ushome2) and 1 in the United Kingdom (denoted ukhome1).  Results have been collected for different values for transmission power and transmission rate, as well as 802.11a and 802.11b wireless devices.A brief description of the three houses along with approximate floorplans (which can be downloaded from the trace intel/home/reachability/floorplan) are shown below. Label    Size (ft^2)    Construction    Floors    Nodes-------------------------------------------------------ushome1    2,500        Wood            2        6ushome2    2,600        Wood            3        6ukhome1    1,500        Brick/steel     3        6network configuration: For 802.11b experiments the nodes are small form-factor PCs with Netgear MA701 compact flash 802.11b wireless cards. The nodes run Linux kernel version 2.4.19 and the hostap driver. For 802.11a experiments the nodes are laptops with NetGear WAG511 CardBus 802.11a/b/g cards running Linux kernel version 2.4.26 and the MIT madwifi-stripped driver. All radios have omnidirectional antennas, and could be considered comparable to the radios that are likely to be integrated in future consumer electronics, e.g. cheap radios with basic functionality. Lastly, all three testbeds are homogeneous; each node consists of the exact same hardware to limit the impact of hardware peculiarities on the obtained results.Our network setup is common among all experiments. All nodes utilize an unused frequency that is at least five channels away from the next occupied 802.11 frequency. To facilitate our experiments, we utilize the 802.11 Independent Basic Service Set (IBSS) mode, which allows all nodes to communicate directly. However, this configuration does not constrain the usefulness of our results to ad hoc (mesh) topologies.data collection methodology: Each node is instructed to run an experiment toward every other node in turn. Our experiments are designed to assess: (i) success/loss rate, and (ii) throughput under different combinations of txrate and txpower. We further alter the node location for specific experiments in order to quantify the impact of exact node location, antenna orientation, and obstacles. Experiments are carried out during the night to avoid interference from moving people and facilitate reproducibility. Except where explicitly stated, each result represents a single experimental run, due to the highly time consuming nature of our experiments. Instead, we rely on the validating runs presented in the following subsections to lend credence to our results.Tracesetintel/home/reachabilityReachability and throughput measurement from home wireless networks. measurement purpose: Network Performance Analysismethodology: Reachability: The reachability experiments assess link quality between each pair of nodes in the home network in terms of success/loss rate, and rely on a series of UDP probe packets sent from every node to every other node. Each probe packet lists the source node, as well as its number in the series. The size of the probe packet and the duration of each sub-experiment are configurable. In all experiments, link-layer retransmissions were disabled, the probe size was 1472 bytes, and the duration of each sub-experiment was 60 seconds, with a frequency of one packet every 500 ms. Each individual wireless link is assessed independently, and no simultaneous transmissions take place inside the network.Throughput: The throughput experiments were run to assess the quality of layer-3 communication within the home network. Throughput was assessed for both TCP and UDP protocols. For our throughput experiments we use the same basic methodology which relies on measurements from all pairings of the six nodes in the testbed. Throughput is measured by the netperf traffic generator using 1472 byte packets. Each node initiates a netperf connection to every other node (in turn) and measures the throughput achieved over a 60 second time interval. Unlike the reachability experiments, the throughput experiments are conducted with link layer retransmission enabled (maximum of 3 retries), which is likely to alleviate the effect of short term degradation in link quality.Autorate: UDP/TCP throughput measurements are collected for 60 second flows when transmitters employ autorate.  intel/home/reachability Tracesfloorplan: Approximate floorplan for the three houses.file: floorplan.tar.gzconfiguration: Floorplan for three different houses, 2 in the United States (denoted ushome1 and ushome2) and 1 in the United Kingdom (denoted ukhome1). The lines in the floorplan images reflect the (unidirectional) links  that exhibited more than 90% loss in the reachability experiments.format: three png image filesdistance: Distance between each pair of nodes.file: distance.tar.gzconfiguration: Distance between each pair of nodes in the three houses (ushome1, ushome2, and ukhome) in the original deployment in feetformat: distance in each rowresults: Distance between each pair of nodes.file: reachability.tar.gzconfiguration: Reachability and Throughput Results.format: File names are as follows:{House}-{Exp}-{Network}-{Traffic}-{Txrate}-{Txpower}.{Mode}.txt- House: ushome1, ushome2, or ukhome- Exp: original (original topology), validation (validation run), rotated (with nodes rotaetd by 180 degrees), or autorate (with autorate on)- Network: b (802.11 b) or a (802.11 a)- Traffic: udp or tcp- Txrate: TX rate (e.g., 2Mbps)- Txpower: TX power (e.g., 30mW)- Mode: comb (for reachability/throughput experiments),or top (for multihop throughput experiments)All files are of the following format. Each row corresponds to the measurements collected from node2->node3, node2->node4, node2->node5, node2->node6, node2->node7, node3->node2, node3->node4, etc. (node1 was used to control the experiments). The first column of measurements corresponds to the number of UDP probes that were successfully received (total number of probes is 120). The second column captures the throughput measured from the source node to the destination node in Mbps. intel/home/multihopMultihop throughput measurement from home wireless networks.measurement purpose: Network Performance Analysismethodology: Multihop: For one specific node in the testbed we setup multihop paths through every other node in the testbed and measure the resulting UDP throughput using netperf. We establish that the resulting multi-hop UDP throughput can be well approximated by thr(src, dst) = 1/(1/thr(src,relay)+1/thr(relay,dst)), where src denotes the transmitting node, dst denotes the receiving node, and relay denotes the node that relays traffic between the two. Using this formula we compare the performance of the network under three different topologies  (i) Direct where each node communicates with every other node using the direct path, (ii) AP-topology, where one specific node is selected to act as a relay between any two other nodes in the testbed, and (iii) Multihop-topology, where nodes communicate with each other either using the optimal path through the topology, where optimality captures minimum airtime. In this last case, we assume that paths are selected using Dijkstra's algorithm and link weights relay airtime, i.e. a path is selected such that a packet between the two nodes occupies the least amount of time in the network. All experiments test performance for a single flow between two nodes in the testbed. There are no contending transmission occupying the network.intel/home/multihop Traceresults: Multihop UDP Throughput Results.file: multihop.tar.gzconfiguration: To assess the accuracy of approximating 2-hop throughput using single hop measurements, we used node2 in ukhome1 as a transmitter and measured 2-hop throughput to every other node in the home using every other node as a relay. We then compared our estimate against the measured 2-hop value. Notice that this kind of analysis looks into UDP throughput alone.format: File names are as follows:{House}-{Exp}-{Network}-{Traffic}-{Txrate}-{Txpower}.{Mode}.txt- House: ushome1, ushome2, or ukhome- Exp: original (original topology), validation (validation run), rotated (with nodes rotaetd by 180 degrees), or autorate (with autorate on)- Network: b (802.11 b) or a (802.11 a)- Traffic: udp or tcp- Txrate: TX rate (e.g., 2Mbps)- Txpower: TX power (e.g., 30mW)- Mode: comb (for reachability/throughput experiments),or top (for multihop throughput experiments)All files are of the following format. The first row denotes the pairs of nodes tested and each other row has an experiment descriptor that indicates the type of topology tested.

测量数据反映了从部署在三所不同住宅内的六节点网格收集到的连通性及UDP/TCP吞吐量数据。
测量开始时间：2005-06-29
测量结束时间：2005-07-03
数据收集环境：测量数据反映了从部署在三所不同住宅内的六节点网格收集到的连通性及UDP/TCP吞吐量数据，其中2所位于美国（记为ushome1和ushome2），1所位于英国（记为ukhome1）。结果针对不同传输功率（txpower）、传输速率（txrate）值，以及802.11a和802.11b无线设备收集。
三所住宅的简要描述及近似平面图（可从trace intel/home/reachability/floorplan下载）如下所示：
标签   面积（平方英尺）   建筑结构   楼层数   节点数
-------------------------------------------------------
ushome1   2,500       木结构        2      6
ushome2   2,600       木结构        3      6
ukhome1   1,500       砖/钢结构      3      6
网络配置：在802.11b实验中，节点为小型PC，配备Netgear MA701 Compact Flash 802.11b无线网卡，运行Linux内核版本2.4.19及hostap驱动。在802.11a实验中，节点为笔记本电脑，配备NetGear WAG511 CardBus 802.11a/b/g网卡，运行Linux内核版本2.4.26及MIT madwifi-stripped驱动。所有无线电均配备全向天线，其性能可与未来消费电子中可能集成的无线电媲美（例如具备基础功能的低成本无线电）。此外，三个测试床均为同构系统：每个节点采用完全相同的硬件，以减少硬件特性对实验结果的影响。
我们的网络设置在所有实验中保持一致：所有节点使用未被占用的频率，且该频率与下一个被占用的802.11频率至少相隔5个信道。为便于实验，我们采用802.11独立基础服务集（Independent Basic Service Set, IBSS）模式，允许所有节点直接通信。然而，该配置并不限制我们的结果仅适用于自组织（mesh）拓扑。
数据收集方法：每个节点依次向其他所有节点运行实验。实验旨在评估：（i）成功/丢失率；（ii）不同传输速率（txrate）和传输功率（txpower）组合下的吞吐量。我们还针对特定实验调整节点位置，以量化节点精确位置、天线方向及障碍物对结果的影响。实验在夜间进行，以避免人员移动造成的干扰并确保可重复性。除非明确说明，否则每个结果仅代表单次实验运行（因实验耗时较长）；相反，我们依赖后续小节中介绍的验证运行来增强结果的可信度。

Traceset intel/home/reachability
家庭无线网络的连通性及吞吐量测量数据
测量目的：网络性能分析
方法：
连通性：连通性实验通过从每个节点向其他所有节点发送一系列UDP探针数据包，评估家庭网络中各节点对之间的链路质量（以成功/丢失率衡量）。每个探针数据包包含源节点信息及其在序列中的编号。探针数据包大小和每个子实验的持续时间均可配置。在所有实验中，链路层重传被禁用，探针大小为1472字节，每个子实验持续60秒，探针发送频率为每500毫秒1个。每个无线链路独立评估，网络内无同时传输。
吞吐量：吞吐量实验旨在评估家庭网络中层3通信的质量，针对TCP和UDP协议均进行了吞吐量评估。我们采用相同的基础方法，即对测试床中六节点的所有节点对进行测量。吞吐量通过netperf流量生成器测量（使用1472字节数据包）。每个节点依次向其他所有节点发起netperf连接，并测量60秒时间间隔内的吞吐量。与连通性实验不同，吞吐量实验启用了链路层重传（最大3次重试），这可能缓解链路质量短期下降的影响。
自动速率（autorate）：当发送方采用自动速率（autorate）时，收集60秒流的UDP/TCP吞吐量测量数据。

intel/home/reachability 数据集
平面图：三所住宅的近似平面图。
文件：floorplan.tar.gz
配置：三所不同住宅（2所位于美国：ushome1、ushome2；1所位于英国：ukhome1）的平面图。平面图图像中的线条反映了连通性实验中丢失率超过90%的（单向）链路。
格式：三个PNG文件

距离：各节点对之间的距离。
文件：distance.tar.gz
配置：三所住宅（ushome1、ushome2、ukhome）原始部署中各节点对之间的距离（单位：英尺）。
格式：每行对应一组距离数据
结果：各节点对之间的距离。

结果：连通性及吞吐量结果。
文件：reachability.tar.gz
配置：连通性及吞吐量测量结果。
格式：文件名格式如下：
{House}-{Exp}-{Network}-{Traffic}-{Txrate}-{Txpower}.{Mode}.txt
- House：ushome1、ushome2或ukhome
- Exp：original（原始拓扑）、validation（验证运行）、rotated（节点旋转180度）或autorate（启用自动速率）
- Network：b（802.11b）或a（802.11a）
- Traffic：udp或tcp
- Txrate：传输速率（例如：2Mbps）
- Txpower：传输功率（例如：30mW）
- Mode：comb（用于连通性/吞吐量实验）或top（用于多跳吞吐量实验）
所有文件格式如下：每行对应从node2->node3、node2->node4、node2->node5、node2->node6、node2->node7、node3->node2、node3->node4等节点对收集的测量数据（node1用于控制实验）。测量数据的第一列对应成功接收的UDP探针数量（总探针数为120）；第二列对应从源节点到目的节点的吞吐量测量值（单位：Mbps）。

intel/home/multihop
家庭无线网络的多跳吞吐量测量数据
测量目的：网络性能分析
方法：
多跳：针对测试床中的一个特定节点，我们设置通过其他所有节点的多跳路径，并使用netperf测量由此产生的UDP吞吐量。我们发现，多跳UDP吞吐量可通过以下公式较好地近似：thr(src, dst) = 1/(1/thr(src,relay)+1/thr(relay,dst))，其中src表示发送节点，dst表示接收节点，relay表示在两者之间中继流量的节点。我们比较了三种不同拓扑下的网络性能：
（i）直接（Direct）拓扑：每个节点使用直接路径与其他节点通信；
（ii）AP拓扑（AP-topology）：选择一个特定节点作为其他所有节点之间的中继；
（iii）多跳拓扑（Multihop-topology）：节点之间使用拓扑中的最优路径通信，最优性定义为最小空中时间（即选择使数据包在网络中占用时间最少的路径）。在此情况下，我们假设路径通过迪杰斯特拉（Dijkstra）算法选择，链路权重为中继空中时间。
所有实验测试测试床中两个节点之间的单流传输，网络内无竞争传输。

intel/home/multihop 数据集
结果：多跳UDP吞吐量结果。
文件：multihop.tar.gz
配置：为评估使用单跳测量近似两跳吞吐量的准确性，我们以ukhome1中的node2作为发送节点，并通过其他所有节点作为中继，测量其到家庭中其他所有节点的两跳吞吐量。然后将估计值与实测两跳值进行比较。请注意，此类分析仅针对UDP吞吐量。
格式：文件名格式如下：
{House}-{Exp}-{Network}-{Traffic}-{Txrate}-{Txpower}.{Mode}.txt
- House：ushome1、ushome2或ukhome
- Exp：original（原始拓扑）、validation（验证运行）、rotated（节点旋转180度）或autorate（启用自动速率）
- Network：b（802.11b）或a（802.11a）
- Traffic：udp或tcp
- Txrate：传输速率（例如：2Mbps）
- Txpower：传输功率（例如：30mW）
- Mode：comb（用于连通性/吞吐量实验）或top（用于多跳吞吐量实验）
所有文件格式如下：第一行表示测试的节点对，其他每行包含一个实验描述符，指示测试的拓扑类型。