Mobile-process-based ubiquitous computing platform

Abstract

Mobile objects and agents are used for implementing distributed applications. Both concepts allow efficient use of local resources, volatile network connectivity and more efficient communication due to appropriate migration, especially in dynamic ubiquitous environments. Mobile processes enable specifying the complete life cycle of complex mobile applications. In this paper, we propose a mobile-process-based platform that turns ubiquitous application development into a manageable task. We advocate the use of Web services for implementing mobile processes in a heterogeneous environment. Based on previous work, we sketch a novel approach for realising mobile context-aware Web services, which implement process steps. We use a separation of state, functionality and implementation code, which enables a reduction, expansion and transformation of the service state and functionality during migration.

Recent Advances in Ambient Intelligence and Context-Aware Computing

“…Projects like Roam (Chu et al, 2004), Sparkle (Siu et al, 2004), Gaia (Ranganathan, Shankar, & Campbell, 2005), Desktop Migration System (Hwang, Park, & Chung, 2006), MDAgent (Zhou et al 2007), SAMProc (Schmidt, Kapitza, & Hauck, 2007), MSP (Hojgaard-Hansen, Nguyen, & Schwefel, 2010), and DPartner (Zhang, Huang, Zhang, Liu, & Mei, 2012) all resulted in centralized solutions, often with a middleware taking care of communication and controlling migration, in most cases using centralized code loading. Centralized architectures rely on stable network connections to function satisfactory.…”

Web-based adaptive application mobility

“…Roamlet class byte code can then be downloaded from a central server and adapted to fit the new device. The SAMProc [12] project works with self-adaptive mobile processes in a similar way, however using a decentralized system infrastructure based on peer-to-peer. Both projects are examples of systems for application migration based on code loading.…”

“…Most solutions rely on centralized distribution of applications (MDAgent [7]; Sparkle [8]; Gaia [9]; MSP [10]) and/or code loading (Roam [11]; SAMProc [12]), when a central server is used to store different versions of the application. Other projects display decentralized solutions, using multicasting as means of communication and signaling (e.g.…”

A MIP-P2P based architecture for application mobility

“…Most CASAM-systems (Roam [6]; an unnamed system by Bandelloni and Paternò [2]; Sparkle [22]; Gaia [19]; MDAgent [23]; SAMProc [21]; MSP [10]) are centralized, to an high extent relying on server-side components. Such an architecture makes the system very sensible to disturbances in Internet connection, thus canceling out one of the most important strengths of application mobility, namely a lesser degree of Internet dependency (for instance compared to the usage of similar cloud applications).…”