CRAWDAD usc/mobilib

VPN session, DHCP log, and trap log data from wireless network at USC.

This dataset includes VPN session, DHCP log, and tcap log data, for 79 access points and several thousand users at USC.

date/time of measurement start: 2003-12-23

date/time of measurement end: 2006-04-28

collection environment: This data set was collected during 2003-2005 at the USC campus, where the number of WLAN users was over 4500.

network configuration: At the time of collection, the USC wireless LAN had 79 APs.

data collection methodology: These traces are logs for timestamps of (start|stop) of VPN sessions. At USC, wireless users must establish connections to a VPN server before they can use the network. Hence the session log contains periods of users potentailly using the network, with its private (dynamic) IP addresses.

Traceset

usc/mobilib/session

VPN session logs from USC wirelss network.

• file: USC_sessions.tgz
  
• description: This traceset contains logs for timestamps of (start|stop) of VPN sessions.
• measurement purpose: User Mobility Characterization, Usage Characterization, Human Behavior Modeling
• methodology: These traces are logs for timestamps of (start|stop) of VPN sessions. At USC, wireless users must establish connections to a VPN server before they can use the network. Hence the session log contains periods of users potentailly using the network, with its private (dynamic) IP addresses.

usc/mobilib/session Trace

• vpn: VPN session logs from USC wireless network.
• file: USC_sessions.tgz
• configuration: These logs of sessions are collected at the VPN server for wireless users at USC. Before using the network, users must establish a VPN session to the server. The "Start" and "Stop" timestamps in the trace represents the beginning and the end of these VPN sessions.
• format: The fields in each line of the trace are: 1. Day of the week: Sun, Mon, Tue, Wed, Thu, Fri, Sat 2. Month 3. Day 4. Time: HH:MM:SS 5. Action: "Start" or "Stop" of a session. 6. Private IP in USC network. 7. Public IP given to the host.

usc/mobilib/dhcp

DHCP logs from USC wirelss network.

• file: USC_dhcp.tgz

• description: This traceset contains The DHCP log of the private IP assignments to MAC addresses.
• measurement purpose: User Mobility Characterization, Usage Characterization, Human Behavior Modeling
• methodology: The DHCP log contains the private IP assignments to MAC addresses.

usc/mobilib/dhcp Trace

• dhcp_log: Trace of DHCP logs from USC wirelss network.
• configuration: This log contains the private IP assignments to MAC addresses. The listed private IP is given to the MAC address at the indicated time.
• format: The fields are: 1. Month 2. Day 3. Time: HH:MM:SS 4. Private IP in USC network 5. MAC address

usc/mobilib/trap

Trap logs from USC wirelss network.

• file: USC_traps.tgz, USC_old_trap.tgz
• description: This traceset contains the trap log of the (switch port, MAC address) association when the user is online.
• measurement purpose: User Mobility Characterization, Usage Characterization, Human Behavior Modeling
• methodology: The trap log contains the (switch port, MAC address) association when the user is online. However, if a MAC re-appears at the same switch port when it was last online, the trap log may NOT record this information. Hence trap logmust be used in conjunction with session log to discover all association sessions. The file [Mapping] is the mapping between switch (IP, port) and the building code of USC campus. USC campus map is available through university website.
• limitation: WARNING: The trap log alone does NOT contain all user online events! If a user comes online at the same switch port repeatedly, it does NOT create separate trap log for each new online event. Also, the trap log only records the online epoch, but not online duration information of any kind. 

usc/mobilib/trap Trace

