A multi path routing protocol with efficient energy consumption in IoT applications real time traffic

Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are pa...
Ausführliche Beschreibung

Gespeichert in:

Autor*in:	Abujassar, Radwan S. [verfasserIn]

Format:	E-Artikel
Sprache:	Englisch

Erschienen:	2024

Schlagwörter:	Network performance stability using the intelligent routing protocol (nPSIR) Internet of Things (IoT) HEAD nodes (HN) Request packets for creative and investigation (RPcI) WSN

Anmerkung:	© The Author(s) 2024

Übergeordnetes Werk:	Enthalten in: EURASIP journal on wireless communications and networking - Springer International Publishing, 2004, 2024(2024), 1 vom: 08. Juni
Übergeordnetes Werk:	volume:2024 ; year:2024 ; number:1 ; day:08 ; month:06

Links:	Volltext

DOI / URN:	10.1186/s13638-024-02377-1

Katalog-ID:	SPR056170718

Internformat


LEADER	01000naa a22002652 4500
001	SPR056170718
003	DE-627
005	20240609064640.0
007	cr uuu---uuuuu
008	240609s2024 xx \|\|\|\|\|o 00\| \|\|eng c
024	7		\|a 10.1186/s13638-024-02377-1 \|2 doi
035			\|a (DE-627)SPR056170718
035			\|a (SPR)s13638-024-02377-1-e
040			\|a DE-627 \|b ger \|c DE-627 \|e rakwb
041			\|a eng
082	0	4	\|a 620 \|a 004 \|q VZ
084			\|a 53.74 \|2 bkl
084			\|a 54.32 \|2 bkl
100	1		\|a Abujassar, Radwan S. \|e verfasserin \|0 (orcid)0000-0002-4572-5588 \|4 aut
245	1	0	\|a A multi path routing protocol with efficient energy consumption in IoT applications real time traffic
264		1	\|c 2024
336			\|a Text \|b txt \|2 rdacontent
337			\|a Computermedien \|b c \|2 rdamedia
338			\|a Online-Ressource \|b cr \|2 rdacarrier
500			\|a © The Author(s) 2024
520			\|a Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility.
650		4	\|a Network performance stability using the intelligent routing protocol (nPSIR) \|7 (dpeaa)DE-He213
650		4	\|a Internet of Things (IoT) \|7 (dpeaa)DE-He213
650		4	\|a HEAD nodes (HN) \|7 (dpeaa)DE-He213
650		4	\|a Request packets for creative and investigation (RPcI) \|7 (dpeaa)DE-He213
650		4	\|a WSN \|7 (dpeaa)DE-He213
773	0	8	\|i Enthalten in \|t EURASIP journal on wireless communications and networking \|d Springer International Publishing, 2004 \|g 2024(2024), 1 vom: 08. Juni \|w (DE-627)47265151X \|w (DE-600)2168613-0 \|x 1687-1499 \|7 nnns
773	1	8	\|g volume:2024 \|g year:2024 \|g number:1 \|g day:08 \|g month:06
856	4	0	\|u https://dx.doi.org/10.1186/s13638-024-02377-1 \|m X:SPRINGER \|x Resolving-System \|z kostenfrei \|3 Volltext
912			\|a SYSFLAG_0
912			\|a GBV_SPRINGER
912			\|a GBV_ILN_11
912			\|a GBV_ILN_20
912			\|a GBV_ILN_22
912			\|a GBV_ILN_23
912			\|a GBV_ILN_24
912			\|a GBV_ILN_39
912			\|a GBV_ILN_40
912			\|a GBV_ILN_60
912			\|a GBV_ILN_62
912			\|a GBV_ILN_63
912			\|a GBV_ILN_65
912			\|a GBV_ILN_69
912			\|a GBV_ILN_70
912			\|a GBV_ILN_73
912			\|a GBV_ILN_95
912			\|a GBV_ILN_105
912			\|a GBV_ILN_110
912			\|a GBV_ILN_151
912			\|a GBV_ILN_161
912			\|a GBV_ILN_170
912			\|a GBV_ILN_206
912			\|a GBV_ILN_213
912			\|a GBV_ILN_230
912			\|a GBV_ILN_285
912			\|a GBV_ILN_293
912			\|a GBV_ILN_370
912			\|a GBV_ILN_602
912			\|a GBV_ILN_702
912			\|a GBV_ILN_2001
912			\|a GBV_ILN_2003
912			\|a GBV_ILN_2005
912			\|a GBV_ILN_2006
912			\|a GBV_ILN_2008
912			\|a GBV_ILN_2009
912			\|a GBV_ILN_2010
912			\|a GBV_ILN_2011
912			\|a GBV_ILN_2014
912			\|a GBV_ILN_2015
912			\|a GBV_ILN_2020
912			\|a GBV_ILN_2021
912			\|a GBV_ILN_2025
912			\|a GBV_ILN_2031
912			\|a GBV_ILN_2038
912			\|a GBV_ILN_2044
912			\|a GBV_ILN_2048
912			\|a GBV_ILN_2050
912			\|a GBV_ILN_2055
912			\|a GBV_ILN_2056
912			\|a GBV_ILN_2057
912			\|a GBV_ILN_2061
912			\|a GBV_ILN_2108
912			\|a GBV_ILN_2111
912			\|a GBV_ILN_2113
912			\|a GBV_ILN_2119
912			\|a GBV_ILN_2190
912			\|a GBV_ILN_4012
912			\|a GBV_ILN_4037
912			\|a GBV_ILN_4112
912			\|a GBV_ILN_4125
912			\|a GBV_ILN_4126
912			\|a GBV_ILN_4249
912			\|a GBV_ILN_4305
912			\|a GBV_ILN_4306
912			\|a GBV_ILN_4307
912			\|a GBV_ILN_4313
912			\|a GBV_ILN_4322
912			\|a GBV_ILN_4323
912			\|a GBV_ILN_4324
912			\|a GBV_ILN_4325
912			\|a GBV_ILN_4326
912			\|a GBV_ILN_4335
912			\|a GBV_ILN_4338
912			\|a GBV_ILN_4367
912			\|a GBV_ILN_4700
936	b	k	\|a 53.74 \|q VZ
936	b	k	\|a 54.32 \|q VZ
951			\|a AR
952			\|d 2024 \|j 2024 \|e 1 \|b 08 \|c 06

