26th IEEE International Conference on Distributed Computing Systems Workshops (ICDCSW'06) 2006
DOI: 10.1109/icdcsw.2006.100
|View full text |Cite
|
Sign up to set email alerts
|

SIP-Based Proactive Handoff Management for Session Continuity in the Wireless Internet

Abstract: New challenging deployment scenarios are accommodating limited and heterogeneous portable devices that roam in wired-wireless best-effort networks with session maintenance and continuity requirements. In particular, continuous services, e.g., multimedia streaming, should not experience any interruption while clients roam between different wireless access localities during service provisioning. The paper describes how to exploit the Session Initiation Protocol (SIP) to build a middleware for session continuity,… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2007
2007
2014
2014

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 9 publications
(1 citation statement)
references
References 22 publications
0
1
0
Order By: Relevance
“…[7] describes a softhandover solution where packets are duplicated, while [8] describes a hard-handover where packets are buffered to avoid packet loss during handover. In [7] and [8], the use of back-toback user agent (B2BUA) is recognized as an effective way to provide better and faster handoff, and both solutions require deployment of entities in each domain or subnet that interact to support the handover. Solutions described in [6] and [7] require that two communication interfaces can operate simultaneously.…”
Section: Background and Related Workmentioning
confidence: 99%
“…[7] describes a softhandover solution where packets are duplicated, while [8] describes a hard-handover where packets are buffered to avoid packet loss during handover. In [7] and [8], the use of back-toback user agent (B2BUA) is recognized as an effective way to provide better and faster handoff, and both solutions require deployment of entities in each domain or subnet that interact to support the handover. Solutions described in [6] and [7] require that two communication interfaces can operate simultaneously.…”
Section: Background and Related Workmentioning
confidence: 99%