2004
DOI: 10.1145/1031483.1031494
|View full text |Cite
|
Sign up to set email alerts
|

Effect of vertical handovers on performance of TCP-friendly rate control

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
34
0

Year Published

2006
2006
2019
2019

Publication Types

Select...
7
2

Relationship

0
9

Authors

Journals

citations
Cited by 74 publications
(34 citation statements)
references
References 42 publications
0
34
0
Order By: Relevance
“…However, TFRC will struggle when network conditions vary rapidly such as when vertical handovers occur, as seen in [35] and [36]. It has also been reported [37], [38] that TFRC may fail to mirror Reno's throughput if certain conditions are observed.…”
Section: Tcp-friendly Rate Control (Tfrc)mentioning
confidence: 98%
“…However, TFRC will struggle when network conditions vary rapidly such as when vertical handovers occur, as seen in [35] and [36]. It has also been reported [37], [38] that TFRC may fail to mirror Reno's throughput if certain conditions are observed.…”
Section: Tcp-friendly Rate Control (Tfrc)mentioning
confidence: 98%
“…However, current mobility management mechanisms make it impossible for the higher layer protocols to take timely corrective actions to cope with the abrupt change. This has led to the introduction of cross-layer enhanced versions, for instance, for TCP [85] and TFRC [86] to improve their performance under vertical handovers. Additionally, the handover decision-making of MIP remains unaware of the requirements of the applications as well as the capabilities of the available ANs without the support for cross-layer signaling.…”
Section: The Purpose Of Cross-layer Information In the Thesismentioning
confidence: 99%
“…One way is to extend TCP, similar to the explicit notification mechanism by setting an Explicit Mobility Notification (EMN) flag [10] and introducing an Explicit Handover Notification bit [11,13] in a specially marked TCP acknowledgement segment, or using a special option in TCP [30]. This mode simplifies some of the inter-layer issues at the CN.…”
Section: Enhancement Of Inter-layer Interaction Between Tcp and Mipv6mentioning
confidence: 99%
“…+T oAR−nAR + T oAR−nAR + T CN−oAR (10) HMIPv6 [27] is another extension to MIPv6 for optimizing the handover latency by introducing a new entity of Mobility Anchor Point (MAP) severing as a local home agent. When the MN moves within the MAP domain (called intra-domain mobility), mobility is handled by the MAP, and the MN only performs the BU procedures (i.e.…”
Section: T Fmipv6 = T Cn−oar + T Cn−oar + T Cn−oarmentioning
confidence: 99%