CRAWDAD umass/diesel (v. 2007-12-02)

This dataset includes the real mobility and real transfers of the bus-based DTN (Disruption-tolerant-network) testbed, called UMassDieselNet, operating from the UMass Amherst campus and the surrounding county.last modified :2007-12-05release date :2007-12-02date/time of measurement start :2005-01-25date/time of measurement end :2007-05-14collection environment :We have constructed a DTN testbed composed of 30-40 buses operated by the UMass Amherst branch of the Pioneer Valley Transport Authority (PVTA) that we have fitted with a custom package of off-the-shelf hardware. This testbed is called UMassDieselNet. The transit buses service an area sparsely covering approximately 150 square miles. The route each bus is placed on each day is chosen by the garage dispatcher and can change during the day. Buses can leave the network at any time. We did not try to automatically determine the routes of buses, though this is possible with some significant effort. We decided against this approach after finding GPS data often inconsistent or containing gaps where line-of-sight to satellites was lost.network configuration :The testbed began operating in May 2004 with five buses. Each bus carries a HaCom Open Brick computer (P6-compatible 577Mhz CPU, 256MB RAM). An 802.11b Access Point (AP) is attached to each brick to provide DHCP access to passengers and passersby. A second USB-based 802.11b interface constantly scans the surrounding area for DHCP offers and other buses. Each bus also has a GPS device attached to the brick. Each brick runs Linux on a 40GB notebook hard drive.data collection methodology :See the metadata of each traceset or trace for details of collection methodology.Tracesetumass/diesel/throwboxBus-to-bus, bus-to-throwbox transfer record collected from DieselNet during 2006 summer.files: DieselNetThrowbox.tar.gzdescription: This traceset was collected during the throwbox deployment in Umass DieselNet in Summer 2006. The traces contain bus-bus transfer records and bus-throwbox transfer records.measurement purpose: Routing Protocol for DTNs (Disruption Tolerant Networks), User Mobility Characterizationmethodology: One solution for improving DTN performance is to place additional stationary nodes in the network, which increases the number and frequency of contact opportunities. We proposed the use of throwboxes within a DTN for this purpose. Throwboxes are inexpensive, battery-powered, stationary nodes with radios and storage. When two nodes pass by the same location at different times, the throwbox acts as a router, creating a new contact opportunity. To support a real-world test of the throwbox, we used our DTN testbed, the UMassDieselNet. The testbed normally consists of 40 buses covering an area of more than 150 square miles. However, when the experiments were performed, during a reduced summer bus schedule, only 10 buses were running on three routes. Each bus is a highly mobile DTN node using a small computer with an attached access point and WiFi interface. Buses constantly scan for other nodes and transfer DTN data whenever a connection can be made. We augmented the equipment on the buses with an XTend radio and added scripts to beacon the position, speed, and direction of motion of the buses once each second. We deployed three always-on throwbox prototypes in fixed locations for three weeks on the UMassDieselNet bus routes.last modified: 2007-12-05dataname: umass/diesel/throwboxversion: 20071202change: the initial versionrelease date: 2007-12-02date/time of measurement start: 2005-01-25date/time of measurement end: 2007-05-14umass/diesel/throwbox Tracessummer2006: Bus-to-bus, bus-to-throwbox transfer record collected from DieselNet during 2006 summer.configuration: The traces contains connection event between buses (in DieselNet) and buses and throwboxes placed in the network.format: The name of the bus nodes follow the pattern "PVTA_(bus number)". The three throwboxes placed in the network have names "PVTA_TB0", "PVTA_TB1", "PVTA_TB2". The connectivity traces have data about the duration of contact, time at which the contact took place, the amount of data transfered, the position (longitude and latitude) at which the connections happened and the speed and direction of the bus motion when the connection event took place. The filenames indicate the date on which the connection trace was collected. For example, 6-23-2006 would mean June 23, 2006.description: The traces contains connection event between buses (in DieselNet) and buses and throwboxes placed in the network.last modified: 2007-12-05dataname: umass/diesel/throwbox/summer2006version: 20071202change: the initial versionrelease date: 2007-12-02date/time of measurement start: 2006-06-23date/time of measurement end: 2006-07-21url: /download/umass/diesel/DieselNetThrowbox.tar.gzumass/diesel/transferData transfer logs between buses on UmassDieselNet, a disruption-tolerant network (DTN).files: APConnectivitySpring2007.tar.gz, DieselNetTracesSpring2006.tar.gz, DieselNetTracesSpring2007.tar.gz, UMassDieselNet_Spring2005.tar.gzdescription: This set of DieselNet logs were compiled from busses running routes serviced by UmassTransit, which lists their bus routes on the web at http://www.umass.edu/campus_services/transit/. Of UmassTransit's busses, 30-40 busses were equipped with DieselNet equipment and a certain portion of those operated daily as dictated by bus failures and maintenance.measurement purpose: Routing Protocol for DTNs (Disruption Tolerant Networks), User Mobility Characterizationmethodology: To maintain and monitor our network, we use numerous external APs that offer free service along the bus routes hosted by third parties. We have installed only two APs - one on campus and one at the bus garage. Whenever the buses have web access, they retrieve software updates from a central server. At that time a bus provides its current GPS location and MAC address, and it uploads logs of its performance during the day, including the throughput of bus-to-bus transfer opportunities, APs contacted, a record of movement, and application records. To enable bus-to-bus transfers, the buses beacon on a single channel once every 100ms. We programmed the bricks in each bus to transfer the largest amount of data possible using TCP at each transfer opportunity. To allow us to easily test different routing algorithms in a real DTN environment, we set the UMassDieselNet buses to transmit random data to one another whenever they are within range and record the time, transmission size, and buses involved.last modified: 2007-12-05dataname: umass/diesel/transferversion: 20071202change: The following traces have been added: transfer/spring2006, transfer/spring2007, and transfer/ap_connectivityrelease date: 2007-12-02date/time of measurement start: 2005-01-25date/time of measurement end: 2007-05-14hole: We excluded holidays and other occasions causing buses to run infrequently.umass/diesel/transfer Tracesap_connectivity: Bus-to-ap transfer record collected from DieselNet during the spring semester of 2007.configuration: UmassTransit's 40 busses were equipped with DieselNet equipment and a certain portion of those operated daily as dictated by bus failures and maintenance.format: All connection events occurring during a day are stored in the log file matching that date (month/day/year). The buses are identified by their MAC address. Time stamps are recorded as absolute minutes and seconds after midnight. In the following entry, bus 00:09:5B:B3:51:6B met an access point at 16 minutes and 44 seconds after midnight for a duration of 36 seconds. Bus 00:09:5B:B3:51:6B with AP at time 00:16:44 for 36.0 secondsdescription: Bus-to-ap transfer record collected from DieselNet during the spring semester of 2007.last modified: 2007-12-05dataname: umass/diesel/transfer/ap_connectivityversion: 20071202change: the initial versionrelease date: 2007-12-02date/time of measurement start: 2007-03-26date/time of measurement end: 2007-03-30url: /download/umass/diesel/APConnectivitySpring2007.tar.gzspring2006: Bus-to-bus transfer record collected from DieselNet during the spring semester of 2006.configuration: This trace includes two directories: * Bus-Bus subdirectory contains bus-to-bus transfer records * DispatchRecord subdirectory contains bus dispatching records.format: 1. Bus-to-bus transfer records are saved in files named as MDDYYYY, for example, file 2082006 contains transfer records for Feb 08, 2006. Within each file, each line describe a bus-to-bus transfer. For example, the following sample lines: Bus 3112 at 72.532745 42.393852 on route 1 in contact with bus 3114 at 72.532745 42.393852 on route 1 at time 418:27 for 45204688 bytes in 184792.0 ms means that the bus 3112 was in contact with bus 3114 while it's at location (72.532745 N,42.393852 W). The contact started at 418mins and 27 seconds after the 00:00:00 (i.e., 6:58:27 A.M.) of Feb 28, 2006, and lasts for 194792.0 milliseconds. Note that the "on route 1" information should be ignored. 2. Dispathcing records include two files: DA_all.txt and DB_sheet.txt. * The DA_all.txt contains the dispatching records (inputed by hand from the DA sheets, with drivers name ignored). For example, the following sample lines in the file: ---------------------------------------------------- DATE 4/3/2006 ## AM SHIFTS TIME_AT_GARAGE SHIFT BUS DRIVER In_SERVICE IN_SERVICE_LOC DRVR_CHNG 6:10 AM21 34 NA 6:55 MHC 10:30 6:10 AM42 32 NA 6:30 GRC 8:32 6:25 AM22 38 NA 6:45 HAGISMALL 11:00 6:30 AM43 42 NA 6:50 STKRD 9:05M 9:23T 6:40 AM45 12 NA 7:00 GRC 8:49 6:40 AM31 16 NA 7:10 HAMPCOLL 10:45B/11:05G 6:42 AM11 33 NA 7:12 OLDBTOWN 10:51 6:45 AMA 21 NA 7:05 STADIUM 10:35 6:50 AM23 35 NA 7:10 HAGISMALL 10:00 6:52 AM1 36 NA 7:19 CLIFFSIDE 10:52 ..... Here, DATE line indicates the following records are for the date specified. Each line follows give "TIME_AT_GARAGE SHIFT BUS DRIVER In_SERVICE IN_SERVICE_LOC DRVR_CHNG" for each shift. For example, the line: 6:10 AM21 34 NA 6:55 MHC 10:30 means that bus 34 serve shift AM21 on that day, it starts at garage at 6:10 A.M., and starts to enter service at 6:55 A.M. at bus stop MHC. The bus will be changed to another driver (also to another shift) at 10:30 A.M. ** DB_sheet.txt contains essentially similar information, dumped from a database system. Each line in the file specifies the mapping from bus to shift. For example, 03/01/2006,30,15MID,3033 means that on March 1 2006, bus 3033 was dispatched to run on shift MID15, route 30.description: Bus-to-bus transfer record collected from DieselNet during the spring semester of 2006.last modified: 2007-12-05dataname: umass/diesel/transfer/spring2006version: 20071202change: the initial versionrelease date: 2007-12-02date/time of measurement start: 2006-01-30date/time of measurement end: 2006-06-22url: /download/umass/diesel/DieselNetTracesSpring2006.tar.gzspring2007: Bus-to-bus transfer record collected from DieselNet during the spring semester of 2007.configuration: This set of DieselNet traces where compiled during Spring 2007 from busses running routes serviced by UmassTransit. UmassTransit's 40 busses were equipped with DieselNet equipment and a certain portion of those operated daily as dictated by bus failures and maintenance.format: All connection events occurring during a day are stored in the log file matching that date (month/day/year). The buses are identified by their MAC address. Time stamps are recorded as absolute minutes and seconds after midnight. In the following entry, bus 00:09:5B:B3:E3:4E sent bus 00:09:5B:B5:6E:6E at 06:57:18 transferring 94240422 bytes. The latitude and longitude of meeting is 72.53267 and 42.39381 respectively. The last column is true if the satellite reading is current and false otherwise. 00:09:5B:B3:E3:4E 00:09:5B:B5:6E:6E 06:57:18 94240422 72.53267 42.39381 truedescription: This set of DieselNet traces where compiled during Spring 2007 from busses running routes serviced by UmassTransit, which lists their bus routes on the web at http://www.umass.edu/campus_services/transit/. UmassTransit's 40 busses were equipped with DieselNet equipment and a certain portion of those operated daily as dictated by bus failures and maintenance.last modified: 2007-12-05dataname: umass/diesel/transfer/spring2007version: 20071202change: the initial versionrelease date: 2007-12-02date/time of measurement start: 2007-02-06date/time of measurement end: 2007-05-14url: /download/umass/diesel/DieselNetTracesSpring2007.tar.gzinfocom2006: Data transfer logs between buses on UmassDieselNet, a disruption-tolerant network (DTN) for Infocom 2006 paper.configuration: Our testbed is subject to the real schedule of the UMass campus - many fewer buses run on weekends and holidays. To realize some uniformity, we used 60 traces from weekdays between January 25, 2005 to May 6, 2005; we excluded holidays and other occasions causing buses to run infrequently. On average, about 28 buses are active each day, and each days lasts from about 7AM to 7PM. In all, the traces consist of over 720 hours of recorded data for each of the 30 buses (about 20,000 bus-hours total). Busses are assigned a route semi-arbitrarily each day. Some routes require short busses, some routes require long busses, and some vary by their passenger capacity needs: - Routes 30, 31, and 38 must use long busses - Routes 34, 35, 37, and 39 must use shot busses - Routes 32, 33, 36, 45, and 46 may use either Bus numbers beginning 30xx are long busses, bus numbers beginning 31xx are short busses. Though not present in these logs, prefix numbers other than 31xx and 30xx indicate a test unit or other non-bus based unit (which often show up on the Umass DieselNet web site).format: All connection events occurring during a day are stored in the log file matching that date (month/day/year). Log events are entered by the bus receiving the data, which is the first bus listed on each line. Though events would ideally be symmetrical, they, in reality, are not. Whichever sending connection begins first will reach maximum speed and slow the "ramping up" of the TCP connection going in the other direction (over time they will equalize). Additionally, a connection in one event may succeed while a connection in the opposite direction may not be established due to network configuration hiccups (the linux network stack and wifi drivers were not targeted toward an environment where interfaces are rapidly reconfigured). Time stamps are recorded as absolute minutes and seconds after midnight. In the following entry, bus 3123 receives 277512 bytes from bus 3102 at 6:55:11 AM. Routes and GPS coordinates should be ignored because GPS information was not accurate when these logs were being generated. "Bus 3123 at 72.53236 42.3933 on route 1 in contact with bus 3102 at 72.53236 42.3933 on route 1 at time 415:11 for 277512 bytes"description: This set of DieselNet logs were compiled during the Spring semester of 2005 from busses running routes serviced by UmassTransit, which lists their bus routes on the web at http://www.umass.edu/campus_services/transit/. Of UmassTransit's 40 busses, approximately 30 busses were equipped with DieselNet equipment and a certain portion of those operated daily as dictated by bus failures and maintenance.last modified: 2007-12-05dataname: umass/diesel/transfer/infocom2006version: 20060117change: the initial versionrelease date: 2006-01-17date/time of measurement start: 2005-01-25date/time of measurement end: 2005-05-22url: /download/umass/diesel/UMassDieselNet_Spring2005.tar.gz

