Document Actions

Recent Results

Up one level

Compilation of recent results

Next 20 items » [1] 2 3 4 5

Components and Aspects Composition Planning for Ubiquitous Adaptive Services — by Mourad Alia — last modified 2010-06-03 11:13: In ubiquitous environments, resources limitations and ﬂuctuations combined with device mobility requires the dynamic adaptation of mobile applications. This paper reports on the extension of the MUSIC adaptation middleware with aspect-oriented programming support in order to handle cross-cutting adaptations. Basically, this extension speciﬁes an architectural model for deﬁning applications as a composition of aspects and components. The dynamic adaptation of an application in a given context is realised by selecting the appropriate component and aspect implementations using utility functions as a mean of optimising the overall QoS. The validation of our approach is assessed through the implementation of a security-based application on top of the MUSIC middleware. The performance measures shows that the aspect-enabled middleware provides the expected adaptations with regards to context variations.
An Adaptive Quality of Experience Framework for Home Network Services — by Mourad Alia — last modified 2010-06-03 11:05
Unanticipated Dynamic Adaptation of Mobile Applications — by Mohammad Ullah Khan — last modified 2010-06-01 12:48: Driven by the emergence of mobile and ubiquitous computing there is a growing demand for context-aware applications that can dynamically adapt to their runtime environment. Middleware support for providing such adaptation to mobile applications has been an attractive research and development issue for several years now. However, one of the major challenges to support adaptation is that they can not be always foreseen during the design time. In a ubiquitous computing environment, a number of mobile devices running adaptive applications supported by the instances of the same middleware may come and go in a particular adaptation domain in an unanticipated manner. Moreover, third party services may also appear and disappear with respect to that particular adaptation domain. In component-based application architectures, with the enhancement of integrating services, mobile applications may benefit from using the components that are provided by other users as well as using third party services. In an ideal case, for a user it should be sufficient to specify what he expects his application to do. At runtime the application will be composed of the available components and services within the adaptation domain. In practice, the core components may be provided by the application developer himself to ensure at least a minimum configuration of the application, while discovered components and services add flexibility of integrating new functionalities along with improving the quality of service. The basis of the work is the results of the research projects MADAM [1] and its successor, MUSIC [2] that I have been involved in. However, none of these projects explicitly addresses the unanticipated adaptation. In this thesis I will present an approach to handle such unanticipated adaptations through adopting and extending the support provided by those projects. I have developed both a conceptual solution, consisting of the approach to address the unanticipated adaptation along with a brief description of the middleware and guidelines for the application developers. I have also implemented an initial version of the middleware based on these concepts. The middleware is tested as a proof of the main concepts, promised to be provided by this work. In order to present a complete picture of the solution MUSIC results are also briefly introduced. Furthermore, I specify and clearly identify where and how that results are updated in this work. [1] Mobility and Adaptation–enabling Middleware (MADAM), project homepage: http://www.intermedia.uio.no/display/madam/Home (accessed on 03.11.2009) [2] Self-Adapting Applications for Mobile Users in Ubiquitous Computing Environments (MUSIC), http://www.ist-music.eu (accessed on 03.11.2009)
Mashing-up integrated location, social networks and recommendations: the POI Radar — by Massimo Valla — last modified 2010-06-01 11:40:  Users want to access user generated content and recommendations in a contextualized way while on the move. In this paper we illustrate the POI Radar service and its architecture, a mobile mashup of integrated location, social network and users’ recommendations to provide contextualized notifications of nearby Points Of Interest voted by user’s contacts. A description of the service scenario, architecture and its technical components is given, focusing on how information is mashed up with mobile technologies.
icin2009 — by Massimo Valla — last modified 2010-06-01 11:33
Testing self-adaptive applications with simulation of context events — by Nearchos Paspallis — last modified 2010-05-27 16:48: Modern trends in mobile computing have raised the expectations of users in terms of such features such as context-awareness and self-adaptiveness. With such capabilities, applications can autonomously sense their context and automate a number of tasks, effectively reducing the attention required by the end users. This paper presents a custom simulation engine, designed to support the testing of applications developed using the MUSIC platform. The simulation tool consists of a platform-independent server module, deployed along with the application, and a client module which is responsible for interpreting and executing the simulation script. The use of the tool is demonstrated in the scope of the SatMotion application, which is designed to assist satellite antenna installers with specialized functionality.
Exploiting Context in Location-Based Information Systems — by Nearchos Paspallis — last modified 2010-05-27 16:34
The Context API in the OMA Next Generation Service Interface — by Massimo Valla — last modified 2010-05-26 15:06: Application Platforms and related APIs are becoming the foundations for emerging eco-systems of online applications/services. End-users are more and more choosing devices and services based on the available offers in the respective eco-system. Attracting, and retaining, application developers and end-users to a networked platform is nowadays more and more depending on the features available to developers in the form of APIs and (e.g. cloud-based) execution environments rather than on the actual portfolio of services. The Open Mobile Alliance (OMA) Next Generation Service Interfaces (NGSI) is one cornerstone of evolving a network operator towards an application platform provider with open APIs. Within NGSI, the Context API enables access to a plethora of rich information about users, places, events, and things - all made available by or brokered through the network operator. This paper explains the OMA NGSI Context API and its rationale, describes the operations, and discusses typical use cases and benefits it can bring to operators and application developers.
D21.2 RATP trial applications, intermediate version — by Jacqueline Floch — last modified 2010-02-15 11:36: The MUSIC project aims at developing a comprehensive open-source software development framework that facilitates the development of self-adapting, reconfigurable software that seamlessly adapts to the highly dynamic user and execution context, and maintains a high level usefulness across context changes. In that context, the main purpose of the RATP trial is to assess the MUSIC development framework. In addition, the trial is a means to demonstrate and promote the MUSIC technology outside the project. The RATP trial will consist of a set of MUSIC demonstrators that relate to the metro traveller’s and employee’s needs and could be demonstrated using the RATP infrastructure. This deliverable provides specifications of the initial versions of the RATP trial applications, as developed in cycles 1 and 2 of the project. The applications will be extended in cycles 3 and 4, and the final versions of the applications will be described in the deliverable D21.3. The deliverable consists of four parts: Part A describes the Travel Assistant application that provides support to the RATP metro traveller for planning itineraries, ticket purchase, navigation and tourist information. Part B describes the PRM application that provides special assistance to RATP travellers with reduced mobility (e.g. sight and walking difficulties). Part C describes the IROP applications that provide medical treatment and communication support in an irregular operation situation. Part D describes the context plug-ins and services common to these applications. URL D21.2 RATP trial applications, intermediate version
D13.12 Telecom Italia’s MUSIC Exploitation:Mobile eTourism — by Nicoletta Salis — last modified 2010-02-11 15:30: MUSIC is a focused initiative with the goal of designing, developing and distributing an open-source software development framework, which enables developers to create context-aware mobile applications that dynamically and seamlessly adapt to changes in the user and execution context. As Telecom Italia (TI) is currently investigating and experiencing new services to support mobile users in their tourist activities, it sees mobile eTourism as the most proper opportunity to exploit the MUSIC results, by developing new eTourism services, benefiting from the adaptation and context-awareness functionalities already offered by the platform. In the context of mobile eTourism services application area and by analyzing the positioning of the possible competitors (both Telco and IT big players), this document reports TI’s choices and opportunities in its will to trial and bring to market new contextualized, self-adapted and Web2.0 services for tourists. By leveraging on innovative technologies promoting ICT convergence, TI would like to build a new offer for the tourism sector in order to contribute enhancing competitiveness. Support for public administrations and operators participating in the national tourism system (regions, provinces, cities of art, the managers of archaeological, cultural and food & wine paths, the consortia of municipalities and agencies, the Parks, …) is one of the goals that TI supports and for which it can provide technology and advanced models of enjoyment and participation. The first two chapters introduce the tourism sector (all over the world and in Italy), explain how the ICT and the mobile technologies are taking it towards the eTourism and the mobile eTourism and which opportunities have been seen by TI in this arena; chapter 4 explains more in detail how the direct (and not direct) TI’s competitors are moving in this area. In chapters 3 and 5 TI’s MUSIC exploitation and the benefits coming from the MUSIC project are well described together with different field trials performed in 2008-2009, by using some parts of the MUSIC middleware inserted in a more general TI’s eTourism platform. In the end, Chapter 6 reports the SWOT analysis of MUSIC in the eTourism services area. Keywords: eTourism, Mobile eTourism, MUSIC Exploitation Project Website: http://www.ist-music.eu
D2.4 Final Research Results on methods, languages, algorithms, and tools to modeling and management of context — by Massimo Valla — last modified 2010-02-11 15:30: This MUSIC deliverable collects the results of research activities done in the area of context-awareness in Work package 2 in the third year of the project. Similarly to previous deliverables from Work package 2, this document has been organized as a collection of scientific papers. Since the basic technologies on which the MUSIC context middleware is architected have already been addressed in previous research cycles, the research reported in this deliverable has primarily focused on collecting experience and feedback obtained while implementing the MUSIC context middleware, plug-ins, tools and trial applications, and proposing improvements based on this feedback. However, some chapters also present new results in the area of the MUSIC context middleware, not yet touched in previous research cycles, and required by the feature-based planning of activities in the project. Keywords: MUSIC, Context, Context-awareness, State-of-the-Art, Requirements, Adaptive systems, Middleware, Modeling, Semantics, Context Reasoning, Context Learning, Model-driven development, Profiles
D23.2 SatCom installation trial initial implementation and evaluation — by Pedro Antonio Ruiz Gonzalez — last modified 2010-02-09 16:51: The MUSIC project aims at developing a comprehensive open-source software development framework that facilitates the development of self-adapting, reconfigurable software that seamlessly adapts to the highly dynamic user and execution contexts, and maintains a high level usefulness across context changes We aim for an adaptation model that clearly separates the adaptation mechanisms and policies from the application logic. This will enable the provision of adaptive behaviour as generic and reusable services, thus relieving the application programmer from much of the complex task of programming adaptation management and mechanisms. The main objective of this deliverable is to report the initial implementation of SatCom application, which is used to assess the MUSIC development framework and is also a means to demonstrate and promote the MUSIC technology outside the project. Furthermore, this implementation on top of the MUSIC middleware allows deriving a set of properties and information that are used to evaluate the MUSIC platform, which is reported through WP20. The SatCom application provides an integrated tool that eases the installation process of bidirectional satellite antennas. For this purpose, the application offers three main blocks of functionalities: PlaInstallation: This block manages and coordinates the workforce, provides installer with dynamic routes and launches other applications in different context situation. Adaptive SatMotion: This block is used in the alignment process of bidirectional satellites antennas, and provides the best operation mode and optimizes the resources usage according to the different context situations. Adap2Nav: This block guides the installer through their way to installation sites, and provides optimal user interfaces and automation mechanisms to offer the user optimal usability in adverse conditions. The document details the functioning of SatCom, explains how MUSIC methodologu can improve its functioning and finally provide the design and report the implementation of SatCom in MUSIC.
D20.3 Evaluation Framework Specification (Final) — by Pedro Antonio Ruiz Gonzalez — last modified 2010-02-09 16:43: The objective of this document is to specify an evaluation framework which will be used by the trial applications to assess the solution provided by the MUSIC platform. This document refines the initial evaluation framework presented in deliverable D20.1, based on the experience of using the initial framework, and includes the features that were not considered in the initial version. We define the evaluation framework from two perspectives: On the one hand, we specify a framework to evaluate MUSIC platform as a development environment to add adaptability to applications, i.e., we consider the evaluation from the developer point of view. For this we analyze the features that should be offered the MUSIC modelling notations, methodologies and tools. The analysis includes usability, coverage of the adaptation domain problem and automation aspects. On the other hand, we specify a framework for the evaluation of the MUSIC platform from the end user perspective. For this framework, we consider aspects of the platform at runtime in such a way we can estimate the end user satisfaction. The framework includes the determination of validation criteria and key quality indicators for measuring the achieved quality of the middleware with respect to a set of adaptation requirements. The criteria are quantifiable and comparable in order to ensure comparable results between different increments of the middleware. The evaluation framework aims at guiding the assessment of the MUSIC platform by trial developers with different needs and various experiences. Therefore we provide a flexible framework that can be customized to the specific characteristics of the targeted applications and to the developer profiles.
D20.1 Intermediate Evaluation Framework — by Pedro Antonio Ruiz Gonzalez — last modified 2010-02-09 16:26: The objective of this document is to specify an evaluation framework which will be used by the trial applications to assess the solution provided by the MUSIC platform. We define the evaluation framework from two perspectives. On the one hand, we specify a framework to evaluate MUSIC platform as a development environment to add adaptability to application, i.e., the evaluation from the developer point of view. For this we analyze the features that should offer the proposed tools and design language extensions in terms of usability, coverage of the adaptation domain problem and automation aspects. Both the modelling methodologies and the development framework will be validated as assisted environments for creating adaptive applications. On the other hand, we also specify a framework for the evaluation of MUSIC platform from the end user perspective. For this framework, we consider aspects of the platform in run time in such a way we can estimate the end user satisfaction. Furthermore, this framework includes the determination of the validation criteria and key quality indicators for measuring the achieved quality of the developed middleware in relation to its adaptation requirements. The defined criteria will be quantifiable and comparable to insure comparable results between different increments of the middleware. Both evaluation frameworks will guide the assessment of the MUSIC platform by the trials developers, so that we provide the needed flexibility to be customized to the specific characteristics of the targeted applications and developer profiles.
D4.3 System design of the MUSIC architecture — by Paolo Barone — last modified 2010-04-06 10:54: MUSIC is a focused initiative with the goal of designing, developing and distributing an open-source software framework, which enables developers to create context-aware mobile applications that dynamically and seamlessly adapt to changes in the user and execution context. MUSIC aims at defining a methodology to support the design and modelling of self-adaptive applications, and at providing a distributed architecture and middleware and tools to support the efficient execution of these applications in ubiquitous environments. The goal of Work Package 4 “Architecture” is designing the MUSIC architecture. It targets the above mentioned mobile and ubiquitous environments which are highly distributed, dynamic and heterogeneous. The purpose of this document is to define the final design of the MUSIC architecture. It specifies the functionalities of major architectural components and their relationship, and takes into account the final results from Work Packages 1 (“Adaptation”), 2 (“Context”) and the feedback coming from the first software development cycle in WP5 - based on the intermediate version of the MUSIC architecture described in D4.2. The final design focuses on the notions of service-oriented self-adaptations and self-adaptability of the MUSIC architecture, SLA negotiation and distribution of context information. The final design of the MUSIC architecture will be used as input for the Work Packages 5 (“Middleware”) and 7 (“Tools”) to develop the final version of the MUSIC middleware and tools.
D13.11 MUSIC & ANDROID — by Nearchos Paspallis — last modified 2010-02-09 14:54: This white paper investigates the Open Handset Alliance’s (OHA) Android platform and how its underlying technology can benefit the MUSIC technology and vice versa. We provide an evaluation of how the Android platform works, focusing on the functioning that is mostly related to the MUSIC platform. It should be noted that while MUSIC consists of both a development framework (MUSIC Studio) and a middleware (MUSIC Runtime Environment) this paper focuses primarily at the comparison between the Android platform and the MUSIC Runtime Environment. As it is argued in this paper, while the two platforms have significant differences, they can nevertheless help each other either practically (i.e., by porting code) or fundamentally (i.e., by porting ideas). Finally, it is shown that the MUSIC platform can be ported to the Android platform, but this introduces some noteworthy limitations which are also discussed.
D6.4 Modelling notation and software development method for adaptive applications in ubiquitous computing environments — by Michael Wagner — last modified 2010-02-09 14:36: MUSIC is an initiative that develops a comprehensive open-source software development framework facilitating the development of self-adapting, reconfigurable software that seamlessly adapts to the highly dynamic user and execution context, typical of mobile and ubiquitous computing and thus maintains a high level of usefulness across context changes. For this purpose, MUSIC provides a methodology for the model-driven development of self-adapting applications integrating modelling language enhancements for the specification of context dependencies, application variability and adaptation capabilities. This deliverable reflects the work done in WP6 for Tasks 6.1 and 6.2 in the third year of the project. Task 6.1 deals with the definition of a modelling notation to express the adaptation capabilities of an application. The modelling notation is based on the requirements derived from MUSIC work packages 1 and 2 as well as the list of MUSIC Features. Task 6.2 deals with providing a methodology for the model-driven development of selfadapting applications integrating modelling language enhancements for the specification of context dependencies, application variability and adaptation capabilities. The methodology utilizes the modelling notation and shows how tools can be incorporated, in order to ease the development task. Therefore, this deliverable has to be considered as important basis for WP7 work that provides the development tool suite (MUSIC Studio) supporting the methodology. The development methodology not only provides a step-by-step guideline to specify the application’s context dependencies, variability and domain model, but also covers the transformation of models to source code, the deployment of applications on the middleware and the testing and validation of the expected adaptation capabilities. Keywords: Adaptive application, context-awareness, context modelling, methodology, modelling notation, model-driven development, UML Profile, service orientation, ontology, OWL, OWL-S, WSDL.
D13.6 MUSIC vision and solutions — by Svein Hallsteinsen — last modified 2010-02-09 14:22: With the widespread proliferation of mobile and pervasive computing, people increasingly use applications while away from their desktop. This creates a need for applications that works properly also in mobile settings, characterised by dynamic variations in user needs and computing resources. Traditional software development approaches provides little support for tackling such dynamic variation in requirements and resource constraints. MUSIC is a focused initiative aiming to alleviate the development of context-aware mobile applications that dynamically and seamlessly adapt to changes in the user and execution context. This white paper describes the vision of the MUSIC project and the solutions we have developed to fulfil it. Furthermore it provides an outlook on how we envisage the continued development of these solutions. It intends to give software developers a first introduction to the broad spectrum of results that can best be understood collectively as a new software development framework for applications meant to operate in dynamic environments.
D7.2 MUSIC Studio and Tools (initial version) — by Yves Vanrompay — last modified 2010-02-09 14:24
D5.4 MUSIC middleware software with documentation (version 2) — by Jorge Lorenzo — last modified 2010-02-09 13:58: This document belongs to the deliverable 5.4: “MUSIC middleware software with documentation (version 2)”which is basically a software deliverable. D5.4 is made up of (a) Java source code, (b) Javadoc documentation, (c) binaries and (d) the current document. The MUSIC project develops an open-source software development framework for the implementation of selfadapting, reconfigurable software that adapts to the dynamic user and execution context. This deliverable is the result of the middleware development during the third year of the project according to the design of the MUSIC architecture provided in D4.3. In this release most of the planned functionality has been implemented, but further improvements and bug fixes are planned during the last half year of the project. The purpose of this document is to continue the documentation of D5.2, paying special attention to the configuration of the MUSIC middleware and how to deploy it in different environments. For a more detailed documentation of the architecture, see D4.3. A set of annexes has been compiled to support middleware developers as well as third parties. These annexes comprise: (a) MUSIC in mobile devices, (b) the communication services, and (c) a guide to set up the development environment. Keywords: Middleware, OSGi, bundle, component, service, SOA, context, context distribution, remoting, service discovery, adaptation, SIP.

Next 20 items » [1] 2 3 4 5

Sections

Personal tools

Document Actions

Recent Results