DOCSLIB.ORG

Multipath TCP and Measuring End- To-End TCP Throughput

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Multipath TCP and Measuring End- To-End TCP Throughput Master of Science in electrical engineering with emphasis on Telecommunication systems JUNE 2018 Multipath TCP and Measuring end- to-end TCP Throughput Measuring TCP Metrics and ways to improve TCP Throughput performance Vineesha Sana Faculty of Computing , Blekinge Institute of Technology , SE-371 79 Karlskrona Sweden This thesis is submitted to the Faculty of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering with emphasis on Telecommunication Systems. The thesis is equivalent to 20 weeks of full time studies. Contact Information: Author: Vineesha Sana E-mail: [email protected], [email protected] External Advisor: Managing Director, Rao. Tummalapalli Seneca Global Hyderabad, India University advisor: Dr. Adrian Popescu Department of Communications Faculty of Computing Internet : www.bth.se Blekinge Institute of Technology Phone : +46 455 38 50 00 SE-371 79 Karlskrona, Sweden Fax : +46 455 38 50 57 ABSTRACT Internet applications make use of the services provided by a transport protocol, such as TCP (a reliable, in-order stream protocol). We use the term Transport Service to mean the end- toend service provided to application by the transport layer. That service can only be provided correctly if information about the intended usage is supplied from the application. The application may determine this information at the design time, compile time, or run time, and it may include guidance on whether a feature is required, a preference by the application, or something in between. Multipath TCP (MPTCP) adds the capability of using multiple paths to a regular TCP session. Even though it is designed to be totally backward compatible to applications. The data transport differs compared to regular TCP, and there are several additional degrees of freedom that the particular application may want to exploit. Multipath TCP is particularly useful in the context of wireless networks using both Wi-Fi and a mobile network is a typical use case. In addition to the gains in throughput from inverse multiplexing, links may be added or dropped as the user moves in or out of coverage without disrupting the end-to-end TCP connection. The problem of link handover is thus solved by abstraction in the transport layer, without any special mechanisms at the network or link level. Handover functionality can then be implemented at the endpoints without requiring special functionality in the sub-networks according to the Internet's end-to-end principle. Multipath TCP can balance a single TCP connection across multiple interfaces and reach very high throughput. Keywords: Congestion control, end-to-end, IP network, TCP performance, Throughput ACKNOWLEDGEMENTS A special note of thanks to my supervisor Dr. Adrian Popescu for his excellent guidance and reviews during the master thesis work. His great ideas and suggestions made me work his patience mean a lot throughout the whole project. I am grateful to thank all of my company staff for their extreme help and valuable suggestions at Seneca global, Hyderabad, India for the great support. I am happy to express that I have encouragement and positive support from my parents all the time during my work. I would like to thank my thesis partner for great help during our work. Finally, I am very much thankful to God who is the superior of everything, who guides and learns me new all the time. LIST OF FIGURES 3.1 Path MTU in TCP 3.2 Round-Trip-Time and Bottleneck-Bandwidth 3.2.1Bandwidth Line Utilization and Round-Trip-Time 3.2.1 Round-Trip-Time Measurements 3.2.2 Measuring Bandwidth Thresholds in TCP 3.7 TCP Throughput Test of TCP Performance LIST OF FIGURES and GRAPHS Figures and Graphs 5: - 5.1 TCP Throughput Relationship Graph 5.2 TCP Congestion Window with Number of Transmissions 5.3 Threshold Graph of Slow Start and Congestion Avoidance 5.4 Throughput Connections of Full Bandwidth 5.5 TCP Throughput Graph with Packet Loss 5.6 Throughput Latency and Utilization 5.7 MPTCP Networks Simple Case from Client-Server 6.1Existing Layers in MPTCP ACRONYMS TCP Transfer Control Protocol MPTCP Multipath Transfer Control Protocol CA Congestion Avoidance RTT Round-Trip-Time BDP Buffer Delay Percentage BB Bottleneck-Bandwidth MTU Maximum Transmission Unit UDP User Datagram Protocol HTTP Hyper Text Transfer Protocol CW Congestion Window IP Internet Protocol Contents 1 INTRODUCTION .................................................................................................................. 2 1.1 Brief Introduction about Seneca Global ...................................................................... 2 1.2 TCP Throughput .......................................................................................................... 2 1.3 Terminology ................................................................................................................. 3 1.4 Problem Statement ...................................................................................................... 5 1.5 Research Questions ..................................................................................................... 6 1.6 Scope and Goals .......................................................................................................... 6 1.7 Split of work͙͙͙͙͙͙͙͙͙͙͙͙ ͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙͙.7 2 RELATED WORK ............................................................................................................. 8 3 METHODOLOGY ............................................................................................................. 12 3.1 Path MTU (Maximum Transmission Unit) ............................................................... 12 3.2 Round-Trip-Time(RTT) and Bottleneck Bandwidth ................................................ 14 3.2.1 Measuring Round-Trip-Time (RTT) .................................................................. 14 3.2.2 Measuring Bottleneck-Bandwidth (BB) ............................................................ 16 3.3 TCP Throughput Measurements ............................................................................... 19 3.4 TCP Metrics .............................................................................................................. 20 3.5 TCP Efficiency .......................................................................................................... 21 3.6 Buffer Delay Percentage ........................................................................................... 22 3.7 TCP Throughput Test ................................................................................................ 23 4 Validation of MPTCP ....................................................................................................... 25 5 Analysis and Results ......................................................................................................... 27 Multiple Transmission Control Protocol Connections ........................................................ 27 Results Simplification ......................................................................................................... 28 1 6 Summary and Conclusion ................................................................................................. 37 6.1 Summary ................................................................................................................... 37 6.2 Conclusion ................................................................................................................. 40 7 Future Work ...................................................................................................................... 41 8 REFERENCES ................................................................................................................. 43 1 INTRODUCTION In this document we describe a practical methodology for measuring endto-end TCP Throughput in a managed IP network and delivery of video on protocol issues related to application and transport layers in MPTCP. Section 1.1 deals with a brief introduction about TCP Throughput Measurements. Section1.2 deals with the terminology of TCP and Throughput. Section1.3 deals with basic terminology terms that used in this thesis work. Section1.4 deals with the problem statement of the project area i.e. challenges and difficulties with TCP Throughput. Section1.5 deals with the methods for evaluation used to solve the research questions. Section1.6 deals with the scope and goals of the project. 1.1 Brief Introduction about Seneca Global Ed Szofer, Rao Tummalapalli and Mani Swami Nathan founded Seneca Global in 2007. All three senior executives had worked together at companies where they had significant success, including: Wittman-Hart (where Ed was President and COO), Divine Interventures (where Rao was Managing Director of off-shore development), and Alliance Consulting. Seneca Global is the culmination of years of IT and leadership experience, resulting in an 2 unmatched service model for Seneca Global clients. Seneca Global began with two office locations: a management, sales and delivery center in Chicago and a software development and testing center in Hyderabad, India. In 2014, we added an office in Hartford, Connecticut. Since our founding in 2007, we have grown to over 300 professionals and, thanks to our unique model, our growth is accelerating as we continue to serve our clients, associates and communities. The IT landscape has never stopped evolving over the years and it never will, either.
Load more