本数据集收录了基于公交的容断网络（DTN，Disruption-Tolerant Network）测试床UMassDieselNet的真实移动性与真实传输数据。该测试床部署于马萨诸塞大学阿默斯特分校（UMass Amherst）校园及周边县域范围。
最后修改时间：2007-12-05
发布日期：2007-12-02
测量起始时间：2005-01-25
测量结束时间：2007-05-14

### 采集环境
我们搭建了一套容断网络测试床，由先锋谷交通局（PVTA，Pioneer Valley Transport Authority）马萨诸塞大学阿默斯特分校下属的30至40辆公交组成，并为每辆公交加装了定制化的商用硬件套件，该测试床即为UMassDieselNet。这些公交的服务范围覆盖约150平方英里的稀疏城区。每日分配给每辆公交的运营线路由车库调度员确定，且可在当日中途变更。公交可随时脱离网络。尽管通过大量工作可以自动识别公交线路，但我们并未采用该方案——因为我们发现全球定位系统（GPS，Global Positioning System）数据常存在不一致性，或在卫星视线受阻时出现数据缺失。

### 网络配置
该测试床于2004年5月启动运行，初始仅配备5辆公交。每辆公交搭载一台HaCom Open Brick计算机（兼容P6架构，577MHz CPU，256MB内存）。每台设备均加装了一个802.11b无线接入点（AP，Access Point），可为乘客及过往人员提供动态主机配置协议（DHCP，Dynamic Host Configuration Protocol）接入服务。此外，还配备了第二个基于通用串行总线（USB，Universal Serial Bus）的802.11b接口，持续扫描周边区域以发现DHCP服务与其他公交节点。每辆公交的HaCom设备还连接了一台GPS接收机，所有设备均基于40GB笔记本硬盘运行Linux操作系统。

