Edge computing

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Edge computing is a distributed computing paradigm which brings computation and data storage closer to the location where it is needed, to improve response times and save bandwidth.[1]

The edge computing infrastructure

Concept[edit]

The increase of IoT devices at the edge of the network is producing a massive amount of data to be computed to data centers, pushing network bandwidth requirements to the limit. Despite the improvements of network technology, data centers cannot guarantee acceptable transfer rates and response times, which could be a critical requirement for many applications.[2] Furthermore devices at the edge constantly consume data coming from the cloud, forcing companies to build content delivery networks to decentralize data and service provisioning, leveraging physical proximity to the end user. In a similar way, the aim of Edge Computing is to move the computation away from data centers towards the edge of the network, exploiting smart objects, mobile phones or network gateways to perform tasks and provide services on behalf of the cloud. By moving services to the edge, it is possible to provide content caching, service delivery, storage and IoT management resulting in better response times and transfer rates. At the same time, distributing the logic in different network nodes introduces new issues and challenges.

Privacy and security[edit]

The distributed nature of this paradigm introduces a shift in security schemes used in cloud computing. Not only data should be encrypted, but different encryption mechanism should be adopted, since data may transit between different distributed nodes connected through the internet before eventually reaching the cloud. Edge nodes may also be resource constrained devices, limiting the choice in terms of security methods. Moreover a shift from centralized top-down infrastructure to a decentralized trust model is required.[3] On the other hand by keeping data at the edge it is possible to shift ownership of collected data from service providers to end-users.

Scalability[edit]

Scalability in a distributed network must face different issues. First, it must take into account the heterogeneity of the devices, having different performance and energy constraints, the highly dynamic condition and the reliability of the connections, compared to more robust infrastructure of cloud data centers. Moreover, security requirements may introduce further latency in the communication between nodes, which may slow down the scaling process.[2]

Reliability[edit]

Management of failovers is crucial in order to maintain a service alive. If a single node goes down and is unreachable, users should still be able to access a service without interruptions. Moreover, edge computing systems must provide actions to recover from a failure and alerting the user about the incident. To this aim, each device must maintain the network topology of the entire distributed system, so that detection of errors and recovery become easily applicable. Other factors that may influence this aspect are the connection technology in use, which may provide different levels of reliability, and the accuracy of the data produced at the edge that could be unreliable due to particular environment conditions. [2]

Applications[edit]

Edge application services reduce the volumes of data that must be moved, the consequent traffic, and the distance that data must travel. That provides lower latency and reduces transmission costs. Computation offloading for real-time applications, such as facial recognition algorithms, showed considerable improvements in response times as demonstrated in early research.[4] Further research showed that using resource rich machines near mobile users, called cloudlets, offering services typically found in the cloud, provided improvements in execution time when some of the tasks are offloaded to the edge node.[5]. On the other hand, offloading every task may result in a slowdown due to transfer times between device and nodes, so depending on the workload an optimal configuration can be defined.

Another vision of the architecture is to give a re-birth for cloud gaming where the game simulations are run in the cloud and the rendered video is transferred to lightweight clients such as mobile, VR glasses, etc. Such type of streaming is also known as pixel streaming.[6] Conventional cloud games may suffer from high latency and insufficient bandwidth, since the amount of data transferred is huge due to the high resolutions required by some services.[7] As real-time games such as FPS (First person Shooting) games have strict constraints on latency, processing game simulation at the edge node is necessary for the immersive game plays. Edge nodes when used for game streaming, are known as Gamelets,[6] which are usually one or two hops away from the client.[8]

Other notable applications include connected, autonomous cars.[9][10], smart cities[11], smart notifications[12] and home automation systems.[13]

Broad definition[edit]

Alex Reznik, Chair of the ETSI MEC ISG standards committee, has a broad definition, "anything that’s not a traditional data center could be the ‘edge’ to somebody."[14] Other definitions are more limited. The State of the Edge report[15] concentrates on servers "in close proximity to the last mile network." Gamelet paper[8] defines 'the edge node is mostly one or two hops away from the mobile client to meet the response time constraints for real-time games'. It also states, "Gamelet system is basically a distributed micro-cloud system in which the computationally intensive tasks such as game simulation and rendering are offloaded to a Gamelet node that is few hops (most of the time one or two hops) away from the mobile client". Philip Laidler believes "edge compute includes workloads running on customer premises."[16] Some call this the customer, enterprise, device edge or on-device. Another, more inclusive way to define "edge computing" is to include any type of computer program delivers low latency nearer to the requests. Karim Arabi, in an IEEE DAC 2014 Keynote [17] and subsequently in an invited talk at MIT's MTL Seminar in 2015 [18] defined Edge Computing broadly as all computing outside Cloud happening at the Edge of the network and more specifically in applications where real-time processing of data is required. In his definition, Cloud Computing operates on “Big Data” while Edge Computing operates on “Instant Data” that is real-time data generated by sensors or users.