• trap_log: Trace of trap logs collected from USC wirelss network during 2005.
• configuration: The trap log contains the (switch port, MAC address) association when the user is online. This log records the approximate location of nodes, since the switch ports correspond to buildings in USC network. However, if a node reappears repeatedly at the same switch port, a new trap entry may not be generated. Hence the trap log is mainly used as an indication of the "last seen" location of the node, and we assume it does not move unless indicated otherwise by a new trap entry.
• format: The fields are: 1. Month 2. Day 3. Time: HH:MM:SS 4. Switch IP 5. Switch port (switch IP + switch port is used to locate the node on USC campus map, the Mapping file is also available online) 6. MAC address
• old_trap_log: Trace of trap logs collected from USC wirelss network during 2003-2005.
• configuration: The trap log contains the (switch port, MAC address) association when the user is online. This log records the approximate location of nodes, since the switch ports correspond to buildings in USC network. However, if a node reappears repeatedly at the same switch port, a new trap entry may not be generated. Hence the trap log is mainly used as an indication of the "last seen" location of the node, and we assume it does not move unless indicated otherwise by a new trap entry.
• format: The fields are: 1. Month 2. Day 3. Time: HH:MM:SS 4. Switch IP 5. Switch port (switch IP + switch port is used to locate the node on USC campus map, the Mapping file is also available online) 6. MAC address

usc/mobilib/association

Association history from USC wirelss network.

• file: trace_processing_code.tgz, USC_duration_trace.tgz, USC_2005_summer.tgz, USC_06spring_trace.tar.gz
• description: this traceset contains "association history" traces for individual MAC addresses, which consist of start times and end times of a MAC associated with various locations.
• measurement purpose: User Mobility Characterization, Usage Characterization, Human Behavior Modeling
• methodology: From the raw traces (session, dhcp, and trap) it is possible to find out user locations (at per switch port granularity, which roughly corresponds to buildings on campus) when they are online. This "association history" trace for individual MAC addresses consists of start times and end times of a MAC associated with various locations. The location granularity is per switch port, roughly corresponding to buildings on campus. There are three files related with generation of association history traces. (1) session file: Records of start/stop of a association session, with the corresponding private IP address. (2) dhcp file: Records of private IPs to MAC address binding. (3) trap file: Records of MAC address showing up at switch ports. The conversion involves getting session durations from (1), then converting the IP address in (1) to MAC address using (2), finally finding the locations of these MAC addresses using (3). The file [Processing code] is the program code we used for trace processing. For more detail about the trace processing, please see [Memo of USC trace processing]. 

usc/mobilib/association Trace

•  duration_log: Trace of association history from USC wirelss network for one month.
• configuration: For the processed trace, we have the association history for each MAC address in a separate file.
• format: The fields in these files are: 1. Start timestamp: The starting time of an association record. The timestamp is defined as the elapsed time since Apr. 1, 2005 in unit of seconds. 2. Location: the building code of the association record. 3. Duration: duration of the association record, in unit of seconds.
• summer_duration_log: Trace of association history from USC wirelss network during 2005 summer.
• configuration: For the processed trace, we have the association history for each MAC address in a separate file. This trace is a longer processed trace for the whole summer. Please note that the summer vacation is from mid-May to mid-Aug for USC, and the WLAN activity significantly reduced during the summer vacation.
• format: The fields in these files are: 1. Start timestamp: The starting time of an association record. The timestamp is defined as the elapsed time since Apr. 1, 2005 in unit of seconds. 2. Location: the building code of the association record. 3. Duration: duration of the association record, in unit of seconds.
• spring_2006_duration_log: Trace of association history from USC wirelss network during Spring 2006.
• configuration: This data set contains 25,481 users that appeared during Jan. 25, 2006 to Apr. 28, 2006. During this time frame, there were 137 unique locations in the trace. Each location roughly corresponds to a building on campus, and it is encoded in the format of IP_port (the actual switch port that controls traffic to/from this location).
• format: The fields in these files are: 1. Start timestamp: The starting time of an association record. The timestamp is defined as the elapsed time since Jan. 1, 2006 in unit of seconds. 2. Location: the format of IP_port (the actual switch port that controls traffic to/from this location). 3. Duration: duration of the association record, in unit of seconds. For more information on the trace format and the processing procedure, please refer to the documents [Memo Format USC06] and [Memo processing USC06].