### 采集方法概述
具体采集细节请参见各轨迹集或单条轨迹的元数据。

---
#### 数据集1：umass/diesel/throwbox
该轨迹集收录了2006年夏季从DieselNet采集的公交间、公交与转发盒（throwbox）间的传输记录。
文件：DieselNetThrowbox.tar.gz
数据集描述：本轨迹集采集自2006年夏季UMassDieselNet部署转发盒期间，包含公交间传输记录与公交-转发盒传输记录。
测量用途：容断网络路由协议、用户移动性特征刻画
采集方法：提升容断网络性能的一种方案是在网络中部署额外的静态节点，以增加接触机会的数量与频率。我们提出在容断网络中使用转发盒实现该目标：转发盒是低成本、电池供电的静态节点，配备无线通信模块与存储单元。当两个移动节点在不同时间经过同一位置时，转发盒可充当路由器，创造新的接触机会。为验证转发盒的实际应用效果，我们使用了UMassDieselNet测试床。该测试床常规配备40辆公交，覆盖面积超过150平方英里。但在本次实验期间，由于夏季公交班次缩减，仅有10辆公交在3条线路上运营。每辆公交均为高移动性的容断网络节点，搭载小型计算机、无线接入点与WiFi接口。公交持续扫描其他节点，一旦建立连接便传输容断网络数据。我们为公交加装了XTend无线电模块，并添加脚本以每秒一次的频率广播公交的位置、速度与运动方向。我们在UMassDieselNet的公交线路上的固定位置部署了3台始终在线的转发盒原型，部署时长为3周。
最后修改时间：2007-12-05
数据集名称：umass/diesel/throwbox
版本：20071202
更新说明：初始版本
发布日期：2007-12-02
测量起始时间：2005-01-25
测量结束时间：2007-05-14

