210 likes | 221 Views
Research on evaluating TCP/UDP protocols performance in O2 and TME GPRS networks focusing on reliability, delay, and bandwidth, includes measurement setup, procedures, and conclusions.
E N D
MobiHealth Communication Infrastructure Performance Analysis of the MobiHealth E2E communication link MobiHealth WP3 meeting January 30, 2003 Katarzyna Wac, University of Twente email: mhealth@mobihealth.org Internet: www.mobihealth.org
Presentation Layout 1. Performance analysis of TCP and UDP transport protocols over GPRS Network • Research issues • Measurement setup • Measurement results 2. State of the Measurement Strategy • Research issues • Proposed measurement strategy • Measurement assumptions
1. Performance analysis of TCP and UDP transport protocols over GPRS Network Research issues • Evaluation of TCP/UDP protocols performance in two GPRS networks: • O2 - The Netherlands • TME - Spain Performance objectives are: • Available network bandwidth (& coding schemes, time slots) • Achieved Reliability (data loss) • Total delay (& Round Trip Delay sensitivity)
Segments of E2E communication link …and particularly whenapplying 2.5G technology - GPRS
(555 kB) Nokia D211 card Measurement setup End-to-End communication model (Win2000) (Linux OS)
Measurement procedures TCP protocol • No control on packet rate (on the server side) applied • (e.g. control on: #packets/sec, #samples/packet). • Control on packet rate applied • Packet size derived from the available network • bandwidth and from the known data rate produced by the sensor system front-end (TMSI): 64 samples/sec, 30B/sample UDP protocol • Procedures as above • Additionally, every packet has 4B sequence number – • control on: out-of-sequence packet delivery, • data loss rate • At the client side: function of data buffering, re-ordering and insertion of lost packets. • Bandwidth = [ (30B / sample * #samples / packet) + TCP/UDP_header] * #packets / second * 8 bits [kbps]
Measurement results GPRS “hick-up”
Viewer Application – TCP protocol Measurement case with and without control on packet rate TCP parameters : 5 samples/packet, 10 packets/second
Viewer Application – UDP protocol Measurement case without the control on packet rate UDP parameters : 5 samples/packet, 10 packets/second
Viewer Application – UDP protocol (cont.) Measurement case with the control on packet rate UDP parameters : 16 samples/packet, 3 packets/second
Conclusion on measurement results TCP vs. UDP performance • TCPsuitable when no control on packet rate applied • UDPperforms better with the control on the packet rate (low data loss, shorter time of transmission) • GPRS provides reliable data link service -> UDP loss occurred on Internet or Enterprise Network • MobiHealth recommendation: • - UDP for the BAN monitoring data (if data loss allowed) • - TCP for the control data to BAN O2 vs. TME GPRS Network TME GPRS network has better performance than O2 GPRS network. Possible reasons: Laboratory & Public network, Voice priority in O2 network
2. State of measurement strategy Layered structure of the m-health system
Proposed measurement strategy High-level abstraction of the m-health system …and its decomposition Traffic Sink (TS) Intermediate MeasurementPoint
Proposed measurement strategy (cont.) Traffic Sink (TS) SGSN Traffic Sink (TS)
Proposed measurement strategy (cont.) Characteristics of the link that will be measured • “good put” experienced by end-user • & throughput (gross bandwidth – with overhead) • Round Trip Delay • Data Loss • Packet Size
Measurement assumptions • Protocols: • Transport Layer: TCP/UDP/W-TCP Network Layer: IP Data Link Layer: GPRS, UMTS • Measurements are done in the following directions Terminal -> Network and Network -> Terminal • Measurements are done in the following positions: Stable position & mobility (80-120 km/h) • Investigation of the real coverage of network will take place • Iterative process: Step-by-step derivation of system’s performance characteristics • High number of measurements (samples) to guarantee • the statistical correctness