1e53490e6aa9c2ccde61 · Predictive Handover Mechanism based on Required Time Estimation in Heterogeneous Wireless Networks
Predictive Handover Mechanism based on Required Time Estimation in Heterogeneous Wireless Networks
In most conventional layer 2 triggering approaches, a pre-defined threshold for a specific perspective such as the received signal strength is used. This may cause too late or too early handover executions. In this paper we propose a new predictive
{
"title_en": "Predictive Handover Mechanism based on Required Time Estimation in Heterogeneous Wireless Networks",
"designation": "",
"series": "",
"status": "",
"date": "2008-11-17",
"date_original": "November 17, 2008",
"url": "https://www.nist.gov/publications/predictive-handover-mechanism-based-required-time-estimation-heterogeneous-wireless",
"source": "NIST Publications",
"display_en": "",
"authors_en": "Sang J. Yoo , David E. Cypher , Nada T. Golmie",
"abstract_excerpt_en": "In most conventional layer 2 triggering approaches, a pre-defined threshold for a specific perspective such as the received signal strength is used. This may cause too late or too early handover executions. In this paper we propose a new predictive",
"id": "1e53490e6aa9c2ccde61",
"sources": [
"NIST Publications"
],
"source_records": [
{
"title_en": "Predictive Handover Mechanism based on Required Time Estimation in Heterogeneous Wireless Networks",
"designation": "",
"series": "",
"status": "",
"date": "2008-11-17",
"date_original": "November 17, 2008",
"url": "https://www.nist.gov/publications/predictive-handover-mechanism-based-required-time-estimation-heterogeneous-wireless",
"source": "NIST Publications",
"display_en": "",
"authors_en": "Sang J. Yoo , David E. Cypher , Nada T. Golmie",
"abstract_excerpt_en": "In most conventional layer 2 triggering approaches, a pre-defined threshold for a specific perspective such as the received signal strength is used. This may cause too late or too early handover executions. In this paper we propose a new predictive"
}
],
"translation_state": "none"
}