See also[edit]

References[edit]

  1. ^ Hamilton, Eric. "What is Edge Computing: The Network Edge Explained". cloudwards.net. Retrieved 2019-05-14.
  2. ^ a b c Shi, Weisong; Cao, Jie; Zhang, Quan; Li, Youhuizi; Xu, Lanyu (October 2016). "Edge Computing: Vision and Challenges". IEEE Internet of Things Journal. 3 (5): 637–646. doi:10.1109/JIOT.2016.2579198.
  3. ^ Garcia Lopez, Pedro; Montresor, Alberto; Epema, Dick; Datta, Anwitaman; Higashino, Teruo; Iamnitchi, Adriana; Barcellos, Marinho; Felber, Pascal; Riviere, Etienne (30 September 2015). "Edge-centric Computing". ACM SIGCOMM Computer Communication Review. 45 (5): 37–42. doi:10.1145/2831347.2831354.
  4. ^ Yi, S.; Hao, Z.; Qin, Z.; Li, Q. (November 2015). "Fog Computing: Platform and Applications". 2015 Third IEEE Workshop on Hot Topics in Web Systems and Technologies (HotWeb): 73–78. doi:10.1109/HotWeb.2015.22. ISBN 978-1-4673-9688-2. Retrieved 4 July 2019.
  5. ^ Verbelen, Tim; Simoens, Pieter; De Turck, Filip; Dhoedt, Bart (2012). "Cloudlets: Bringing the Cloud to the Mobile User". Proceedings of the Third ACM Workshop on Mobile Cloud Computing and Services. ACM: 29–36. doi:10.1145/2307849.2307858. Retrieved 4 July 2019.
  6. ^ a b "CloudHide: Towards Latency Hiding Techniques for Thin-client Cloud Gaming". ResearchGate. Retrieved 2019-04-12.
  7. ^ "Google Stadia". Google Stadia Webpage. Retrieved 4 July 2019.
  8. ^ a b Anand, B.; Edwin, A. J. Hao (January 2014). "Gamelets — Multiplayer mobile games with distributed micro-clouds". 2014 Seventh International Conference on Mobile Computing and Ubiquitous Networking (ICMU): 14–20. doi:10.1109/ICMU.2014.6799051. ISBN 978-1-4799-2231-4.
  9. ^ Autonomous Cars, Big Data, and Edge Computing: What You Need to Know Published by dzone.com on February 19, 2019, retrieved April 10, 2019,
  10. ^ It's Time to Think Beyond Cloud Computing Published by wired.com retrieved April 10, 2019,
  11. ^ Taleb, Tarik; Dutta, Sunny; Ksentini, Adlen; Iqbal, Muddesar; Flinck, Hannu (March 2017). "Mobile Edge Computing Potential in Making Cities Smarter". IEEE Communications Magazine. 55 (3): 38–43. doi:10.1109/MCOM.2017.1600249CM. Retrieved 5 July 2019.
  12. ^ "What Is Edge Computing and How Can It Benefit Push Notifications?". OpenBack. July 2019.
  13. ^ Chakraborty, T.; Datta, S. K. (November 2017). "Home automation using edge computing and Internet of Things". 2017 IEEE International Symposium on Consumer Electronics (ISCE): 47–49. doi:10.1109/ISCE.2017.8355544. ISBN 978-1-5386-2189-9. Retrieved 5 July 2019.
  14. ^ "ETSI - ETSI Blog - What is Edge?". www.etsi.org. Retrieved 2019-02-19.
  15. ^ "DocSend - Simple, intelligent, modern content sending". DocSend. Retrieved 2019-02-19.
  16. ^ "10 things you should know about telco edge computing". www.stlpartners.com. Retrieved 2019-08-30.
  17. ^ IEEE DAC 2014 Keynote: Mobile Computing Opportunities, Challenges and Technology Drivers
  18. ^ MIT MTL Seminar: Trends, Opportunities and Challenges Driving Architecture and Design of Next Generation Mobile Computing and IoT Devices
Retrieved from "https://en.wikipedia.org/w/index.php?title=Edge_computing&oldid=920538833"