Fog/Edge Computing

In recent years, with the proliferation of the Internet of Things (IoT) and the wide penetration of wireless networks, the number of edge devices and the data generated  from the edge have been growing rapidly [1]. Data mitigation is becoming a bottleneck constraining the cloud computing paradigm for delay-sensitive IoT services. Fog Computing promises lower response times for IoT services while provides the necessary computational resources, closer to the users, on the path between IoT devices to the cloud [2]. Fog Topology is organized hierarchically with IoT devices at the bottom and the cloud on top [3] [4].

Edge/Fog computing is a new paradigm in which the resources of an edge server are placed at the edge of the Internet, in close proximity to mobile devices, sensors, end users, and the emerging IoT. Terms such as “cloudlets,” “micro data centers,” and “fog” have been used in the literature to refer to these types of small, edge-located computing hardware. They all represent counterpoints to the theme of consolidation and massive data centers that have dominated discourse in cloud computing.

Three-Tier Fog Computing Model: By analyzing several representative application scenarios of fog computing we abstract a typical three-tier edge computing model: IoT, edge, and cloud. The first tier is IoT, including drones, sensors in the connected health area, devices and appliances in the smart home, and equipment in the industrial Internet.

Multiple communication protocols are used to connect IoT and the second tier, edge. Edge, including connected and autonomous vehicles, cellular tower, gateway, and edge servers, requires the huge computing and storage capabilities of the cloud to complete complex tasks. The protocols between IoT and the edge usually have the characteristics of low power consumption and short distance, while the protocols between the edge and the cloud have large throughput and high speed. The Ethernet, optical fibers, and the coming 5G are the preferred communication protocols between the edge and the cloud. Since a fog is made up of heterogenous devices [2] [5], ranging from low power sensors to powerful servers, the communication technologies used are also diverse, e.g., “ZigBee, Wi-Fi, 2G/3G/4G, WiMax, 6Lowpan and so on”[6]. There are several communication protocols that are used in fog computing, e.g., HTTP, CoAP, or MQTT [7].

Service Graph Topology Descriptions

The service graph is a topology-aware descriptive model where nodes represent the services composing an application and directed edges represent the relationship(s) and inter-dependencies between services. Nodes can be additionally annotated by a number of attributes denoting service-specific characteristics including configurations, optimizations, constraints and requirements. In turn, directed edges representing relationships and interdependencies denote the service deployment order, resource exchange protocols and can also be annotated with service-to-service specific characteristics such as the configuration shown in the figure.

Figure: Service Graph Example

In this figure that represents a service graph example, the product service is configured to direct 90% of the incoming requests to the current version of the reviews service while 10% of the traffic is directed to a newer (untested) version.

The service graph plays a prominent role in RAINBOW as users will be able to graphically describe their application topology, denote intercommunication and dependencies among services, and annotate the description with constraints, optimization policies and QoS requirements, simply denoted as “Configurations”. Users are not constantly derailed and can focus on core application development leaving enforcement to the RAINBOW platform. [8]

[1] W. Shi, G. Pallis and Z. Xu, “Edge computing,” in Proceedings of the IEEE, 2019

[2] F. Bonomi, R. Milito, J. Zhu and S. Addepalli, “Fog Computing and Its Role in the Internet of Things,” in Proceedings of the First Edition of the MCC Workshop on Mobile Cloud Computing, 2012

[3] C. C. Byers, “Architectural Imperatives for Fog Computing: Use Cases, Requirements, and Architectural Techniques for Fog-Enabled IoT Networks,” IEEE Communications Magazine, vol. 55, no. 8, 2017.

[4] OpenFog Consortium Architecture Working Group, “OpenFog Reference Architecture for Fog Computing,” OpenFog Consortium, 2017

[5] S. Yi, Z. Hao, Z. Qin and Q. Li, “Fog Computing: Platform and Applications,” in 2015 Third IEEE Workshop on Hot Topics in Web Systems and Technologies (HotWeb), 2015.

[6] Y. Shi, G. Ding, H. Wang, H. E. Roman and S. Lu, “The fog computing service for healthcare,” in 2015 2nd International Symposium on Future Information and Communication Technologies for Ubiquitous HealthCare (Ubi-HealthTech), 2015

[7] J. Dizdarević, F. Carpio, A. Jukan and X. Masip-Bruin, “A Survey of Communication Protocols for Internet of Things and Related Challenges of Fog and Cloud Computing Integration,” ACM Comput. Surv., 2019.

[8] F. Bonomi, R. Milito, J. Zhu and S. Addepalli, “Fog Computing and Its Role in the Internet of Things,” in Proceedings of the First Edition of the MCC Workshop on Mobile Cloud Computing, 2012

1 Comment
  1. […] Below you can read a blog post authored by K3Y and originally published at the RAINBOW website. […]

Leave a reply

Your email address will not be published. Required fields are marked *


Rainbow Project ©2024 All rights reserved

Log in with your credentials

Forgot your details?