##### 子轨迹集：umass/diesel/throwbox/summer2006
该轨迹集收录了2006年夏季从DieselNet采集的公交间、公交与转发盒间的传输记录。
配置：轨迹包含DieselNet测试床内公交之间、公交与部署的转发盒之间的连接事件。
格式：公交节点的命名格式为"PVTA_(公交编号)"。网络中部署的3台转发盒分别命名为"PVTA_TB0"、"PVTA_TB1"、"PVTA_TB2"。连接轨迹数据包含接触时长、接触发生时间、传输数据量、连接发生时的经纬度位置，以及连接发生时公交的运动速度与方向。文件名标识了连接轨迹的采集日期，例如"6-23-2006"代表2006年6月23日。
数据集描述：本轨迹包含DieselNet测试床内公交之间、公交与部署的转发盒之间的连接事件。
最后修改时间：2007-12-05
数据集名称：umass/diesel/throwbox/summer2006
版本：20071202
更新说明：初始版本
发布日期：2007-12-02
测量起始时间：2006-06-23
测量结束时间：2006-07-21
下载链接：/download/umass/diesel/DieselNetThrowbox.tar.gz

---
#### 数据集2：umass/diesel/transfer
本数据集收录了UMassDieselNet容断网络中公交间的数据传输日志。
文件：APConnectivitySpring2007.tar.gz、DieselNetTracesSpring2006.tar.gz、DieselNetTracesSpring2007.tar.gz、UMassDieselNet_Spring2005.tar.gz
数据集描述：本套DieselNet日志由UMassTransit运营的公交采集得到，UMassTransit的公交线路信息可在官网http://www.umass.edu/campus_services/transit/ 查询。UMassTransit的40辆公交中，有30至40辆加装了DieselNet设备，其中部分公交每日正常运营，其余因故障或维护暂停运行。
测量用途：容断网络路由协议、用户移动性特征刻画
采集方法：为维护和监控本网络，我们在公交沿线部署了多个第三方提供的免费外部无线AP。我们仅自行部署了两台AP：一台位于校园内，另一台位于公交车库。每当公交获得网络访问权限时，便从中央服务器获取软件更新，同时上报当前GPS位置与MAC地址，并上传当日的运行日志，包括公交间传输机会的吞吐量、接触过的AP、运动记录与应用程序记录。为实现公交间传输，公交每100ms在单个信道上广播探测包。我们将每辆公交的HaCom设备编程为在每次传输机会中尽可能多地使用TCP协议传输数据。为便于在真实容断网络环境中测试不同的路由算法，我们将UMassDieselNet的公交设置为：在通信范围内时互相传输随机数据，并记录传输时间、传输数据量与涉及的公交节点。
最后修改时间：2007-12-05
数据集名称：umass/diesel/transfer
版本：20071202
更新说明：新增以下轨迹：transfer/spring2006、transfer/spring2007与transfer/ap_connectivity
发布日期：2007-12-02
测量起始时间：2005-01-25
测量结束时间：2007-05-14
备注：我们排除了节假日及其他导致公交班次减少的时段。

