TCP-UEM: Detectando falhas no enlace mantendo a semântica fim a fim (TCP-UEM: Detecting Link Failure by Keeping End-to-end Semantics)

Renato Fernando Silva Gonçalves (progrenato@yahoo.com.br), Valéria Delisandra Feltrim (valeria.feltrim@uem.br), Luciana Andréia Fondazzi Martimiano (luciana@uem.br)


Universidade Estadual de Maringá
This paper appears in: Revista IEEE América Latina

Publication Date: May 2013
Volume: 11,   Issue: 3 
ISSN: 1548-0992


Abstract:
The evolution of computer networks has happened, in most cases, on the wired networks. However, the appearance of the wireless network, called “revolution wireless”, brought some challenges. The use of the technologies belonging to the wired networks on wireless networks is not appropriate. Some challenges are in the transport layer. The main and default transport protocols known are TCP and UDP. However, these protocols evolved to answer problems mainly found in wired networks. The use of the TCP and its mechanism to avoid congestion on wireless networks introduce important problems, such as, misinterpretation of route failures as congestion, misinterpret link errors as congestion, inefficiency when dealing with contention both internal and external to the node, inefficiency caused by spurious retransmission, poor conservation of energy of the node, among others. Many solutions have been investigated and most of the solutions change the original TCP to solve one or more problems, but not all. Others solutions try to solve the problems designing a new protocol for transport layer. In this paper we present a new TCP scheme, called TCP-UEM, which aims at detecting link failures while maintaining the end-to-end semantic of the original TCP in order to avoid the congestion mechanism to be erroneously executed. The simulations carried out to evaluate the TCP-UEM are described as well as the statistical analysis of the results.

Index Terms:
Transport-protocols, Congestion-Control, Wireless -networks, Wireless-LAN, TCP/IP,   


Documents that cite this document
This function is not implemented yet.


[PDF Full-Text (633)]