2019
DOI: 10.1007/978-3-030-14132-5_4
|View full text |Cite
|
Sign up to set email alerts
|

Meeting Smart City Latency Demands with SDN

Abstract: Smart cities utilise a large number of heterogeneous devices with goal to improve all aspects of city operations. This often includes critical functionality, which brings strict requirements on network communication. One of the most important requirements is network latency. This paper analyses latency requirements in areas of smart cities and related domains. Analysed requirements are then practically tested in use case networks based on software-defined networking-a modern paradigm of network programmability… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
3
1
1

Relationship

1
4

Authors

Journals

citations
Cited by 6 publications
(2 citation statements)
references
References 8 publications
0
2
0
Order By: Relevance
“…The industry poses distinct performance requirements on IoT applications. For instance, the latency requirement in industrial automation is much demanding, e.g., <2 ms cycle time for motion control, 2-10 ms for factory automation, ∼50 ms for process monitoring and 10-100 ms for video-operated remote control [54] while latency is relatively tolerable in the massive IoT category, e.g., 40-500 ms for traffic management, <1 s for audio and video transfer in smart grid [55], etc. The payload in industrial communication can range from a few bytes for process automation up to 250 bytes for machine control [54] and 1.5 kilobytes for smart grid [56].…”
Section: Highlights Of Experimental Resultsmentioning
confidence: 99%
“…The industry poses distinct performance requirements on IoT applications. For instance, the latency requirement in industrial automation is much demanding, e.g., <2 ms cycle time for motion control, 2-10 ms for factory automation, ∼50 ms for process monitoring and 10-100 ms for video-operated remote control [54] while latency is relatively tolerable in the massive IoT category, e.g., 40-500 ms for traffic management, <1 s for audio and video transfer in smart grid [55], etc. The payload in industrial communication can range from a few bytes for process automation up to 250 bytes for machine control [54] and 1.5 kilobytes for smart grid [56].…”
Section: Highlights Of Experimental Resultsmentioning
confidence: 99%
“…Some quantitative requirements of IoT applications can be found in the literature. For instance, the latency requirement in industrial automation is much demanding, e.g., <2 ms cycle time for motion control, 2-10 ms for factory automation, ∼50 ms for process monitoring and 10-100 ms for videooperated remote control [7] while latency is relatively tolerable in the massive IoT category, e.g., 40-500 ms for traffic management, <1 s for audio and video transfer in smart grid [8], etc. The payload in industrial communication can range from a few bytes for process automation up to 250 bytes for machine control [7] and 1.5 kilobytes for smart grid [9].…”
Section: Iot Segmentationmentioning
confidence: 99%