##### 子轨迹集1：umass/diesel/transfer/ap_connectivity
该轨迹集收录了2007年春季学期从DieselNet采集的公交与AP间的传输记录。
配置：UMassTransit的40辆公交中，有部分加装了DieselNet设备，每日运营数量由公交故障与维护情况决定。
格式：每日发生的所有连接事件均存储在对应日期命名的日志文件中（格式为月/日/年）。公交通过MAC地址标识。时间戳记录为自午夜起的绝对分钟数与秒数。示例条目译为：公交00:09:5B:B3:51:6B于午夜后16分44秒与AP建立连接，连接时长为36秒。
数据集描述：本轨迹集收录了2007年春季学期从DieselNet采集的公交与AP间的传输记录。
最后修改时间：2007-12-05
数据集名称：umass/diesel/transfer/ap_connectivity
版本：20071202
更新说明：初始版本
发布日期：2007-12-02
测量起始时间：2007-03-26
测量结束时间：2007-03-30
下载链接：/download/umass/diesel/APConnectivitySpring2007.tar.gz

##### 子轨迹集2：umass/diesel/transfer/spring2006
该轨迹集收录了2006年春季学期从DieselNet采集的公交间传输记录。
配置：本轨迹包含两个子目录：
- Bus-Bus子目录：存储公交间传输记录
- DispatchRecord子目录：存储公交调度记录
格式：
1. 公交间传输记录：存储在以MDDYYYY命名的文件中，例如文件"2082006"包含2006年2月8日的传输记录。每个文件内的每一行描述一次公交间传输。示例行译为：公交3112在位置（72.532745 W，42.393852 N）与公交3114建立连接，连接于2006年2月28日午夜后418分27秒（即上午6:58:27）开始，持续时长为184792.0毫秒。注意："on route 1"相关信息可忽略。
2. 调度记录：包含两个文件DA_all.txt与DB_sheet.txt。
- DA_all.txt：包含调度记录（从调度表手动录入，未记录驾驶员姓名）。示例行译为：公交34于当日执行AM21班次，6:10从车库出发，6:55在MHC公交站开始运营，并于10:30更换驾驶员与班次。
- DB_sheet.txt：包含类似信息，从数据库系统导出。文件内每一行指定公交与班次的映射关系，例如"03/01/2006,30,15MID,3033"译为：2006年3月1日，公交3033被调度执行MID15班次，线路30。
数据集描述：本轨迹集收录了2006年春季学期从DieselNet采集的公交间传输记录。
最后修改时间：2007-12-05
数据集名称：umass/diesel/transfer/spring2006
版本：20071202
更新说明：初始版本
发布日期：2007-12-02
测量起始时间：2006-01-30
测量结束时间：2006-06-22
下载链接：/download/umass/diesel/DieselNetTracesSpring2006.tar.gz

