The network traffic files used by the simulator are all of a standard packet capture format commonly known as pcap, as defined in file pcap.h (version 2.4) of libpcap. See http://wiki.wireshark.org/Development/LibpcapFileFormat . Usually the files have been captured at the endpoints of the network at client devices. These files are used as interfering traffic input to the simulation model.
The following types of streams are included in the standard test cases:
These files have been anonymously captured by a variety of researchers and from a variety of sources as real examples of representative types of packet traffic. In general, the files are a reflection of the traffic patterns observed and have had the payloads stripped to protect the privacy and rights of the actual content as well as to keep the overall file size small. Note that even though the traffic source files omit the payloads, size information is maintained so that the full traffic is modeled by the simulation. Pcap files with payloads can be used as test streams or interfering streams, since the simulator does pass payload data.
In addition to payload stripping, the pcap files have had a number of processing steps:
Flow separation: The captured files are split into upstream (toward the core) and downstream (toward the client endpoint) files for simulation.
Bandwidth analysis: The files are analyzed as to their overall and average bandwidth over finite time periods. As reference files, the microscopic and macroscopic bandwidth characteristics must be understood so that they can be applied reasonably to the various simulation test cases. In particular, the bandwidth characteristics of the files are highly dependent on factors such as the overall bandwidth capabilities and rate limitations of the network path, and the behavior and rate adaptation of higher layer network protocols.
Smoothing: At a microscopic level, bandwidth analysis of some pcap files reveals that there are microbursts. A potential problem with these microbursts is that the instantaneous bandwidth requirement can overwhelm link or memory capacities of the scenario under test. This can be alleviated either through external smoothing of the file or by the rate shaping parameters in the simulation configuration file.
Bandwidth scaling: The standard pcap files are specific captures intended to be representative of network usage. Since they are generic in nature, playback into the simulator is made by bandwidth scaling. This is accomplished by temporal dilation: playback of packets by a constant scale factor, faster or slower, achieves the desired network usage.
6.4.1.1.1.3 describes the standard pcap files in detail, and includes the files as an electronic attachment. The average bandwidth of one example (using a five second non-overlapping window) is plotted in Figure .
Table lists the inputs to the simulation. The core-to-LAN network topology is assumed. One access technology (DSL or GPON) is selected. There are parameters for each network element and for each pcap file used as an interfering traffic stream.
Traffic flows are assigned a priority that is essential in practical access networks to ensure that higher priority traffic from managed services is carried in preference to lower priority traffic. The simulator has 7 priority levels and no per-class bandwidth reservation. The simulation test cases are set as follows:
1: (highest priority) Managed voice traffic
2: Managed IPTV-type video traffic
3 - 6: Unused
7: (lowest priority) Best effort, OTT video, VoIP/FoIP, peer-to-peer