ROCS: a remotely provisioned OSGi framework for ambient systems

Abstract

Abstract-One of the challenges of ambient systems lies in providing all the available services of the environment to the ambient devices, even if they do not physically host those services. Although this challenge has come to find a solution through cloud computing, there are still few devices and operating systems that enable applications execution by only uploading the required components into the runtime environment.The ROCS (Remote OSGi Caching Service) framework is a novel proposal which relies on a heavy-weighted standard Java/OSGi stack. It is distributed between class servers and ambient devices to provide full functionalities to resource-constrained environments. The ROCS framework provides improvements in two areas. First, it defines a minimal bootstrap environment that runs a standard Java/OSGi stack. Secondly, it provides an architecture for loading any necessary missing class from remote servers into memory at runtime.Our first results show similar performances when classes are either remotely downloaded into the main memory from a local network or from a flash drive. These results suggest a way to design minimalistic middleware that dynamically obtain their applications from the network as a first step towards cloud-aware operating systems.

On the design of a flexible software platform for in-building OTT service provisioning

“…Various implementations of the standard are available, such as Eclipse Equinox [11] and Apache Felix [12]. Frénot et al [13] describe an extension to OSGi to support context awareness in distributed environments. A few concepts may be extrapolated to our platform, but we refrain from this so as not to overcomplicate the model.…”

Various Extensions for the Ambient OSGi Framework

“…The Remotely Provisioned OSGi framework for Ambient Systems [6] project leverages a very simple standard Java principle which is that of remote classes loading. Before starting the activator of a bundle, the OSGi framework performs some activities.…”

“…MOSGi Management (Royon & Frénot, 2007;Fleury & Frénot, 2003;Frénot et al, 2008) POSGi Management (Frénot & Royon, 2005) VOSGi Runtime (Royon et al, 2006) Suspend & Resume Runtime (Dunklau & Frénot, 2009) iJVM Runtime (Geoffray et al, 2009) ROCS Runtime (Frénot et al, 2010) AxSel Runtime (Ben Hamida et al, 2008) SFelix Security (Parrend & Frénot, 2006, 2007b Unsecured Bundle Catalog Security (Parrend & Frénot, 2007a, 2008a, 2008c Hardened OSGi Security Geoffray et al, 2009) CBAC Security (Parrend & Frénot, 2008b) Specification implementation. Since iJVM impacts the underlying virtual machine it does not directly concern the OSGi framework.…”

Servicio para la resolución de dependencias de software basado en componentes

“…Extracto del constant pool de la clase Quickstart.Se propone entonces, compilar a partir de un proxy de la biblioteca, un representativo que contenga únicamente descriptores y firmas de las clases[40]. Luego, analizar y entregar sólo las clases que son referenciadas por el programa del usuario en las dependencias directas y transitivas, como se ilustra en el ejemplo de laFig.…”