Indie Fog: an Efficient Fog-Computing Infrastructure for the Internet of Things
Total Page:16
File Type:pdf, Size:1020Kb
CLOUD COVER Indie Fog: An Efficient Fog-Computing Infrastructure for the However, fog computing faces its own challenges, such as equipment that works only with the service pro- viders’ technologies or only with cel- Internet of Things lular networks. In response, we have proposed Chii Chang and Satish Narayana Srirama, University of Tartu the Indie Fog infrastructure, which utilizes consumers’ networking de- Rajkumar Buyya, University of Melbourne and Manjrasoft Pty Ltd. vices—such as their Wi-Fi access- point routers—to provide IoT service Fog computing can help with some of providers with a fog-computing en- vironment. This reduces the need the Internet of Things’ limitations but also for IoT service providers to deploy their own devices throughout a fog faces challenges of its own. The Indie Fog system. infrastructure could be a flexible, cost-effective Indie Fog would be flexible and cost-effective, support the IoT, and way to cope with these challenges. work with today’s technologies. THE IoT’S LATENCY he Internet of Things (IoT) has created many CHALLENGE technical and business opportunities but also The IoT represents the Internet’s next stage, in which has its limitations. For example, the traditional common objects such as vehicles, home appliances, office cloud-based IoT can experience more latency equipment, manufacturing facilities, and consumer elec- Tthan many target applications can tolerate. tronic devices connect to the Internet.1 This facilitates im- Fog computing, which moves computation and net- portant new software-based services such as smart cities, working closer to the network edge, reduces the need to smart factories, smart agriculture, and ambient assisted communicate via the cloud and thus decreases latency. living (AAL). 92 COMPUTER PUBLISHED BY THE IEEE COMPUTER SOCIETY 0018-9162/17/$33.00 © 2017 IEEE EDITOR SAN MURUGESAN BRITE Professional Services; [email protected] Central management server Central management server Deploy Deploy Data source Fog application package Data source Fog application Indie Fog package Indie Fog Gateway (a) Application (b) Figure 1. Two types of Indie Fog deployments. (a) In the integrated form, the functionality is provided by a gateway device integrated into the Indie Fog server, which connects to data sources and user devices. (b) In the collaborative form, the functionality is provided by a workstation in the same subnet as the data-source devices, to which it connects via an Internet gateway. In the IoT’s architecture, a cloud- home Internet router the provider various distributed computing tasks. based central server manages all ac- sends to the customer. This is different And Fon (fon.com) utilizes CPEs to es- tivities of IoT devices residing at the from public-cloud systems, in which tablish a global Wi-Fi network. These network edge. This cloud-centric IoT third-party infrastructure companies examples confirm that many consum- (CIoT) requires these devices to send offer generic platforms that work with ers are willing to let providers pay to use their data to the central server and wait multiple service providers. their equipment for offering services. for its response, thereby creating la- Recently, the European Telecom- We envision the CaP model ex- tency. Many emerging, data-intensive munications Standards Institute (ETSI) tending to fog computing, and we IoT-driven applications, such as AAL introduced the Mobile Edge Computing use this approach in Indie Fog. Indi- and smart-traffic services, can’t toler- (MEC) architecture,3 which lets CIoT viduals, not just organizations, could ate latency. Researchers have thus de- providers utilize cellular base stations’ configure their devices to provide veloped fog computing.2 virtual machine (VM)-enabled servers public fog services. The independent to perform distributed computational nature of such a deployment inspired FOG COMPUTING’S or networking processes at the cellular- us to use the name Indie Fog, much CHALLENGES network edge. However, because MEC as the term is used in areas such as By operating at the network edge, fog works only with cellular networks, its indie art, indie music, indie design, computing brings computation and usefulness is limited. and indie games.5 networking closer to users and data To address these limitations, we sources. This reduces latency and in- propose Indie Fog. INDIE FOG’S ROLE creases computational and communi- In general, Indie Fog services come cation efficiency. CONSUMER AS PROVIDER in two forms: integrated and collabo- Typically, network-infrastructure The popular Consumer as Provider rative (see Figure 1). In the integrated providers, ISPs, or cloud-service pro- (CaP) service-provision model4 has version, the Internet router itself viders offer fog services via customer- triggered a new form of service provi- provides the virtual server that acts premises equipment (CPE) designed sion in multiple domains. For example, as the fog node. In the collaborative specifically for the providers’ applica- the MQL5 Cloud Network distributed- version, a computer connected to the tions. For example, an ISP might en- computing project (cloud.mql5.com) Internet router provides the fog node. able fog services from the proprietary uses consumers’ equipment to perform Both Indie Fog types operate at the SEPTEMBER 2017 93 CLOUD COVER Cloud Core network (regional) Access/edge network (neighborhood) Private fog Public fog Gateway/CPE Indie Fog Indie Fog (building/street) Private fog Indie Fog End points Private fog Physical connection Virtual connection Figure 2. Customer-premises equipment (CPE), computers embedded in vehicles, or mobile devices with Internet connections can host an Indie Fog system. Because the technology is software defined, Indie Fog nodes provide virtual connectivity across different layers of the cloud-centric Internet of Things (IoT) architecture. fog computing architecture’s gateway devices that have OSs and Internet con- either hypervisor-oriented VM layer. nectivity—including consumer elec- technologies or containeriza- According to the OpenFog Consor- tronics, appliances, smartphones, and tion technologies. A trusted tium,2 the fog-computing architec- computers embedded in vehicles—at cloud-based coordinator ture has multiple layers (see Figure the gateway layer. service manages the registered 2). In general, the fog server can be Indie Fog has the following nodes. hosted in devices at the access layer characteristics: (such as a citywide Internet gateway), › Interoperability. Indie fog nodes INDIE FOG DEPLOYMENT at the gateway layer (such as within can interact with other fog nodes There are four basic Indie Fog deploy- a building or in the street), or within to create a software-defined ment models. various objects (such as vehicles, lap- network. tops, or smartphones) that serve as IoT › Scalability. A CIoT system can Clustered Indie Fog end points. form a scalable, software-defined When a group of stationary Indie Fog Commonly, service providers fol- cluster of Indie Fog nodes. Both nodes are in close proximity, such as low the private fog model, in which public and private fog systems within an ISP’s subnet or in the same they configure a fog server within a can use Indie Fog to extend their building, they are ideal for establish- device for use only by specified parties. networks. ing a software-defined grid-comput- In the public fog model, like that used › Cost efficiency. Because Indie Fog ing cluster (see Figure 3a). Such a clus- in the MEC architecture, providers uses customer equipment, it’s ter can perform, in the edge network, make fog services available via generic less expensive, particularly for high-performance preprocessing of platforms to any paying customer with large deployments. data collected by sensors and other the proper equipment. › Security. Indie Fog nodes provide sources. This reduces the bandwidth Figure 2 shows how Indie Fog serv- a sandbox-based software- needed to send the data to the cloud ers can be in various consumer-based deployment environment using and the cost of processing it. 94 COMPUTER WWW.COMPUTER.ORG/COMPUTER Cloud management server Cloud management server Cloud management server Cloud management server Deploy Deploy Deploy Deploy Deploy script source code Deploy Deploy Deploy Deploy Deploy Indie Fog Indie Fog Indie Fog Indie Fog Indie Fog Indie Fog Indie Fog Indie Fog Indie Fog Indie Fog Indie Fog Sense Sense Data source Data source Data source Physical world (a) (b) (c) (d) Figure 3. Indie Fog facilitates the deployment of four types of software-defined cloud-centric IoT systems: (a) clustered Indie Fog, (b) infrastructural Indie Fog, (c) vehicular Indie Fog, and (d) smartphone Indie Fog. Infrastructural Indie Fog dynamic, random connections. How- analyze data for context brokering, Indie Fog deployed in stationary sen- ever, mobile-device-based server which is the collection and analysis of sor devices, such as cameras, in an nodes could still be useful in urban data to provide context for subsequent urban outdoor area could provide an sensing. Smartphones could collect decision making. infrastructure for ubiquitous appli- many kinds of sensory data. If smart- cations that require temporary data phone users install Indie Fog servers Software-defined IoT orchestration. acquisition and processing in a short on their devices, the phones could Deploying a distributed IoT-driven period of time (see Figure 3b). For ex- provide and even preprocess their col- Business Process Management System ample, scientists