Wiki » History » Version 35
Version 34 (MOURA, Ninon, 03/16/2016 07:19 PM) → Version 35/45 (MOURA, Ninon, 03/16/2016 07:22 PM)
h1. Improving TCP over satellite
h2. [[Tasks list]]
h2. Introduction
When deploying terrestrial networks and particularly the internet, the need to ensure integrity in data transfer combined with the wish to divide fairly a bandwidth between users lead to the born of TCP, a well known transport protocol. It was developped for terrestrial networks where the delay between routers is few milliseconds and the transmission quality is quite constant. But when we want to use it for geostationary satellite links the inevitable delay of 250ms for a single hop become a problem to have good throughput.
Considering the huge number of terminals using TCP, an overhaul of the protocol is not conceivable. However we can have clever solutions to skirt the problem and improve the performances. In this project the solution we use is to break the TCP chain in isolating the satellite link with PEP (Performance Enhancing Proxy), which makes virtually transparent the use of a satellite link at the TCP level.
This report will first address the state of the art of TCP over a satellite link, then the network architecture and the equipment configuration will be issued. Finally, simulations and results about PEPsal will be assessed.
h2. [[I - State of the art]]
h3. [[1. Specifications of a satellite link]]
h3. [[2. TCP improvements over a satellite link]]
h3. [[3. PEP TCP]]
h3. [[4. PEPsal]]
h2. [[II - Network architecture and equipment configuration]]
h3. [[1. Network architecture]]
h3. [[2. Modem MDM 6000]]
h3. [[3. PC Engines and PEPsal]]
h2. [[III - Simulation and results]]
h3. [[1. Simulation [[Simulation limitations]]
h3. [[2. Simulation [[Simulation programm]]
h3. [[3. Simulation [[Simulation without satellite link]]
h3. [[4. Simulation [[Simulation with faked satellite link]]
h2. [[References]]
h2. [[List of figures]]
h2. [[Tasks list]]
h2. Introduction
When deploying terrestrial networks and particularly the internet, the need to ensure integrity in data transfer combined with the wish to divide fairly a bandwidth between users lead to the born of TCP, a well known transport protocol. It was developped for terrestrial networks where the delay between routers is few milliseconds and the transmission quality is quite constant. But when we want to use it for geostationary satellite links the inevitable delay of 250ms for a single hop become a problem to have good throughput.
Considering the huge number of terminals using TCP, an overhaul of the protocol is not conceivable. However we can have clever solutions to skirt the problem and improve the performances. In this project the solution we use is to break the TCP chain in isolating the satellite link with PEP (Performance Enhancing Proxy), which makes virtually transparent the use of a satellite link at the TCP level.
This report will first address the state of the art of TCP over a satellite link, then the network architecture and the equipment configuration will be issued. Finally, simulations and results about PEPsal will be assessed.
h2. [[I - State of the art]]
h3. [[1. Specifications of a satellite link]]
h3. [[2. TCP improvements over a satellite link]]
h3. [[3. PEP TCP]]
h3. [[4. PEPsal]]
h2. [[II - Network architecture and equipment configuration]]
h3. [[1. Network architecture]]
h3. [[2. Modem MDM 6000]]
h3. [[3. PC Engines and PEPsal]]
h2. [[III - Simulation and results]]
h3. [[1. Simulation [[Simulation limitations]]
h3. [[2. Simulation [[Simulation programm]]
h3. [[3. Simulation [[Simulation without satellite link]]
h3. [[4. Simulation [[Simulation with faked satellite link]]
h2. [[References]]
h2. [[List of figures]]