CRAWDAD umass/diesel

The bus-based DTN (Disruption-tolerant networks) traces from UMass Amherst campus. 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. The following traces have been added: transfer/fall2007, transfer/ap_connectivity, and transfer/vifi. date/time of measurement start: 2005-01-25 date/time of measurement end: 2007-12-14 collection 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.  Tracesets umass/diesel/throwboxfile: 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. umass/diesel Traces throwbox/summer2006: Bus-to-bus, bus-to-throwbox transfer record collected from DieselNet during 2006 summer.file: DieselNetThrowbox.tar.gzconfiguration: 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. umass/diesel/transferfile: DieselNetThrowbox.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. transfer/fall2007: Data transfer logs on UmassDieselNet, a disruption-tolerant network (DTN) in the months October-November 2007.file: dieselnet-fall-2007.tar.gzconfiguration: The released traces have five directories 1. gps_logs : This is the directory which has the cumulative gps_logs for all the buses seen during the period which the traces were collected. 2. mobile-mobile: This is the collection of all the mobile-mobile contact events. 3. basestation-mobile: The traces are similar to the mobile-mobile traces but are for the AP-mobile contact events. 4. mobile-mobile-mesh-relay: these are the traces for the connection events between a mobile node and the six stationary relay/mesh boxes placed in the network. 5. xtendtrace: This has the connection events between mobile nodes over the Xtend Maxstream radio. If you use these traces in a research paper, please reference the traces as Relays, Base Stations, and Meshes: Enhancing Mobile Networks with Infrastructure. Nilanjan Banerjee, Mark D. Corner, Don Towsley, and Brian Neil Levine. In Proceedings of ACM MobiCom, San Francisco, CA, USA, September 2008. format: The released traces have five directories 1. gps_logs : This is the directory which has the cumulative gps_logs for all the buses seen during the period which the traces were collected. There is a directory corresponding to every bus and within each directory for a bus there are files for every day with a set of time stamped gps locations. 2. mobile-mobile: This is the collection of all the mobile-mobile contact events. Each line includes the time at which a contact occured, the amount of data that was transfered, the duration of contact and the position where the contact took place. 3. basestation-mobile: The traces are similar to the mobile-mobile traces but are for the AP-mobile contact events. 4. mobile-mobile-mesh-relay: these are the traces for the connection events between a mobile node and the six stationary relay/mesh boxes placed in the network. 5. xtendtrace: This has the connection events between mobile nodes over the Xtend Maxstream radio.