The Middleware for Edge Clouds & Cloudlets (MECC) workshop aims to address the increasing need for closer integration between the different tiers on modern cloud computing platforms.
There is a growing trend of interactive and resource-intensive (e.g., compute, storage, need for big data) applications on mobile devices today, and currently many such applications are provided using resources on infrastructural clouds. However, it is challenging to provide such applications using cloud resources when there is limited connectivity. Harvesting the resources present on nearby mobile devices and/or cloudlets is a viable solution to this problem.
Today, there is also increasing demand for middleware that offers higher level abstractions without hampering expressiveness and performance. However, many distributed systems today are designed for the datacenter, and their assumptions, such as that nodes use fast wired interconnects, no longer hold in edge environments. In particular, edge clouds, such as those made up of only mobile devices at the edge, use unreliable wireless links. These unreliable links directly translate into unavailability and churn. Simultaneously, since mobile devices have limited energy resources, heavyweight distributed algorithms, such as coordination using a leader-based consensus protocol, are impractical.
As an effort to offload computation from mobile devices, cloudlets were originally envisioned as server-class hardware deployed in a neighborhood, office building or more generally, in close physical proximity to any scenario with a high density of users, such as at large public events. It is now transitioning to a more lightweight approach where the offloading is done through multiple techniques besides the use of virtual machines, as originally proposed, and where cloudlets can also offer connectivity support to crowd-sourced mobile devices, i.e., edge clouds.
With this new trend in sight, there is a need to define the services that should be offered at each tier. For example, cloudlets can provide well-defined APIs to support multiple computation offloading methods. Furthermore, new modular and reconfigurable architectures have to be proposed in order to support a variety of deployment scenarios, such as edge clouds without cloudlet support, and scenarios with very limited access to infrastructural clouds.
Topics of interest include but are not limited to:
All accepted papers will appear in a Middleware 2016 companion proceedings, which will be available in the ACM Digital Library prior to the workshop.
At least one of the authors will have to register for the workshop and present the paper.
Authors should also acknowledge the following disclaimer by the ACM: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. (For those rare conferences whose proceedings are published in the ACM Digital Library after the conference is over, the official publication date remains the first day of the conference.)
MECC 2016 will receive proposals for communication in the form of full research papers of at most 6 pages, and short research papers of at most 3 pages, including references. Short papers should either describe work-in-progress, or should describe visions of challenges, problems, and potential research directions in MECC. Content should be work that is not previously published or concurrently submitted elsewhere.
All submissions should be in PDF and must follow the ACM template. Submissions must have authors information, text, figures, references and appendices (if applicable). Submissions that do not respect the formatting requirement may be rejected without review.
Reviewing is single-blind. This means that the names and affiliations of the authors must appear in the submitted papers. Each paper will receive at least three reviews from members of the program committee.
Submissions should be done through EasyChair at the following URL: https://easychair.org/conferences/?conf=mecc2016
General and Technical Program Co-Chairs
The program co-chairs can be contacted through the workshop Easychair email.Technical Program Committee
The Middleware for Edge Clouds & Cloudlets (MECC) workshop aims to address the ever-increasing need for a closer integration between the different tiers on modern cloud computing platforms. Several opportunities can arise from a better integration/leverage of these different tiers.
The increasing concerns about privacy and data security might be an enabler for MECC, as computation can be done locally, the need for central rendezvous (normally provided by an infrastructure cloud) can be avoided or at least minimized. We also envision new applications that make use of this local computation and data locality, such as VR.
Research on edge clouds and cloudlets has been progressively generating more interest in the systems research community. As an indicator of this interest, since 2014 there have been 1750 papers on cloudlets and 296 on edge clouds.