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.

本数据集包含从部署于3处不同住宅的6节点网格中采集的连通性与UDP/TCP吞吐量数据。
测量起始时间：2005年6月29日；测量结束时间：2005年7月3日。

采集环境说明：本数据集的连通性与UDP/TCP吞吐量数据采自部署于3处住宅的6节点网格，其中2处住宅位于美国（分别记为ushome1与ushome2），1处住宅位于英国（记为ukhome1）。实验采集了不同发射功率、传输速率，以及802.11a（802.11a）、802.11b（802.11b）无线设备下的测试结果。

以下是3处住宅的简要说明与近似楼层平面图（可从trace intel/home/reachability/floorplan路径下载）：
住宅标识 面积（ft²） 建筑结构 楼层数 节点数量
ushome1 2,500 木结构 2 6
ushome2 2,600 木结构 3 6
ukhome1 1,500 砖/钢结构 3 6

网络配置说明：
针对802.11b（802.11b）实验，测试节点为搭载Netgear MA701紧凑型闪存802.11b无线网卡的小型紧凑型PC，运行Linux内核版本2.4.19与hostap驱动程序。针对802.11a（802.11a）实验，测试节点为搭载NetGear WAG511 CardBus 802.11a/b/g无线网卡的笔记本电脑，运行Linux内核版本2.4.26与MIT madwifi-stripped驱动程序。所有无线网卡均配备全向天线，其性能可与未来消费电子集成的基础功能廉价无线模块相媲美。此外，三处测试床均采用同构配置：每个节点使用完全相同的硬件，以降低硬件特性差异对测试结果的影响。

所有实验采用统一的网络设置：所有节点使用与其他已占用802.11频段至少相隔5个信道的未使用频段。为便于实验开展，我们采用802.11独立基本服务集（IBSS，Independent Basic Service Set）模式，允许所有节点直接通信。但该配置并未将实验结果的适用范围限制在自组织（Mesh）拓扑中。

数据采集方法：
每个节点依次向其他所有节点发起实验。本实验旨在评估：(i) 不同传输速率（Txrate）与发射功率（Txpower）组合下的链路成功率/丢包率，以及(ii) 对应吞吐量。我们还会在特定实验中调整节点位置与天线朝向，以量化节点精确位置、天线朝向与障碍物对链路性能的影响。实验均在夜间开展，以避免人员移动带来的干扰并提升实验可复现性。除非另有明确说明，每个结果均来自单次实验运行——因本实验耗时极长，我们通过后续小节中的验证实验来确保结果的可信度。

### 追踪集：intel/home/reachability
本追踪集包含家庭无线网络的连通性与吞吐量测量数据，测量目的为网络性能分析。

#### 连通性测试方法
连通性实验通过评估家庭网络中每对节点间的链路质量（以链路成功率/丢包率为指标），具体方式为：从每个节点向其他所有节点发送一系列UDP探测包，每个探测包包含源节点标识与该包在序列中的编号。探测包大小与单次子实验时长均可配置。本实验中，链路层重传功能均已禁用，探测包大小为1472字节，单次子实验时长为60秒，发包频率为每500毫秒1个包。每个无线链路均独立评估，网络内无同时传输行为。

#### 吞吐量测试方法
吞吐量实验用于评估家庭网络的三层通信质量，分别针对TCP与UDP协议开展测试。本吞吐量实验采用与连通性实验一致的基础方法，基于测试床中6个节点的所有配对组合开展测量。吞吐量通过netperf流量生成器使用1472字节数据包进行测量：每个节点依次向其他所有节点发起netperf连接，并在60秒的时间窗口内测量吞吐量。与连通性实验不同，吞吐量实验启用了链路层重传（最多重试3次），以缓解链路质量短期劣化的影响。

#### 自动速率测试
当发射端采用自动速率模式时，采集60秒流量的UDP/TCP吞吐量数据。

