Please use this identifier to cite or link to this item: http://localhost:80/xmlui/handle/123456789/1810
Full metadata record
DC FieldValueLanguage
dc.contributor.authorMitra, Avik-
dc.contributor.authorSardar, Bhaskar-
dc.contributor.authorSaha, Debashis-
dc.date.accessioned2018-03-15T04:42:02Z-
dc.date.available2018-03-15T04:42:02Z-
dc.date.issued2011-
dc.identifier.urihttp://hdl.handle.net/123456789/1810-
dc.description.abstractProtocols 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.isoenen_US
dc.subjectNEMOen_US
dc.subjectMIPv6en_US
dc.subjectHandoffen_US
dc.subjectPre-fetchingen_US
dc.subjectTuring machineen_US
dc.titleWhy NEMO Protocols Do Not Pre-fetch More Than One CoA?en_US
dc.typeArticleen_US
Appears in Collections:BCA

Files in This Item:
File Description SizeFormat 
Avik-Why-NEMO-Protocols-Do-Not-Pre-fetch-More-Than-One-CoA.pdf246.21 kBAdobe PDFView/Open


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.