The sender application sends 5000 bundles of 1 MByte, which are then slowly forwarded to the bus, the gateway, and finally the receiver application as contact opportunities arise.
We choose to deploy the Village Example on a 4-host setup, with one host per DTN node (kiosk, bus, and gateway) plus the KauNet host.
Similarly, a bandwidth pattern BGW.bw is shared on pipes 101 and 102, while the contact pattern BGW.trg for bus and gateway is loaded only on pipe 101: ipfw add 1 pipe 1 ip from 10.0.1.1 to 10.0.2.1 in.
A simple solution to reduce the delay in bundle delivery would of course be to allow the bus and gateway a longer contact time, thus reducing the impact of the bottleneck link.
The steps observed in Figure 8 closely match the no-contact periods between the bus and the gateway, that is, the receiver.
The link between the bus and the gateway is shared by all kiosks on their paths from sender to receiver and becomes a bottleneck.
We measure how many bundles are delivered to the gateway for every bus round-trip, over 30 rounds.
Improving the "gateway" rail and bus stations is seen as key to the wider ambitions for an enterprise zone in the centre of Cardiff.
It also connects to devices attached to the CAN-Bus, and finally the car gateway (e.g., a dedicated light weighted embedded car PC) that can serve as the hardware platform (see Figure 2).
Other nodes (e.g., hosts running applications, cameras, gateways to the CAN bus,...) are possibly connected to the MRs/ARs through an ITS station internal network.
When we move quickly through crowded travel gateways such as airports, bus and train stations, or even walk down a busy urban street, we typically miss the details and manufactured or natural beauty of our daily surroundings.
