Table 5 Comparison of middleware systems for mobile communication
From: A DDS-based middleware for scalable tracking, communication and collaboration of mobile nodes
Aspect | Sales | Solar | DDSS | Revenge | SDDL |
|---|---|---|---|---|---|
Application | Generic middleware | Generic middleware | Generic middleware | News dissemination | Generic middleware |
Communication modes | Pure UDP | Pasty and TCP | Pub/Sub | Pub/Sub | Unicast, Groupcast and Broadcast, Limited form of Pub/Sub on MNs |
Fault-tolerance | No | No | No | Active Replication on fixed nodes, and node failure detection allowing data re-routing | Gateway failure through MH handovers, and MR-UDP resilience to node’s short disconnections and IP Addr changes |
Reliable data delivery to mobile nodes | There is a contact between data producers and consumers | TCP reliability only (not well suited for wireless connection) | Yes | Yes, but no handover support | Yes, MTD service caches non-deliverd messages, and RUDP has internal asks |
Software on the mobile node | Just UDP | TCP stack and Pastry protocol | Lightweight DDS node | DDS node with minimum profile | Just the MR-UDP java Library |
DDS compliance and QoS support | No | No | Yes, also at the mobile nodes | Yes, also at the mobile nodes | Only in the SDDL core but not on the MNs |
Load Balancing | Yes, using a hierarchical (tree) | N/A | N/A | Yes, in the routing substrate | Yes, of the mobile Gateways’load |
Wireless deployment/test | Yes, without wireless disconnection tests | Yes, without wireless disconnection tests | Not mentioned | Deployment in campus Wi-Fi network | In a WAN, but simulated disconnection and IP Address changes |
Number of MNs | N/A | N/A | N/A | 10 source nodes, 10 sink nodes | Several thousands MNs |
Context Updates by each MN | N/A | N/A | N/A | N/A | Yes, ≈1KB sent every 30 seconds |
Total traffic | N/A | N/A | N/A | 1000 news/s | >250 1KB-object/s |