2020
DOI: 10.1109/jiot.2020.2985925
|View full text |Cite
|
Sign up to set email alerts
|

Mobility Management With Session Continuity During Handover in LPWAN

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
16
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
6
1

Relationship

2
5

Authors

Journals

citations
Cited by 15 publications
(16 citation statements)
references
References 31 publications
0
16
0
Order By: Relevance
“…Figure 6 depicts a typical LoRaWAN mobility scenario with several different mobile IoT devices, with particular mobility behaviors and consequently distinct QoS requirements. Moreover, several works [132,133,134,135] have proposed new protocols and mechanisms to provide mobility support for LoRaWAN applications, and we present them in the following subsection.…”
Section: Summary and Open Issuesmentioning
confidence: 99%
See 1 more Smart Citation
“…Figure 6 depicts a typical LoRaWAN mobility scenario with several different mobile IoT devices, with particular mobility behaviors and consequently distinct QoS requirements. Moreover, several works [132,133,134,135] have proposed new protocols and mechanisms to provide mobility support for LoRaWAN applications, and we present them in the following subsection.…”
Section: Summary and Open Issuesmentioning
confidence: 99%
“…Ayoub et al [132] addressed the application session continuity during the end device mobility in LPWANS. The authors developed a mechanism that extended the SCHC scheme [138] to improve network roaming through a rulebased mechanism.…”
Section: Mobility Managementmentioning
confidence: 99%
“…This solution is proposed by Ayoub et al [45,46]. The authors propose a framework to manage end device mobility between different network operators having the same technology, giving a special focus on LoRaWAN technology.…”
Section: Mobility Management With Session Continuity During Handover In Lpwanmentioning
confidence: 99%
“…After investigating [45], the list of care-of-addresses can be received by an attacker, who in his turn can assign these addresses to himself or to the devices under his control and send binding update messages to the visited network without any verification on the message sources that are sent from the same device, namely the attacker. To clarify this, consider the scenario in figure 9, the attacker devices were in their home network with their IPv6 addresses (HoA1, HoAi, HoAn).…”
Section: False Handover Requestmentioning
confidence: 99%
“…Yet, in both works [4], [3], the authors proposed the MSCHC Protocol (Mobile Static Context Header Compression) based on the Static Context Header Compression (SCHC) protocol [2] to handle end-devices mobility. They proposed an enabling solution of session continuity during end-device mobility through a rule based mechanism.…”
Section: Related Workmentioning
confidence: 99%