##### 楼层平面图（floorplan）
文件：floorplan.tar.gz
配置说明：包含3处住宅的楼层平面图，其中2处位于美国（ushome1、ushome2），1处位于英国（ukhome1）。平面图中的线条代表在连通性实验中丢包率超过90%的（单向）链路。
格式：3张PNG图像文件

##### 节点间距（distance）
文件：distance.tar.gz
配置说明：包含原始部署场景下，3处住宅（ushome1、ushome2、ukhome1）中每对节点间的距离，单位为英尺。
格式：每行代表一组节点间距数据

##### 连通性与吞吐量结果（reachability）
文件：reachability.tar.gz
配置说明：连通性与吞吐量测试结果。
文件名格式如下：{House}-{Exp}-{Network}-{Traffic}-{Txrate}-{Txpower}.{Mode}.txt
各字段说明：
- House：ushome1、ushome2或ukhome1
- Exp：original（原始拓扑）、validation（验证实验）、rotated（节点旋转180度）或autorate（启用自动速率模式）
- Network：b（802.11b）或a（802.11a）
- Traffic：udp或tcp
- Txrate：传输速率（例如2Mbps）
- Txpower：发射功率（例如30mW）
- Mode：comb（用于连通性/吞吐量实验）或top（用于多跳吞吐量实验）

所有结果文件格式统一：每行代表从节点2→节点3、节点2→节点4、节点2→节点5、节点2→节点6、节点2→节点7、节点3→节点2、节点3→节点4等链路的测量数据（节点1用于控制实验）。测量数据的第一列为成功接收的UDP探测包数量（总探测包数为120），第二列为从源节点到目的节点的吞吐量，单位为Mbps。

### 追踪集：intel/home/multihop
本追踪集包含家庭无线网络的多跳吞吐量测量数据，测量目的为网络性能分析。

#### 多跳测试方法
针对测试床中的某个特定节点，我们通过其他所有节点构建多跳路径，并使用netperf测量对应的UDP吞吐量。我们验证了多跳UDP吞吐量可通过如下公式近似估算：
$$ ext{thr}(src, dst) = frac{1}{frac{1}{ ext{thr}(src,relay)} + frac{1}{ ext{thr}(relay,dst)}}$$
其中src为发送节点，dst为接收节点，relay为中继节点。基于该公式，我们对比了三种不同拓扑下的网络性能：
(i) 直连拓扑：每个节点通过直连路径与其他所有节点通信；
(ii) AP拓扑：选择一个特定节点作为测试床中任意其他两个节点间的中继；
(iii) 多跳拓扑：节点通过拓扑中的最优路径通信，最优路径定义为总空中传输时间最短的路径。本场景中，我们假设使用迪杰斯特拉算法（Dijkstra's algorithm）选择路径，链路权重为中继空中传输时间，即选择可使两个节点间的数据包在网络中占用最少时间的路径。
所有实验均测试测试床中两个节点间的单一流的性能，网络内无其他竞争传输占用带宽。

#### 多跳测试结果
文件：multihop.tar.gz
配置说明：为评估使用单跳测量值近似两跳吞吐量的准确性，我们选取ukhome1中的node2作为发送节点，以其他所有节点作为中继，测量到其他所有节点的两跳吞吐量，并将估算值与实测两跳吞吐量进行对比。本分析仅针对UDP吞吐量。
文件名格式如下：{House}-{Exp}-{Network}-{Traffic}-{Txrate}-{Txpower}.{Mode}.txt
各字段说明：
- House：ushome1、ushome2或ukhome1
- Exp：original（原始拓扑）、validation（验证实验）、rotated（节点旋转180度）或autorate（启用自动速率模式）
- Network：b（802.11b）或a（802.11a）
- Traffic：udp或tcp
- Txrate：传输速率（例如2Mbps）
- Txpower：发射功率（例如30mW）
- Mode：comb（用于连通性/吞吐量实验）或top（用于多跳吞吐量实验）

所有结果文件格式统一：第一行为测试的节点对，其余每行包含一个实验描述符，用于说明测试的拓扑类型。