2004
DOI: 10.1023/b:mone.0000031605.84447.1d
|View full text |Cite
|
Sign up to set email alerts
|

A Two-Tier Heterogeneous Mobile Ad Hoc Network Architecture and Its Load-Balance Routing Problem

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
37
0

Year Published

2007
2007
2017
2017

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 59 publications
(37 citation statements)
references
References 19 publications
0
37
0
Order By: Relevance
“…Furthermore, route flapping [29] is a common issue. Most solutions in this category model a gateway's load using different gateway parameters, such as total traffic [30], residual capacity [31]- [33], number of active flows [17], average queue length [34], and number of registered mobile nodes [35].…”
Section: B Gateway Load Balancingmentioning
confidence: 99%
“…Furthermore, route flapping [29] is a common issue. Most solutions in this category model a gateway's load using different gateway parameters, such as total traffic [30], residual capacity [31]- [33], number of active flows [17], average queue length [34], and number of registered mobile nodes [35].…”
Section: B Gateway Load Balancingmentioning
confidence: 99%
“…In [4] a two layer heterogeneous network has been proposed. It provides the internet access to the lower layer nodes but it does not provide communication between lower layer nodes.…”
Section: Related Workmentioning
confidence: 99%
“…Most of these can suffer from route flapping or poor performance for not taking contention into account. From proposed algorithms in [10], DA and CA just consider their load and don t take their distance to gateway nodes as well as interference with other flows into account, so perform very poorly. NGW and MLI associate each node to its nearest gateway which can result in gateways that are overloaded while others are under-utilized [10].…”
Section: Introductionmentioning
confidence: 99%
“…From proposed algorithms in [10], DA and CA just consider their load and don t take their distance to gateway nodes as well as interference with other flows into account, so perform very poorly. NGW and MLI associate each node to its nearest gateway which can result in gateways that are overloaded while others are under-utilized [10]. With MLI, every time that there is an imbalance between gateways, border nodes switch to another domain to even the load of the domains so makes high switching overhead.…”
Section: Introductionmentioning
confidence: 99%