Please use this identifier to cite or link to this item:
http://localhost:80/xmlui/handle/123456789/1810
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Mitra, Avik | - |
dc.contributor.author | Sardar, Bhaskar | - |
dc.contributor.author | Saha, Debashis | - |
dc.date.accessioned | 2018-03-15T04:42:02Z | - |
dc.date.available | 2018-03-15T04:42:02Z | - |
dc.date.issued | 2011 | - |
dc.identifier.uri | http://hdl.handle.net/123456789/1810 | - |
dc.description.abstract | Protocols for managing network mobility (NEMO) should reduce handoff latency significantly to provide uninterrupted Internet connectivity. Since the path of a high-speed vehicle is predefined in most cases, it could be beneficial for a NEMO protocol to pre-fetch care-of-addresses of the potential future cells. However, the current NEMO protocols either do not use pre-fetching or use it for at most one cell. While investigating this behavior of the NEMO protocols analytically, we find that pre-fetching beyond the next one cell does not necessarily improve the handoff performance even though the future route of the vehicle could be known beforehand. | en_US |
dc.language.iso | en | en_US |
dc.subject | NEMO | en_US |
dc.subject | MIPv6 | en_US |
dc.subject | Handoff | en_US |
dc.subject | Pre-fetching | en_US |
dc.subject | Turing machine | en_US |
dc.title | Why NEMO Protocols Do Not Pre-fetch More Than One CoA? | en_US |
dc.type | Article | en_US |
Appears in Collections: | BCA |
Files in This Item:
File | Description | Size | Format | |
---|---|---|---|---|
Avik-Why-NEMO-Protocols-Do-Not-Pre-fetch-More-Than-One-CoA.pdf | 246.21 kB | Adobe PDF | View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.