##### 子轨迹集3：umass/diesel/transfer/spring2007
该轨迹集收录了2007年春季学期从DieselNet采集的公交间传输记录。
配置：本套DieselNet轨迹采集自2007年春季UMassTransit运营的公交。UMassTransit的40辆公交中，有部分加装了DieselNet设备，每日运营数量由公交故障与维护情况决定。
格式：每日发生的所有连接事件均存储在对应日期命名的日志文件中（格式为月/日/年）。公交通过MAC地址标识。时间戳记录为自午夜起的绝对分钟数与秒数。示例条目译为：公交00:09:5B:B3:E3:4E于06:57:18向公交00:09:5B:B5:6E:6E传输94240422字节数据，连接发生位置的经纬度分别为72.53267与42.39381，最后一列标识卫星读数是否有效（true为有效，false为无效）。
数据集描述：本套DieselNet轨迹采集自2007年春季UMassTransit运营的公交，UMassTransit的公交线路信息可在官网http://www.umass.edu/campus_services/transit/ 查询。UMassTransit的40辆公交中，有部分加装了DieselNet设备，每日运营数量由公交故障与维护情况决定。
最后修改时间：2007-12-05
数据集名称：umass/diesel/transfer/spring2007
版本：20071202
更新说明：初始版本
发布日期：2007-12-02
测量起始时间：2007-02-06
测量结束时间：2007-05-14
下载链接：/download/umass/diesel/DieselNetTracesSpring2007.tar.gz