Indexfelder

author_variant	r s a rs rsa
matchkey_str	article:16871499:2024----::mliahotnpooowtefcetnryosmtoiitp
hierarchy_sort_str	2024
bklnumber	53.74 54.32
publishDate	2024
allfields	10.1186/s13638-024-02377-1 doi (DE-627)SPR056170718 (SPR)s13638-024-02377-1-e DE-627 ger DE-627 rakwb eng 620 004 VZ 53.74 bkl 54.32 bkl Abujassar, Radwan S. verfasserin (orcid)0000-0002-4572-5588 aut A multi path routing protocol with efficient energy consumption in IoT applications real time traffic 2024 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier © The Author(s) 2024 Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. Network performance stability using the intelligent routing protocol (nPSIR) (dpeaa)DE-He213 Internet of Things (IoT) (dpeaa)DE-He213 HEAD nodes (HN) (dpeaa)DE-He213 Request packets for creative and investigation (RPcI) (dpeaa)DE-He213 WSN (dpeaa)DE-He213 Enthalten in EURASIP journal on wireless communications and networking Springer International Publishing, 2004 2024(2024), 1 vom: 08. Juni (DE-627)47265151X (DE-600)2168613-0 1687-1499 nnns volume:2024 year:2024 number:1 day:08 month:06 https://dx.doi.org/10.1186/s13638-024-02377-1 X:SPRINGER Resolving-System kostenfrei Volltext SYSFLAG_0 GBV_SPRINGER GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_206 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_702 GBV_ILN_2001 GBV_ILN_2003 GBV_ILN_2005 GBV_ILN_2006 GBV_ILN_2008 GBV_ILN_2009 GBV_ILN_2010 GBV_ILN_2011 GBV_ILN_2014 GBV_ILN_2015 GBV_ILN_2020 GBV_ILN_2021 GBV_ILN_2025 GBV_ILN_2031 GBV_ILN_2038 GBV_ILN_2044 GBV_ILN_2048 GBV_ILN_2050 GBV_ILN_2055 GBV_ILN_2056 GBV_ILN_2057 GBV_ILN_2061 GBV_ILN_2108 GBV_ILN_2111 GBV_ILN_2113 GBV_ILN_2119 GBV_ILN_2190 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4335 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 53.74 VZ 54.32 VZ AR 2024 2024 1 08 06
spelling	10.1186/s13638-024-02377-1 doi (DE-627)SPR056170718 (SPR)s13638-024-02377-1-e DE-627 ger DE-627 rakwb eng 620 004 VZ 53.74 bkl 54.32 bkl Abujassar, Radwan S. verfasserin (orcid)0000-0002-4572-5588 aut A multi path routing protocol with efficient energy consumption in IoT applications real time traffic 2024 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier © The Author(s) 2024 Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. Network performance stability using the intelligent routing protocol (nPSIR) (dpeaa)DE-He213 Internet of Things (IoT) (dpeaa)DE-He213 HEAD nodes (HN) (dpeaa)DE-He213 Request packets for creative and investigation (RPcI) (dpeaa)DE-He213 WSN (dpeaa)DE-He213 Enthalten in EURASIP journal on wireless communications and networking Springer International Publishing, 2004 2024(2024), 1 vom: 08. Juni (DE-627)47265151X (DE-600)2168613-0 1687-1499 nnns volume:2024 year:2024 number:1 day:08 month:06 https://dx.doi.org/10.1186/s13638-024-02377-1 X:SPRINGER Resolving-System kostenfrei Volltext SYSFLAG_0 GBV_SPRINGER GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_206 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_702 GBV_ILN_2001 GBV_ILN_2003 GBV_ILN_2005 GBV_ILN_2006 GBV_ILN_2008 GBV_ILN_2009 GBV_ILN_2010 GBV_ILN_2011 GBV_ILN_2014 GBV_ILN_2015 GBV_ILN_2020 GBV_ILN_2021 GBV_ILN_2025 GBV_ILN_2031 GBV_ILN_2038 GBV_ILN_2044 GBV_ILN_2048 GBV_ILN_2050 GBV_ILN_2055 GBV_ILN_2056 GBV_ILN_2057 GBV_ILN_2061 GBV_ILN_2108 GBV_ILN_2111 GBV_ILN_2113 GBV_ILN_2119 GBV_ILN_2190 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4335 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 53.74 VZ 54.32 VZ AR 2024 2024 1 08 06
allfields_unstemmed	10.1186/s13638-024-02377-1 doi (DE-627)SPR056170718 (SPR)s13638-024-02377-1-e DE-627 ger DE-627 rakwb eng 620 004 VZ 53.74 bkl 54.32 bkl Abujassar, Radwan S. verfasserin (orcid)0000-0002-4572-5588 aut A multi path routing protocol with efficient energy consumption in IoT applications real time traffic 2024 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier © The Author(s) 2024 Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. Network performance stability using the intelligent routing protocol (nPSIR) (dpeaa)DE-He213 Internet of Things (IoT) (dpeaa)DE-He213 HEAD nodes (HN) (dpeaa)DE-He213 Request packets for creative and investigation (RPcI) (dpeaa)DE-He213 WSN (dpeaa)DE-He213 Enthalten in EURASIP journal on wireless communications and networking Springer International Publishing, 2004 2024(2024), 1 vom: 08. Juni (DE-627)47265151X (DE-600)2168613-0 1687-1499 nnns volume:2024 year:2024 number:1 day:08 month:06 https://dx.doi.org/10.1186/s13638-024-02377-1 X:SPRINGER Resolving-System kostenfrei Volltext SYSFLAG_0 GBV_SPRINGER GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_206 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_702 GBV_ILN_2001 GBV_ILN_2003 GBV_ILN_2005 GBV_ILN_2006 GBV_ILN_2008 GBV_ILN_2009 GBV_ILN_2010 GBV_ILN_2011 GBV_ILN_2014 GBV_ILN_2015 GBV_ILN_2020 GBV_ILN_2021 GBV_ILN_2025 GBV_ILN_2031 GBV_ILN_2038 GBV_ILN_2044 GBV_ILN_2048 GBV_ILN_2050 GBV_ILN_2055 GBV_ILN_2056 GBV_ILN_2057 GBV_ILN_2061 GBV_ILN_2108 GBV_ILN_2111 GBV_ILN_2113 GBV_ILN_2119 GBV_ILN_2190 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4335 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 53.74 VZ 54.32 VZ AR 2024 2024 1 08 06
allfieldsGer	10.1186/s13638-024-02377-1 doi (DE-627)SPR056170718 (SPR)s13638-024-02377-1-e DE-627 ger DE-627 rakwb eng 620 004 VZ 53.74 bkl 54.32 bkl Abujassar, Radwan S. verfasserin (orcid)0000-0002-4572-5588 aut A multi path routing protocol with efficient energy consumption in IoT applications real time traffic 2024 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier © The Author(s) 2024 Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. Network performance stability using the intelligent routing protocol (nPSIR) (dpeaa)DE-He213 Internet of Things (IoT) (dpeaa)DE-He213 HEAD nodes (HN) (dpeaa)DE-He213 Request packets for creative and investigation (RPcI) (dpeaa)DE-He213 WSN (dpeaa)DE-He213 Enthalten in EURASIP journal on wireless communications and networking Springer International Publishing, 2004 2024(2024), 1 vom: 08. Juni (DE-627)47265151X (DE-600)2168613-0 1687-1499 nnns volume:2024 year:2024 number:1 day:08 month:06 https://dx.doi.org/10.1186/s13638-024-02377-1 X:SPRINGER Resolving-System kostenfrei Volltext SYSFLAG_0 GBV_SPRINGER GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_206 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_702 GBV_ILN_2001 GBV_ILN_2003 GBV_ILN_2005 GBV_ILN_2006 GBV_ILN_2008 GBV_ILN_2009 GBV_ILN_2010 GBV_ILN_2011 GBV_ILN_2014 GBV_ILN_2015 GBV_ILN_2020 GBV_ILN_2021 GBV_ILN_2025 GBV_ILN_2031 GBV_ILN_2038 GBV_ILN_2044 GBV_ILN_2048 GBV_ILN_2050 GBV_ILN_2055 GBV_ILN_2056 GBV_ILN_2057 GBV_ILN_2061 GBV_ILN_2108 GBV_ILN_2111 GBV_ILN_2113 GBV_ILN_2119 GBV_ILN_2190 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4335 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 53.74 VZ 54.32 VZ AR 2024 2024 1 08 06
allfieldsSound	10.1186/s13638-024-02377-1 doi (DE-627)SPR056170718 (SPR)s13638-024-02377-1-e DE-627 ger DE-627 rakwb eng 620 004 VZ 53.74 bkl 54.32 bkl Abujassar, Radwan S. verfasserin (orcid)0000-0002-4572-5588 aut A multi path routing protocol with efficient energy consumption in IoT applications real time traffic 2024 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier © The Author(s) 2024 Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. Network performance stability using the intelligent routing protocol (nPSIR) (dpeaa)DE-He213 Internet of Things (IoT) (dpeaa)DE-He213 HEAD nodes (HN) (dpeaa)DE-He213 Request packets for creative and investigation (RPcI) (dpeaa)DE-He213 WSN (dpeaa)DE-He213 Enthalten in EURASIP journal on wireless communications and networking Springer International Publishing, 2004 2024(2024), 1 vom: 08. Juni (DE-627)47265151X (DE-600)2168613-0 1687-1499 nnns volume:2024 year:2024 number:1 day:08 month:06 https://dx.doi.org/10.1186/s13638-024-02377-1 X:SPRINGER Resolving-System kostenfrei Volltext SYSFLAG_0 GBV_SPRINGER GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_206 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_702 GBV_ILN_2001 GBV_ILN_2003 GBV_ILN_2005 GBV_ILN_2006 GBV_ILN_2008 GBV_ILN_2009 GBV_ILN_2010 GBV_ILN_2011 GBV_ILN_2014 GBV_ILN_2015 GBV_ILN_2020 GBV_ILN_2021 GBV_ILN_2025 GBV_ILN_2031 GBV_ILN_2038 GBV_ILN_2044 GBV_ILN_2048 GBV_ILN_2050 GBV_ILN_2055 GBV_ILN_2056 GBV_ILN_2057 GBV_ILN_2061 GBV_ILN_2108 GBV_ILN_2111 GBV_ILN_2113 GBV_ILN_2119 GBV_ILN_2190 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4335 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 53.74 VZ 54.32 VZ AR 2024 2024 1 08 06
language	English
source	Enthalten in EURASIP journal on wireless communications and networking 2024(2024), 1 vom: 08. Juni volume:2024 year:2024 number:1 day:08 month:06
sourceStr	Enthalten in EURASIP journal on wireless communications and networking 2024(2024), 1 vom: 08. Juni volume:2024 year:2024 number:1 day:08 month:06
format_phy_str_mv	Article
institution	findex.gbv.de
topic_facet	Network performance stability using the intelligent routing protocol (nPSIR) Internet of Things (IoT) HEAD nodes (HN) Request packets for creative and investigation (RPcI) WSN
dewey-raw	620
isfreeaccess_bool	true
container_title	EURASIP journal on wireless communications and networking
authorswithroles_txt_mv	Abujassar, Radwan S. @@aut@@
publishDateDaySort_date	2024-06-08T00:00:00Z
hierarchy_top_id	47265151X
dewey-sort	3620
id	SPR056170718
language_de	englisch
fullrecord	<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000naa a22002652 4500</leader><controlfield tag="001">SPR056170718</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20240609064640.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">240609s2024 xx \|\|\|\|\|o 00\| \|\|eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1186/s13638-024-02377-1</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)SPR056170718</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(SPR)s13638-024-02377-1-e</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="082" ind1="0" ind2="4"><subfield code="a">620</subfield><subfield code="a">004</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">53.74</subfield><subfield code="2">bkl</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">54.32</subfield><subfield code="2">bkl</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Abujassar, Radwan S.</subfield><subfield code="e">verfasserin</subfield><subfield code="0">(orcid)0000-0002-4572-5588</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">A multi path routing protocol with efficient energy consumption in IoT applications real time traffic</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2024</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">© The Author(s) 2024</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Network performance stability using the intelligent routing protocol (nPSIR)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Internet of Things (IoT)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">HEAD nodes (HN)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Request packets for creative and investigation (RPcI)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">WSN</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">Enthalten in</subfield><subfield code="t">EURASIP journal on wireless communications and networking</subfield><subfield code="d">Springer International Publishing, 2004</subfield><subfield code="g">2024(2024), 1 vom: 08. Juni</subfield><subfield code="w">(DE-627)47265151X</subfield><subfield code="w">(DE-600)2168613-0</subfield><subfield code="x">1687-1499</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:2024</subfield><subfield code="g">year:2024</subfield><subfield code="g">number:1</subfield><subfield code="g">day:08</subfield><subfield code="g">month:06</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://dx.doi.org/10.1186/s13638-024-02377-1</subfield><subfield code="m">X:SPRINGER</subfield><subfield code="x">Resolving-System</subfield><subfield code="z">kostenfrei</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_0</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_SPRINGER</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_11</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_20</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_22</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_23</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_24</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_39</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_40</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_60</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_62</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_63</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_65</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_69</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_73</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_95</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_105</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_110</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_151</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_161</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_170</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_206</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_213</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_230</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_285</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_293</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_370</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_602</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_702</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2001</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2003</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2005</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2006</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2008</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2009</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2010</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2011</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2014</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2015</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2020</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2021</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2025</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2031</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2038</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2044</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2048</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2050</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2055</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2056</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2057</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2061</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2108</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2111</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2113</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2119</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2190</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4012</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4037</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4112</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4125</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4126</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4249</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4305</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4306</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4307</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4313</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4322</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4323</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4324</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4325</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4326</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4335</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4338</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4367</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4700</subfield></datafield><datafield tag="936" ind1="b" ind2="k"><subfield code="a">53.74</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="936" ind1="b" ind2="k"><subfield code="a">54.32</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">2024</subfield><subfield code="j">2024</subfield><subfield code="e">1</subfield><subfield code="b">08</subfield><subfield code="c">06</subfield></datafield></record></collection>
author	Abujassar, Radwan S.
spellingShingle	Abujassar, Radwan S. ddc 620 bkl 53.74 bkl 54.32 misc Network performance stability using the intelligent routing protocol (nPSIR) misc Internet of Things (IoT) misc HEAD nodes (HN) misc Request packets for creative and investigation (RPcI) misc WSN A multi path routing protocol with efficient energy consumption in IoT applications real time traffic
authorStr	Abujassar, Radwan S.
ppnlink_with_tag_str_mv	@@773@@(DE-627)47265151X
format	electronic Article
dewey-ones	620 - Engineering & allied operations 004 - Data processing & computer science
delete_txt_mv	keep
author_role	aut
collection	springer
remote_str	true
illustrated	Not Illustrated
issn	1687-1499
topic_title	620 004 VZ 53.74 bkl 54.32 bkl A multi path routing protocol with efficient energy consumption in IoT applications real time traffic Network performance stability using the intelligent routing protocol (nPSIR) (dpeaa)DE-He213 Internet of Things (IoT) (dpeaa)DE-He213 HEAD nodes (HN) (dpeaa)DE-He213 Request packets for creative and investigation (RPcI) (dpeaa)DE-He213 WSN (dpeaa)DE-He213
topic	ddc 620 bkl 53.74 bkl 54.32 misc Network performance stability using the intelligent routing protocol (nPSIR) misc Internet of Things (IoT) misc HEAD nodes (HN) misc Request packets for creative and investigation (RPcI) misc WSN
topic_unstemmed	ddc 620 bkl 53.74 bkl 54.32 misc Network performance stability using the intelligent routing protocol (nPSIR) misc Internet of Things (IoT) misc HEAD nodes (HN) misc Request packets for creative and investigation (RPcI) misc WSN
topic_browse	ddc 620 bkl 53.74 bkl 54.32 misc Network performance stability using the intelligent routing protocol (nPSIR) misc Internet of Things (IoT) misc HEAD nodes (HN) misc Request packets for creative and investigation (RPcI) misc WSN
format_facet	Elektronische Aufsätze Aufsätze Elektronische Ressource
format_main_str_mv	Text Zeitschrift/Artikel
carriertype_str_mv	cr
hierarchy_parent_title	EURASIP journal on wireless communications and networking
hierarchy_parent_id	47265151X
dewey-tens	620 - Engineering 000 - Computer science, knowledge & systems
hierarchy_top_title	EURASIP journal on wireless communications and networking
isfreeaccess_txt	true
familylinks_str_mv	(DE-627)47265151X (DE-600)2168613-0
title	A multi path routing protocol with efficient energy consumption in IoT applications real time traffic
ctrlnum	(DE-627)SPR056170718 (SPR)s13638-024-02377-1-e
title_full	A multi path routing protocol with efficient energy consumption in IoT applications real time traffic
author_sort	Abujassar, Radwan S.
journal	EURASIP journal on wireless communications and networking
journalStr	EURASIP journal on wireless communications and networking
lang_code	eng
isOA_bool	true
dewey-hundreds	600 - Technology 000 - Computer science, information & general works
recordtype	marc
publishDateSort	2024
contenttype_str_mv	txt
author_browse	Abujassar, Radwan S.
container_volume	2024
class	620 004 VZ 53.74 bkl 54.32 bkl
format_se	Elektronische Aufsätze
author-letter	Abujassar, Radwan S.
doi_str_mv	10.1186/s13638-024-02377-1
normlink	(ORCID)0000-0002-4572-5588
normlink_prefix_str_mv	(orcid)0000-0002-4572-5588
dewey-full	620 004
title_sort	a multi path routing protocol with efficient energy consumption in iot applications real time traffic
title_auth	A multi path routing protocol with efficient energy consumption in IoT applications real time traffic
abstract	Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. © The Author(s) 2024
abstractGer	Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. © The Author(s) 2024
abstract_unstemmed	Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility. © The Author(s) 2024
collection_details	SYSFLAG_0 GBV_SPRINGER GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_206 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_702 GBV_ILN_2001 GBV_ILN_2003 GBV_ILN_2005 GBV_ILN_2006 GBV_ILN_2008 GBV_ILN_2009 GBV_ILN_2010 GBV_ILN_2011 GBV_ILN_2014 GBV_ILN_2015 GBV_ILN_2020 GBV_ILN_2021 GBV_ILN_2025 GBV_ILN_2031 GBV_ILN_2038 GBV_ILN_2044 GBV_ILN_2048 GBV_ILN_2050 GBV_ILN_2055 GBV_ILN_2056 GBV_ILN_2057 GBV_ILN_2061 GBV_ILN_2108 GBV_ILN_2111 GBV_ILN_2113 GBV_ILN_2119 GBV_ILN_2190 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4335 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700
container_issue	1
title_short	A multi path routing protocol with efficient energy consumption in IoT applications real time traffic
url	https://dx.doi.org/10.1186/s13638-024-02377-1
remote_bool	true
ppnlink	47265151X
mediatype_str_mv	c
isOA_txt	true
hochschulschrift_bool	false
doi_str	10.1186/s13638-024-02377-1
up_date	2024-07-03T20:39:39.665Z
_version_	1803591802857455616
fullrecord_marcxml	<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000naa a22002652 4500</leader><controlfield tag="001">SPR056170718</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20240609064640.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">240609s2024 xx \|\|\|\|\|o 00\| \|\|eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1186/s13638-024-02377-1</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)SPR056170718</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(SPR)s13638-024-02377-1-e</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="082" ind1="0" ind2="4"><subfield code="a">620</subfield><subfield code="a">004</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">53.74</subfield><subfield code="2">bkl</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">54.32</subfield><subfield code="2">bkl</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Abujassar, Radwan S.</subfield><subfield code="e">verfasserin</subfield><subfield code="0">(orcid)0000-0002-4572-5588</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">A multi path routing protocol with efficient energy consumption in IoT applications real time traffic</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2024</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">© The Author(s) 2024</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Abstract The extensive utilization of IoT applications leads to the aggregation of a substantial volume of data, presenting a crucial challenge in terms of data routing within these networks. RPL intentionally surpasses the limitations sometimes observed in low-power and lossy networks, which are particularly prevalent in IoT networks. The RPL protocol is designed specifically for static networks that do not involve mobility or topological changes. The RPL protocol guarantees continuous connectivity between nodes and mitigates the risk of data loss in stationary IoT applications that do not involve mobility or alterations in network configuration. The article utilizes a mobility aid technology known as network performance stability using the intelligent routing protocol (nPSIR), which expands upon RPL. The Mobility Support Entity (nPSIR) facilitates the displacement of all nodes, with the exception of the root node, and ensures uninterrupted connection during mobility. Moreover, it deals with the situation where there is a physical barrier between two interconnected nodes in a changing environment. In order to achieve this objective, it employs a dynamic trickle timer that operates within two distinct ranges. Furthermore, it utilizes a neighbor link quality table, a mechanism for selecting the most beneficial parent node in the event of migration, a measure of confidence, the identification of crucial regions, and a blacklist. Multiple simulations validate that nPSIR effectively decreases hand-off delay and improves packet delivery, despite the minor drawbacks of increased signaling costs and power consumption. The delivery ratio decreases the quantity of lost data packets and surpasses both RPL as a responsive protocol and mRPL as a proactive protocol in relation to mobility.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Network performance stability using the intelligent routing protocol (nPSIR)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Internet of Things (IoT)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">HEAD nodes (HN)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Request packets for creative and investigation (RPcI)</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">WSN</subfield><subfield code="7">(dpeaa)DE-He213</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">Enthalten in</subfield><subfield code="t">EURASIP journal on wireless communications and networking</subfield><subfield code="d">Springer International Publishing, 2004</subfield><subfield code="g">2024(2024), 1 vom: 08. Juni</subfield><subfield code="w">(DE-627)47265151X</subfield><subfield code="w">(DE-600)2168613-0</subfield><subfield code="x">1687-1499</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:2024</subfield><subfield code="g">year:2024</subfield><subfield code="g">number:1</subfield><subfield code="g">day:08</subfield><subfield code="g">month:06</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://dx.doi.org/10.1186/s13638-024-02377-1</subfield><subfield code="m">X:SPRINGER</subfield><subfield code="x">Resolving-System</subfield><subfield code="z">kostenfrei</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_0</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_SPRINGER</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_11</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_20</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_22</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_23</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_24</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_39</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_40</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_60</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_62</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_63</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_65</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_69</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_73</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_95</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_105</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_110</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_151</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_161</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_170</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_206</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_213</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_230</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_285</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_293</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_370</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_602</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_702</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2001</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2003</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2005</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2006</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2008</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2009</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2010</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2011</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2014</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2015</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2020</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2021</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2025</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2031</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2038</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2044</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2048</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2050</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2055</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2056</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2057</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2061</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2108</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2111</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2113</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2119</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2190</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4012</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4037</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4112</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4125</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4126</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4249</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4305</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4306</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4307</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4313</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4322</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4323</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4324</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4325</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4326</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4335</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4338</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4367</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4700</subfield></datafield><datafield tag="936" ind1="b" ind2="k"><subfield code="a">53.74</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="936" ind1="b" ind2="k"><subfield code="a">54.32</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">2024</subfield><subfield code="j">2024</subfield><subfield code="e">1</subfield><subfield code="b">08</subfield><subfield code="c">06</subfield></datafield></record></collection>
score	7.4014015

Nicht das Richtige dabei?

Schreiben Sie uns!

A multi path routing protocol with efficient energy consumption in IoT applications real time traffic

Nicht das Richtige dabei?

Zugang & Verfügbarkeit

Vorhandene Bände

Nicht das Richtige dabei?