Recommended publications
  • Encoding a Tcp Offload Engine Within
    (19) TZZ__ _T (11) EP 1 719 276 B1 (12) EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention (51) Int Cl.: of the grant of the patent: H04L 29/06 (2006.01) H04L 29/08 (2006.01) 05.10.2016 Bulletin 2016/40 (86) International application number: (21) Application number: 05713673.1 PCT/US2005/004941 (22) Date of filing: 16.02.2005 (87) International publication number: WO 2005/091826 (06.10.2005 Gazette 2005/40) (54) ENCODING A TCP OFFLOAD ENGINE WITHIN FCP CODIERUNG EINER TCP-OFFLOAD-ENGINE MIT FCP CODAGE D’UN MOTEUR DE DECHARGEMENT DE PROTOCOLE DE COMMANDE DE TRANSMISSION A L’INTERIEUR D’UN FCP (84) Designated Contracting States: • DEGROOTE, Stephen AT BE BG CH CY CZ DE DK EE ES FI FR GB GR Maple Grove, MN 55311 (US) HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR • BASAVAIAH, Murali Sunnyvale, CA 94087 (US) (30) Priority: 27.02.2004 US 548766 P • PARTHASARATHY, Anand 29.04.2004 US 836368 Fremont, CA 94555 (US) (43) Date of publication of application: (74) Representative: Kazi, Ilya et al 08.11.2006 Bulletin 2006/45 Mathys & Squire LLP The Shard (73) Proprietor: Cisco Technology, Inc. 32 London Bridge Street San Jose, CA 95134 (US) London SE1 9SG (GB) (72) Inventors: (56) References cited: • KUIK, Timothy US-A1- 2001 037 406 US-A1- 2001 049 740 Lino Lakes, MN 55014 (US) US-A1- 2002 002 625 US-A1- 2003 051 135 • THOMPSON, David US-A1- 2004 030 668 US-B1- 6 697 846 Rogers, MN 55374 (US) Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations.
    [Show full text]
  • 1 in the United States District Court for The
    Case 2:16-cv-00695 Document 1 Filed 06/30/16 Page 1 of 107 PageID #: 1 IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF TEXAS MARSHALL DIVISION ALACRITECH, INC., a California corporation, Plaintiff, v. Case No. 2:16-cv-695 DELL INC., a Delaware corporation, Jury Trial Demanded Defendant. COMPLAINT FOR PATENT INFRINGEMENT In this action for patent infringement under 35 U.S.C. § 271, Plaintiff Alacritech, Inc. ("Alacritech"), by and through its undersigned counsel, complains and alleges as follows against Defendant Dell Inc. ("Dell"), based on Alacritech's own personal knowledge with respect to its own actions and upon information and belief with respect to others' actions: THE PARTIES 1. Alacritech is a California corporation with its principal place of business at P.O. Box 20307, San Jose, California 95160. 2. Dell is a Delaware corporation with its principal place of business at One Dell Way, Round Rock, Texas 78682. NATURE OF THE ACTION 3. This is a civil action for patent infringement arising under the patent laws of the United States, 35 U.S.C. § 1, et seq. 4. Dell has infringed and continues to infringe, has contributed to and continues to contribute to the infringement of, and has actively induced and continues to actively induce others to infringe the following Alacritech patents: U.S. Patent Numbers 7,124,205; 7,237,036; 1 Case 2:16-cv-00695 Document 1 Filed 06/30/16 Page 2 of 107 PageID #: 2 7,337,241; 7,673,072; 7,945,699; 8,131,880; 8,805,948; and 9,055,104 (collectively, the "Asserted Patents").
    [Show full text]
  • Ciena Telecom Glossary.Pdf
    Telecom Glossary edited by Erin Malone Chris Janson 1st edition Publisher Acknowledgement: This is the first edition of this book. Please notify us of any acronyms we may have missed by submitting them via the form at www.ciena.com/glossary. We will be happy to in- clude them in further editions of “The Acronyms Guide”. For additional information on Ciena’s Carrier Ethernet or Optical Communications Certification programs please contact [email protected]. Table of Contents A .......................................1 B .......................................2 C .......................................3 D .......................................5 E .......................................6 F........................................6 G .......................................7 H .......................................8 I .........................................8 J ........................................9 K .......................................9 L ........................................9 M ....................................10 N .....................................11 O.....................................12 P .....................................13 Q.....................................14 R .....................................15 S......................................16 T .....................................17 U .....................................18 V .....................................18 W ....................................19 X .....................................19 A Add/Drop Allows optical wavelengths to be added or dropped at
    [Show full text]
  • Qlogic Bcm57xx and Bcm57xxx
    User’s Guide Ethernet iSCSI Adapters and Ethernet FCoE Adapters QLogic BCM57xx and BCM57xxx Third party information brought to BC0054508-00 J you courtesy of Dell. User’s Guide—Ethernet iSCSI Adapters and Ethernet FCoE Adapters QLogic BCM57xx and BCM57xxx Document Revision History Revision A, February 18, 2015 Revision B, July 29, 2015 Revision C, March 24, 2016 Revision D, April 8, 2016 Revision E, February 2, 2017 Revision F, August 25, 2017 Revision G, December 19, 2017 Revision H, March 15, 2018 Revision J, April 13, 2018 Changes Sections Affected Changed Step 1. “Downloading Documents” on page xxiii Added support for NPIV (via Fibre Channel - Link “FCoE” on page 4 Services specification) on Linux and Windows. In the first paragraph, clarified the last sentence to “Configuring Teaming in Windows Server” on indicate that “Windows Server 2016 and later do page 7 not support QLogic’s QLASP teaming driver.” In the NOTE, clarified the last sentence to indicate “QLASP Overview” on page 7 that “Windows Server 2016 does not support QLogic’s QLASP teaming driver…” In the NOTE, clarified the first and second sen- “Link Aggregation (802.3ad)” on page 9 tences: “The static and dynamic Link Aggregation (switch dependent) team type is not supported on ports with NIC partitioning (NPAR) mode enabled or iSCSI-offload enabled. Some switches support FCoE-offload in dynamic LACP teaming mode.” Added RHEL 6.9, 7.4, 7.5, SLES12 SP3 to the list “Linux” on page 18 of supported OSs. Added ESXi 6.0 U3, ESXi 6.5 U1, ESXi 6.5 U2, “VMware ESXi” on page 19 ESXi 6.7 to the list of supported OSs.
    [Show full text]
  • A FORMAL APPROACH to PROTOCOL OFFLOAD for WEB SERVERS By
    A FORMAL APPROACH TO PROTOCOL OFFLOAD FOR WEB SERVERS By Juan Manuel Sol¶a-Sloan A thesis submitted in partial ful¯llment of the requirements for the degree of DOCTOR OF PHILOSOPHY in COMPUTING INFORMATION SCIENCE AND ENGINEERING UNIVERSITY OF PUERTO RICO MAYAGUEZÄ CAMPUS May, 2009 Approved by: Nayda G. Santiago-Santiago, Ph.D Date Member, Graduate Committee Manuel Rodr¶³guez-Mart¶³nez,Ph.D Date Member, Graduate Committee Domingo Rodr¶³guez-Rodr¶³guez,Ph.D Date Member, Graduate Committee Isidoro Couvertier-Reyes, Ph.D Date President, Graduate Committee Dorial Castellanos-Rodr¶³guez,Ph.D Date Representative of Graduate Studies Nestor Rodr¶³guez-Rivera, Ph.D Date Chairperson of the Department ABSTRACT The use of networks as computational tools has been fundamental in Com- puter Information Science and Engineering research. As computers have evolved, the demands for faster data transmission have incremented. Protocol processing and application processing compete for a share of CPU time when the underlying network evolves. O²oad Engines have been proposed as ways to alleviate the CPU of the host of the cost of processing the protocols used in an end-to-end communication. These engines are proposed as part of the network interface hardware or as a component near or even inside the CPU. However, an increase in performance is not guaranteed after the installation of this type of engine. The operating system of the host is capable of processing the protocols faster than the engine in some particular occasions. A probabilistic model that estimates the performance metrics of utilization and delay, before and after extracting the protocol processing from the CPU of the host is presented in this document.
    [Show full text]
  • Fastlinq 41000 Series
    Marvell® FastLinQ® 41000 Series Adapters Converged Network Adapters and Intelligent Ethernet Adapters User’s Guide Doc No. AH0054601-00 Rev. M June 15, 2021 Cover Marvell FastLinQ® 41000 Series Adapters User’s Guide THIS DOCUMENT AND THE INFORMATION FURNISHED IN THIS DOCUMENT ARE PROVIDED “AS IS” WITHOUT ANY WARRANTY. MARVELL AND ITS AFFILIATES EXPRESSLY DISCLAIM AND MAKE NO WARRANTIES OR GUARANTEES, WHETHER EXPRESS, ORAL, IMPLIED, STATUTORY, ARISING BY OPERATION OF LAW, OR AS A RESULT OF USAGE OF TRADE, COURSE OF DEALING, OR COURSE OF PERFORMANCE, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. This document, including any software or firmware referenced in this document, is owned by Marvell or Marvell's licensors, and is protected by intellectual property laws. No license, express or implied, to any Marvell intellectual property rights is granted by this document. The information furnished in this document is provided for reference purposes only for use with Marvell products. It is the user's own responsibility to design or build products with this information. Marvell products are not authorized for use as critical components in medical devices, military systems, life or critical support devices, or related systems. Marvell is not liable, in whole or in part, and the user will indemnify and hold Marvell harmless for any claim, damage, or other liability related to any such use of Marvell products. Marvell assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use.
    [Show full text]
  • Emulex Drivers Version 10.6 for Windows User Manual
    Emulex Drivers Version 10.6 for Windows User Manual P011382-01A Rev. A Connect • Monitor • Manage 2 Copyright © 2003-2015 Emulex. All rights reserved worldwide. No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex. Information furnished by Emulex is believed to be accurate and reliable. However, no responsibility is assumed by Emulex for its use; or for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent, copyright or related rights of Emulex. Emulex, the Emulex logo, Emulex BladeEngine, Emulex InSpeed, Emulex LightPulse, Emulex OneCommand, Emulex OneConnect, and SLI are registered trademarks, and Emulex Advanced-8, Emulex Connect, Emulex CrossLink, Emulex Engine, Emulex Edge, Emulex ExpressLane, Emulex GreenState, Network Xceleration, Emulex OneCore, Emulex Pilot, Emulex SURF, Emulex Universal Multi-Channel, Emulex vEngine, Emulex Virtual Fabric, Emulex Virtual Network Exceleration, Emulex vPath, Emulex vScale, AutoPilot, AutoPilot Installer, and BlockGuard are trademarks, of Emulex. All other brands or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations. Emulex provides this manual "as is" without any warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Emulex may make improvements and changes to the product described in this manual at any time and without any notice. Emulex assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties that may result.
    [Show full text]