##### 子轨迹集4：umass/diesel/transfer/infocom2006
本数据集收录了用于Infocom 2006论文的UMassDieselNet容断网络中公交间的数据传输日志。
配置：本测试床遵循马萨诸塞大学校园的真实公交排班——周末与节假日的公交班次大幅减少。为保证数据一致性，我们选取了2005年1月25日至2005年5月6日的工作日轨迹共60条，排除了节假日及其他导致公交班次减少的时段。每日平均有约28辆公交活跃，运营时间约为上午7点至下午7点。所有轨迹累计时长超过720小时，覆盖30辆公交（总公交时长约20000小时）。每日为公交分配的线路具有一定随机性，部分线路需要长公交，部分需要短公交，部分线路则根据乘客载客量需求调整：
- 线路30、31、38必须使用长公交
- 线路34、35、37、39必须使用短公交
- 线路32、33、36、45、46可使用任意类型公交
编号以30xx开头的公交为长公交，以31xx开头的为短公交。尽管本日志中未出现，前缀非30xx/31xx的公交编号代表测试单元或其他非公交节点（常出现在UMass DieselNet官网中）。
格式：每日发生的所有连接事件均存储在对应日期命名的日志文件中（格式为月/日/年）。日志事件由接收数据的公交录入，即每行列出的第一个公交为接收方。理想情况下事件应是对称的，但实际并非如此：先发起的连接会达到最大传输速率，并减缓反向TCP连接的建立速度（最终二者速率会趋于一致）。此外，一个方向的连接可能成功建立，而反向连接可能因网络配置问题（Linux网络栈与WiFi驱动并非针对快速重配置的接口环境优化）无法建立。时间戳记录为自午夜起的绝对分钟数与秒数。示例行译为：公交3123于午夜后415分11秒（即上午6:55:11）从公交3102接收277512字节数据，连接发生位置为（72.53236 W，42.3933 N）。注意：线路与GPS坐标信息可忽略，因为生成该日志时GPS数据并不准确。
数据集描述：本套DieselNet日志采集自2005年春季学期UMassTransit运营的公交，UMassTransit的公交线路信息可在官网http://www.umass.edu/campus_services/transit/ 查询。UMassTransit的40辆公交中，有约30辆加装了DieselNet设备，每日运营数量由公交故障与维护情况决定。
最后修改时间：2007-12-05
数据集名称：umass/diesel/transfer/infocom2006
版本：20060117
更新说明：初始版本
发布日期：2006-01-17
测量起始时间：2005-01-25
测量结束时间：2005-05-22
下载链接：/download/umass/diesel/UMassDieselNet_Spring2005.tar.gz