2008
Journal article
Restricted
The PERSONA framework for supporting context-awareness in open distributed systems
Fidesvalero A, Freddi M, Furfari F, Tazari M
Although several context-aware systems have been devel- oped within the past 15 years that use contextual info captured from the physical environment in combination with system usage context and personalization data, it seems that a breakthrough has not been achieved yet, because still more and more research pro jects work on adequate so- lutions for supporting context-awareness. It seems that the ma jor dif- ficulties have to do with a hurdle called context modeling and its ex- tensibility as well as the open nature of such systems that must allow for dynamic pluggability of components distributed over several physical nodes. This paper presents the related work results from the EU pro ject PERSONA that feature remarkable conceptual solutions for the above issues. It consists of a middleware solution for open distributed systems dealing with seamless connectivity and adequate support for interoper- ability that makes use of ontological technologies and defines appropriate protocols along with an upper ontology for sharing context. A set of stan- dard platform components together with a general conceptual solution for binding ultra-thin nodes top off the presented approach.DOI: 10.1007/978-3-540-89617-3_7
Metrics:
Fidesvalero A, Freddi M, Furfari F, Tazari M
Although several context-aware systems have been devel- oped within the past 15 years that use contextual info captured from the physical environment in combination with system usage context and personalization data, it seems that a breakthrough has not been achieved yet, because still more and more research pro jects work on adequate so- lutions for supporting context-awareness. It seems that the ma jor dif- ficulties have to do with a hurdle called context modeling and its ex- tensibility as well as the open nature of such systems that must allow for dynamic pluggability of components distributed over several physical nodes. This paper presents the related work results from the EU pro ject PERSONA that feature remarkable conceptual solutions for the above issues. It consists of a middleware solution for open distributed systems dealing with seamless connectivity and adequate support for interoper- ability that makes use of ontological technologies and defines appropriate protocols along with an upper ontology for sharing context. A set of stan- dard platform components together with a general conceptual solution for binding ultra-thin nodes top off the presented approach.DOI: 10.1007/978-3-540-89617-3_7
Metrics:
See at:
doi.org 
| CNR IRIS | CNR IRIS | www.springerlink.com
2008
Journal article
Open Access
Realizing ambient assisted living spaces with the PERSONA platform
Furfari F, Tazari M
The PERSONA project is working on a general-purpose technological platform for developing and deploying Ambient Assisted Living (AAL) services. Initial results include middleware that supports self-organization in an ad-hoc manner and a reference architecture for building AAL spaces.Source: ERCIM NEWS, vol. 74, pp. 47-48
Project(s): PRACE
Furfari F, Tazari M
The PERSONA project is working on a general-purpose technological platform for developing and deploying Ambient Assisted Living (AAL) services. Initial results include middleware that supports self-organization in an ad-hoc manner and a reference architecture for building AAL spaces.Source: ERCIM NEWS, vol. 74, pp. 47-48
Project(s): PRACE
See at:
ercim-news.ercim.org 
| CNR IRIS | CNR IRIS
2004
Conference article
Restricted
DomoML: the definition of a standard markup for interoperability of human home interactions
Furfari F, Sommaruga L, Soria C, Fresco R
DomoML is a mark-up language aimed at the definition of interoperability standard for domestic resources within the NICHE project (Natural Interaction in Computerised Home Environment). The project focuses on human language as a means for mediating user interaction with the home environment, enabling a user to control, query and program devices. Various heterogeneous components are going to take part in this architecture, and DomoML is the glue which allows them to be interfaced. It is a mark-up language intended to define a semantic layer on which novel value-added services (agents) can easily be built.DOI: 10.1145/1031419.1031430
Metrics:
Furfari F, Sommaruga L, Soria C, Fresco R
DomoML is a mark-up language aimed at the definition of interoperability standard for domestic resources within the NICHE project (Natural Interaction in Computerised Home Environment). The project focuses on human language as a means for mediating user interaction with the home environment, enabling a user to control, query and program devices. Various heterogeneous components are going to take part in this architecture, and DomoML is the glue which allows them to be interfaced. It is a mark-up language intended to define a semantic layer on which novel value-added services (agents) can easily be built.DOI: 10.1145/1031419.1031430
Metrics:
2007
Conference article
Restricted
Open source and product lines architectures
Bermejo J, Golatowski F, Furfari F, Zeeb E
The high level of customizability together with other business competitive advantages like reduced cost of acquisition and decreased vendor lock-in are pushing the open source adoption process. In parallel, the availability of the source code encourages the reuse. This process is evolving to an optimization of architectures that is meeting product line engineering. The product line maturity framework developed during ITEA-Families project identifies four key dimensions (business, architecture, process and organisation) to assess the maturity stage in product line development. This paper analyses the impact of open source within the architecture dimension focussing on the middleware and variability support. It identifies major differences from the conventional approach in product line development introducing Osiris R&D platform as an effort for defining an infrastructure supporting product lines for multiple domains. It gathers preliminary results from open source related research from Cosiris [1] (ITEA-Cosi [2] & ITEA-Osiris [3] projects syndication) ITEA-Sirena [4] and Domoware [5] projects addressing foundations for ambient intelligence applications.
Bermejo J, Golatowski F, Furfari F, Zeeb E
The high level of customizability together with other business competitive advantages like reduced cost of acquisition and decreased vendor lock-in are pushing the open source adoption process. In parallel, the availability of the source code encourages the reuse. This process is evolving to an optimization of architectures that is meeting product line engineering. The product line maturity framework developed during ITEA-Families project identifies four key dimensions (business, architecture, process and organisation) to assess the maturity stage in product line development. This paper analyses the impact of open source within the architecture dimension focussing on the middleware and variability support. It identifies major differences from the conventional approach in product line development introducing Osiris R&D platform as an effort for defining an infrastructure supporting product lines for multiple domains. It gathers preliminary results from open source related research from Cosiris [1] (ITEA-Cosi [2] & ITEA-Osiris [3] projects syndication) ITEA-Sirena [4] and Domoware [5] projects addressing foundations for ambient intelligence applications.
2005
Conference article
Open Access
DomoML-env: an ontology for Human Home Interaction
Furfari F, Perri A, Sommaruga L
Household appliances have fast changed in the last decades and achieved an important role in the ordinary home daily activity, e.g. in assisting people during cooking, phone calls, house monitoring, etc. Pervasiveness and interoperability are interesting aspects related to domestic devices. The semantic web is here considered to make an infrastructural support for resource interoperability by providing a domestic environment ontology, called DomoML-env, for human home interactions aiming to connect household appliances each other, to exchange their services and information, and to overcome or extend their individual capabilities. The paper focuses on the development of an extensible ontology in the home automation field, open to the integration of other more specific ontologies.
Furfari F, Perri A, Sommaruga L
Household appliances have fast changed in the last decades and achieved an important role in the ordinary home daily activity, e.g. in assisting people during cooking, phone calls, house monitoring, etc. Pervasiveness and interoperability are interesting aspects related to domestic devices. The semantic web is here considered to make an infrastructural support for resource interoperability by providing a domestic environment ontology, called DomoML-env, for human home interactions aiming to connect household appliances each other, to exchange their services and information, and to overcome or extend their individual capabilities. The paper focuses on the development of an extensible ontology in the home automation field, open to the integration of other more specific ontologies.
See at:
CNR IRIS | sunsite.informatik.rwth-aachen.de | CNR IRIS
2005
Other
Restricted
AKOGRIMO - D4.3.1 - Architecture of the GRID Infrastructure Services Layer
Albacar J., Bocci D., Bori R., Chatzis S., Cirillo G., Furfari F., Halkos D., Jähnert J., Kyriazis D., Laria G., Litke A., Martrat J., Mediavilla I. A., Mueller I., Negro G., Rovezzi A., Serrano M., Skoutas D.
This document describes the architecture that will be adopted within the WP4.3 Grid Infrastructure Services Layer of the Akogrimo project. It has a relation to the overall architecture already presented in Deliverable D3.1.1 but its aim is to provide a more detailed view of the architecture of the Grid infrastructure itself. The document gives an overview of the Open Grid Services Architecture (OGSA) which is the basis upon which the architecture is built. In the sequel it presents the Web Services Resource Framework (WSRF) and some implementations that are met in the current trends of the appropriate players/stakeholders. The document includes an overview of the requirements that need to be met by an OGSA based Grid in the project and shows in a layered approach the positioning of the WP4.3 components within the Akogrimo overall architecture. The components that have been identified as building blocks of the WP4.3 architecture are the Execution Management Services component, Data Management, Monitoring component, Service Level Agreement Enforcement, Policy Manager, Metering component and the Security framework that will be applied. The discussion on the modules concerns the technologies that are applied as well as the interfaces they use to interact with each other. Finally, the Annex presents several cases and examples in order to clarify the functionality and the interactions of these modules.
Albacar J., Bocci D., Bori R., Chatzis S., Cirillo G., Furfari F., Halkos D., Jähnert J., Kyriazis D., Laria G., Litke A., Martrat J., Mediavilla I. A., Mueller I., Negro G., Rovezzi A., Serrano M., Skoutas D.
This document describes the architecture that will be adopted within the WP4.3 Grid Infrastructure Services Layer of the Akogrimo project. It has a relation to the overall architecture already presented in Deliverable D3.1.1 but its aim is to provide a more detailed view of the architecture of the Grid infrastructure itself. The document gives an overview of the Open Grid Services Architecture (OGSA) which is the basis upon which the architecture is built. In the sequel it presents the Web Services Resource Framework (WSRF) and some implementations that are met in the current trends of the appropriate players/stakeholders. The document includes an overview of the requirements that need to be met by an OGSA based Grid in the project and shows in a layered approach the positioning of the WP4.3 components within the Akogrimo overall architecture. The components that have been identified as building blocks of the WP4.3 architecture are the Execution Management Services component, Data Management, Monitoring component, Service Level Agreement Enforcement, Policy Manager, Metering component and the Security framework that will be applied. The discussion on the modules concerns the technologies that are applied as well as the interfaces they use to interact with each other. Finally, the Annex presents several cases and examples in order to clarify the functionality and the interactions of these modules.
2008
Other
Restricted
Full version of ambient assisted architecture specification
Tazari S, Furfari F, Freddi M, Amoretti M, Zanichelli F
This report is the deliverable specifying a reference-architecture for AAL spaces. To motivate the proposed architecture, we first summarize the intermediate results along the way covered within the first year of the project towards this specification. Then we introduce a physical and a logical architecture for AAL spaces at an abstract level and explain the basic ideas and concepts within it. The abstract physical architecture treats an AAL space as a dynamic ensemble of networked nodes and the logical architecture abstracts all functionality not leading to context, input, or output events (or the direct processing of such events) as service. Hence, the proposed architecture is service oriented.
Tazari S, Furfari F, Freddi M, Amoretti M, Zanichelli F
This report is the deliverable specifying a reference-architecture for AAL spaces. To motivate the proposed architecture, we first summarize the intermediate results along the way covered within the first year of the project towards this specification. Then we introduce a physical and a logical architecture for AAL spaces at an abstract level and explain the basic ideas and concepts within it. The abstract physical architecture treats an AAL space as a dynamic ensemble of networked nodes and the logical architecture abstracts all functionality not leading to context, input, or output events (or the direct processing of such events) as service. Hence, the proposed architecture is service oriented.
2009
Other
Restricted
PERSONA IR3.7.2 - First Technical Evaluation Report
Lázaro J, Huertas S, Furfari F, Amoretti M, Tazari S
The objective of the current deliverable is to make a first evaluation of the technical results of PERSONA project. The current evaluation is based on the requirements defined in IR3.7.1, and it is focused on the platform (middleware plus platform components) without taking into consideration neither software components nor hardware components directly connected to AAL Services. The evaluation of AAL Services and hardware components will be reported in IR3.7.3. In this IR an update of the Risk Registry from IR3.7.1 is provided.Project(s): Perceptive spaces promoting independent aging
Lázaro J, Huertas S, Furfari F, Amoretti M, Tazari S
The objective of the current deliverable is to make a first evaluation of the technical results of PERSONA project. The current evaluation is based on the requirements defined in IR3.7.1, and it is focused on the platform (middleware plus platform components) without taking into consideration neither software components nor hardware components directly connected to AAL Services. The evaluation of AAL Services and hardware components will be reported in IR3.7.3. In this IR an update of the Risk Registry from IR3.7.1 is provided.Project(s): Perceptive spaces promoting independent aging
2009
Other
Restricted
PERSONA IR4.3.2. - Second Period Dissemination Activity Report
Furfari F
This document describes the Second Period Dissemination Activity Report of the PERSONA project. Numerous dissemination activities have been undertaken during this period to widely spread the PERSONA project results to the relevant international scientific community and to increase public awareness of its potentials and benefits for the elderly based on Ambient Assisted Living framework. The Consortium"s has disseminated extensively the existence of PERSONA project and its goals, not only within Europe but also internationally, in order to present Europe as a major world force in the relevant scientific and industrial field and to open international markets to European companies. Thus, dissemination has addressed the international community on scientific and industrial/commercial level and served as a promotion of the project to experts (i.e. product or project managers, researchers of various interests, general public, etc.). Towards this goal the following actions have been taken for disseminating the PERSONA project results: i. Presentation of main result through the World Wide Web ii. Production of dissemination material for the PERSONA project (brochure/leaflet/fact sheet, poster, video film, multimedia contents) iii. Publications in Technical magazines iv. Participation in Technical Exhibitions, Conferences and major fairs focusing on products relative to the results of the project v. Involvement of Academic and Industrial Key Actors in the dissemination strategy vi. Participation in Social Networks where PERSONA will be announced Dissemination activities are important for the Consortium also on a partner level, that is, internal communication to assure knowledge sharing and a common understanding. Making the Consortium partner"s competencies known can prove beneficial for promoting their activities as well. Regardless the specific partner contribution in the Work Package, all partners have taken part in dissemination activities even on a different level. This contribution takes several forms, ranging from artistic design in the dissemination material to scientific papers on PERSONA project at international, European and local workshops, exhibitions and conferences. Thus it has been essential that all partners had a preliminary idea of their planned dissemination activities either for PERSONA purposes exclusively or for general purposes where PERSONA project has been shown. This report is a working document that will be periodically updated along PERSONA project life. It will be updated at the end of the project (month 42-june 2010) with the release of the "Deliverable 4.3.-Final Dissemination Report". Moreover, PERSONA Dissemination Report has been reviewed to include the suggestions and guidelines received from the European Commission to increase the overall visibility and publicity around all the e-Inclusion projects. All PERSONA project Consortium has a strong commitment on disseminating PERSONA project and its role within the Strategic Objective "AAL for the Ageing Society" of the 6th Framework Program of the European Commission.Project(s): HEARTCYCLE
Furfari F
This document describes the Second Period Dissemination Activity Report of the PERSONA project. Numerous dissemination activities have been undertaken during this period to widely spread the PERSONA project results to the relevant international scientific community and to increase public awareness of its potentials and benefits for the elderly based on Ambient Assisted Living framework. The Consortium"s has disseminated extensively the existence of PERSONA project and its goals, not only within Europe but also internationally, in order to present Europe as a major world force in the relevant scientific and industrial field and to open international markets to European companies. Thus, dissemination has addressed the international community on scientific and industrial/commercial level and served as a promotion of the project to experts (i.e. product or project managers, researchers of various interests, general public, etc.). Towards this goal the following actions have been taken for disseminating the PERSONA project results: i. Presentation of main result through the World Wide Web ii. Production of dissemination material for the PERSONA project (brochure/leaflet/fact sheet, poster, video film, multimedia contents) iii. Publications in Technical magazines iv. Participation in Technical Exhibitions, Conferences and major fairs focusing on products relative to the results of the project v. Involvement of Academic and Industrial Key Actors in the dissemination strategy vi. Participation in Social Networks where PERSONA will be announced Dissemination activities are important for the Consortium also on a partner level, that is, internal communication to assure knowledge sharing and a common understanding. Making the Consortium partner"s competencies known can prove beneficial for promoting their activities as well. Regardless the specific partner contribution in the Work Package, all partners have taken part in dissemination activities even on a different level. This contribution takes several forms, ranging from artistic design in the dissemination material to scientific papers on PERSONA project at international, European and local workshops, exhibitions and conferences. Thus it has been essential that all partners had a preliminary idea of their planned dissemination activities either for PERSONA purposes exclusively or for general purposes where PERSONA project has been shown. This report is a working document that will be periodically updated along PERSONA project life. It will be updated at the end of the project (month 42-june 2010) with the release of the "Deliverable 4.3.-Final Dissemination Report". Moreover, PERSONA Dissemination Report has been reviewed to include the suggestions and guidelines received from the European Commission to increase the overall visibility and publicity around all the e-Inclusion projects. All PERSONA project Consortium has a strong commitment on disseminating PERSONA project and its role within the Strategic Objective "AAL for the Ageing Society" of the 6th Framework Program of the European Commission.Project(s): HEARTCYCLE
2010
Other
Open Access
universAAL - universAAL integration and testing strategy and issue tracker
Gorman J., Bellenguer Querol L., Hanke S., Furfani F., Maglaveras N., Tazari S., Benc I., Peres Y., Schmidt A., Petkovic M., Valles J., Wanscher C. E., Hackbarth K., Obermeisser R., Lázaro-Ramos J. P., Boos H., Vera C.
This deliverable deals with the integration of components from other projects (or newly created) and their testing, for which a set of tools and development guidelines are studied and selected. These tools and procedures set up a development process that each piece of software must follow to be integrated into universAAL, ranging from the very inception of the process, selection of existing components, code development, testing and deployment. This document first starts with the common decisions a software project must make at its beginning, like deciding the code language and running framework. For universAAL, Java and OSGi have been selected due to their usage in most of the input projects. In international projects like universAAL, with so many different partners, it is necessary to use tools that help in synchronizing the work of developers when coding, building and documenting the software. In this aspect, we will use Maven for building, GForge for development management, Subversion for code sharing, and scripted HTML and Wiki documentations. A set of requirements should be addressed throughout the whole process in order to not only properly manage the project but also make it a successful open source one. The IPR management section gives recommendations and advice about how to decide for a license for the software developed at universAAL, despite it is not its purpose to decide which one must be use. It also advices on how to behave when using third-party software, as this may have different licenses, and defines a procedure and registry to deal with this issue. Lastly, it gives guidelines to follow when writing code in regard to the license applied. Development Environment section specifies how to properly use Eclipse IDE, by installing some plugins that help developers maintain an integrated interaction with the rest of tools and guidelines, namely Subclipse, ADJT, M2Eclipse and Pax runner. Other tools and advices are commented related to style and code documentation. Project Management and Issue Tracker is a section that introduces GForge as main managing tool for the development of code. It covers a wide range of features of project management, from version control to documentation and, one of the most important, includes an issue tracker to keep trace of the appearing bugs and issues and manage them as they are solved. The Integration Strategy defines the process through which an external software component is adopted into universAAL reference implementation, by passing different approval stages, adaptation and evaluation. In the case of a new development, it describes the path it would follow in an analogous way. Responsibilities are adjudicated for each of the major releases in universAAL, by describing how to lead the release plan. Integration Strategy also contains the risks of its process identified so far along with possible mitigation strategies. The Testing and Deployment Strategy describes the tools and techniques used for automated code testing that developers should follow (JUnit, for instance, among others), along with the tools selected for deployment (Nexus)Source: Project report, UniversAAL, Deliverable D2.3-A, 2010
Gorman J., Bellenguer Querol L., Hanke S., Furfani F., Maglaveras N., Tazari S., Benc I., Peres Y., Schmidt A., Petkovic M., Valles J., Wanscher C. E., Hackbarth K., Obermeisser R., Lázaro-Ramos J. P., Boos H., Vera C.
This deliverable deals with the integration of components from other projects (or newly created) and their testing, for which a set of tools and development guidelines are studied and selected. These tools and procedures set up a development process that each piece of software must follow to be integrated into universAAL, ranging from the very inception of the process, selection of existing components, code development, testing and deployment. This document first starts with the common decisions a software project must make at its beginning, like deciding the code language and running framework. For universAAL, Java and OSGi have been selected due to their usage in most of the input projects. In international projects like universAAL, with so many different partners, it is necessary to use tools that help in synchronizing the work of developers when coding, building and documenting the software. In this aspect, we will use Maven for building, GForge for development management, Subversion for code sharing, and scripted HTML and Wiki documentations. A set of requirements should be addressed throughout the whole process in order to not only properly manage the project but also make it a successful open source one. The IPR management section gives recommendations and advice about how to decide for a license for the software developed at universAAL, despite it is not its purpose to decide which one must be use. It also advices on how to behave when using third-party software, as this may have different licenses, and defines a procedure and registry to deal with this issue. Lastly, it gives guidelines to follow when writing code in regard to the license applied. Development Environment section specifies how to properly use Eclipse IDE, by installing some plugins that help developers maintain an integrated interaction with the rest of tools and guidelines, namely Subclipse, ADJT, M2Eclipse and Pax runner. Other tools and advices are commented related to style and code documentation. Project Management and Issue Tracker is a section that introduces GForge as main managing tool for the development of code. It covers a wide range of features of project management, from version control to documentation and, one of the most important, includes an issue tracker to keep trace of the appearing bugs and issues and manage them as they are solved. The Integration Strategy defines the process through which an external software component is adopted into universAAL reference implementation, by passing different approval stages, adaptation and evaluation. In the case of a new development, it describes the path it would follow in an analogous way. Responsibilities are adjudicated for each of the major releases in universAAL, by describing how to lead the release plan. Integration Strategy also contains the risks of its process identified so far along with possible mitigation strategies. The Testing and Deployment Strategy describes the tools and techniques used for automated code testing that developers should follow (JUnit, for instance, among others), along with the tools selected for deployment (Nexus)Source: Project report, UniversAAL, Deliverable D2.3-A, 2010
See at:
ISTI Repository | CNR ExploRA
2011
Journal article
Restricted
universAAL: an open platform and reference specification for building AAL systems
Furfari Francesco, Tazari Mohammadreza, Eisemberg Vadim
universAAL is a European research project that aims at creating an open platform and standards which will make it technically feasible and economically viable to develop Ambient Assisted Living solutions. The project follows an open source license model and preliminary results are already available
Furfari Francesco, Tazari Mohammadreza, Eisemberg Vadim
universAAL is a European research project that aims at creating an open platform and standards which will make it technically feasible and economically viable to develop Ambient Assisted Living solutions. The project follows an open source license model and preliminary results are already available
2011
Journal article
Open Access
AALOA - Towards a shared infrastructure for realizing AAL solutions
Furfari F, Wichert R, Guillen S, Gorman, J
Ambient Assisted Living (AAL) has great potential to positively influence the lives of many people. But the impacts so far have been less than hoped, partly due to fragmentation of research efforts and the lack of a standardized approach for developers. To address this, we are forming AALOA (the AAL Open Association), and invite you to join in our efforts
Furfari F, Wichert R, Guillen S, Gorman, J
Ambient Assisted Living (AAL) has great potential to positively influence the lives of many people. But the impacts so far have been less than hoped, partly due to fragmentation of research efforts and the lack of a standardized approach for developers. To address this, we are forming AALOA (the AAL Open Association), and invite you to join in our efforts
See at:
ercim-news.ercim.eu | CNR IRIS | CNR IRIS
2011
Other
Open Access
universAAL - execution environment installation packages and hardware abstraction
Furfari F
Deliverable 2.1 mainly consists of software that is supposed to create the basic collaborative environment based on which different resources embedded within or otherwise distributed throughout an AAL space can communicate on a secure basis. The development of this software is organized within Task 2.1 "Create the universAAL Execution Environment and Hardware Abstraction Layer". D2.1 also consists of a report that provides an overview of the work done in Task 2.1 towards the development of the targeted software.Project(s): UNIVERSAAL
Furfari F
Deliverable 2.1 mainly consists of software that is supposed to create the basic collaborative environment based on which different resources embedded within or otherwise distributed throughout an AAL space can communicate on a secure basis. The development of this software is organized within Task 2.1 "Create the universAAL Execution Environment and Hardware Abstraction Layer". D2.1 also consists of a report that provides an overview of the work done in Task 2.1 towards the development of the targeted software.Project(s): UNIVERSAAL
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2011
Other
Open Access
universAAL - generic platform services, AAL platform services and ontology artefacts
Furfari F
Deliverable 2.2 is part of work package 2 - "Open source AAL Platform and Implementation" - whose main objective is to design, configure and implement an operational universAAL platform. This platform will be available in the Developer Depot and can be deployed to execution platforms like mobile phones, laptops, high-performance servers, etc. Special attention is given to operational issues such as reliability, security, interoperability and maintainability as perceived by service and application developers. The deliverable D2.2 particularly reports on the progress of work done in task 2.2 - "Implement universAAL Generic Platform Services, AAL platform services and ontology support". The platform services to be implemented within this task comprise support for context awareness and personalization, service-based interoperability, and adaptive user interaction, to name a few, and should facilitate the implementation of AAL specific features.Project(s): UNIVERSAAL
Furfari F
Deliverable 2.2 is part of work package 2 - "Open source AAL Platform and Implementation" - whose main objective is to design, configure and implement an operational universAAL platform. This platform will be available in the Developer Depot and can be deployed to execution platforms like mobile phones, laptops, high-performance servers, etc. Special attention is given to operational issues such as reliability, security, interoperability and maintainability as perceived by service and application developers. The deliverable D2.2 particularly reports on the progress of work done in task 2.2 - "Implement universAAL Generic Platform Services, AAL platform services and ontology support". The platform services to be implemented within this task comprise support for context awareness and personalization, service-based interoperability, and adaptive user interaction, to name a few, and should facilitate the implementation of AAL specific features.Project(s): UNIVERSAAL
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2011
Other
Restricted
universAAL - Part I: Roadmap and the work processes (D1.3-C )
Furfari F, Tazari S, Farshchian B
This sub-part of D1.3 establishes the common understanding of how the different major results expected from T1.4 relate to each other and defines in this way a roadmap from a reference model for AAL, over a reference architecture for AAL, to the concrete architecture underlying the development work in universAAL. It then describes the rationale and the pattern behind the consolidation processes in the project, which are leading to early results in parallel. A short reference to the ARCADE framework for describing architectures of ICT systems that is applied to the design work in universAAL closes the general part of this document. The remaining of this Part is divided into three similarly structured sections, each of them providing supplementary info related to one of the three main results presented in the Parts II to IV. The supplementary info covers the method, tools, and the process based on which the actual results have been produced. This way, the following three Parts could be kept very concise, just summarizing the result itself, while interested readers can still find more info in this document.Project(s): UNIVERSAAL
Furfari F, Tazari S, Farshchian B
This sub-part of D1.3 establishes the common understanding of how the different major results expected from T1.4 relate to each other and defines in this way a roadmap from a reference model for AAL, over a reference architecture for AAL, to the concrete architecture underlying the development work in universAAL. It then describes the rationale and the pattern behind the consolidation processes in the project, which are leading to early results in parallel. A short reference to the ARCADE framework for describing architectures of ICT systems that is applied to the design work in universAAL closes the general part of this document. The remaining of this Part is divided into three similarly structured sections, each of them providing supplementary info related to one of the three main results presented in the Parts II to IV. The supplementary info covers the method, tools, and the process based on which the actual results have been produced. This way, the following three Parts could be kept very concise, just summarizing the result itself, while interested readers can still find more info in this document.Project(s): UNIVERSAAL
2011
Conference article
Restricted
universAAL - An Open and Consolidated AAL Platform
Hanke S, Mayer C, Hoeftberger O, Boos H, Wichert R, Tazari M, Wolf P, Furfari F
Due to the demographic development towards an ageing society AAL technologies will play an important role in the future. There has been a lot of work clone in the field of AAL, but most of the project outcomes are proprietary and thus impossible to be combined. Accordingly, there is a need for an universal and open platform, which can be used as a starting point for further developments or just as an integration and standardization tool. For future service platform related research projects reference use cases as well as a reference tool set and framework would help to ensure a reusable and expandable platform, which is wide spread and therefore ensures a quality of service. The aim of the universAAL project is to combine the advantages and strengths of still ongoing or already finished research projects to create an universally applicable platform. The focus thereby is on interoperability and standardization to ensure a broad range of applicability and to develop an open platform that will make it technically feasible and economically viable to develop AAL applications. There are two tools for spreading the outcomes and ideas of the project planned: On the one hand the establishment of a store providing plug-and-play AAL applications and services that support multiple execution platforms and can be deployed to various devices and users, and on the other hand the AAL Open Association (AALOA) with the mission to create a platform for identifying key research topics in AAL, and to reach agreement on prioritization of these and to design, develop, evaluate and standardize a common service platform for AAL.DOI: 10.1007/978-3-642-18167-2_10
Project(s): UNIVERSAAL
Metrics:
Hanke S, Mayer C, Hoeftberger O, Boos H, Wichert R, Tazari M, Wolf P, Furfari F
Due to the demographic development towards an ageing society AAL technologies will play an important role in the future. There has been a lot of work clone in the field of AAL, but most of the project outcomes are proprietary and thus impossible to be combined. Accordingly, there is a need for an universal and open platform, which can be used as a starting point for further developments or just as an integration and standardization tool. For future service platform related research projects reference use cases as well as a reference tool set and framework would help to ensure a reusable and expandable platform, which is wide spread and therefore ensures a quality of service. The aim of the universAAL project is to combine the advantages and strengths of still ongoing or already finished research projects to create an universally applicable platform. The focus thereby is on interoperability and standardization to ensure a broad range of applicability and to develop an open platform that will make it technically feasible and economically viable to develop AAL applications. There are two tools for spreading the outcomes and ideas of the project planned: On the one hand the establishment of a store providing plug-and-play AAL applications and services that support multiple execution platforms and can be deployed to various devices and users, and on the other hand the AAL Open Association (AALOA) with the mission to create a platform for identifying key research topics in AAL, and to reach agreement on prioritization of these and to design, develop, evaluate and standardize a common service platform for AAL.DOI: 10.1007/978-3-642-18167-2_10
Project(s): UNIVERSAAL
Metrics:
See at:
doi.org | CNR IRIS | CNR IRIS | link.springer.com
2009
Software
Metadata Only Access
PERSONA middleware
Furfari F
It is the runtime software used by all the components of the PERSONA platform and developed by the EU FP6 IP PERSONA. It consists of a middleware solution for open distributed systems dealing with seamless connectivity and adequate support for interoper- ability that makes use of ontological technologies and denes appropriate protocols along with an upper ontology for sharing context. The middleware discovery protocol used in PERSONA is based on UPNP protocol stack. The CNR developed in particular the Abstract Communication Layer, the UPnP connectors and the Middleware core.
Furfari F
It is the runtime software used by all the components of the PERSONA platform and developed by the EU FP6 IP PERSONA. It consists of a middleware solution for open distributed systems dealing with seamless connectivity and adequate support for interoper- ability that makes use of ontological technologies and denes appropriate protocols along with an upper ontology for sharing context. The middleware discovery protocol used in PERSONA is based on UPNP protocol stack. The CNR developed in particular the Abstract Communication Layer, the UPnP connectors and the Middleware core.
See at:
CNR IRIS | www.aal-persona.org
2019
Conference article
Open Access
A personalised virtual coach to counteract ageing decline: the H2020 NESTORE project
Guarneri Mr, Mastropietro A, Caon M, Maldonado Fernandez L, Furfari F, Andreoni G, Rizzo G
Ageing population is growing faster in EU. ICT can provide solutions forActive Ageing; however, the success of novel ICT solutions depends on the userperception of their efficacy to support toward health promotion and global wellness.In this context, the H2020 project NESTORE (Non-intrusive Empowering Solutionsand Technologies for Older people to Retain Everyday life activity) will developan innovative, multidimensional, personalised e-coaching system to support healthyageing by: (1) Generating and sustaining motivation to take care of health; (2) Sug-gesting healthy nutrition and personalised physical and mental coaching, as well as social interaction, to prevent decline and preserve wellbeing. NESTORE started inSeptember 2017 and will last three years. It involves 16 partners from 7 European countries.DOI: 10.1007/978-3-030-05921-7_1
DOI: 10.5281/zenodo.4530897
DOI: 10.5281/zenodo.4530898
Project(s): NESTORE
Metrics:
Guarneri Mr, Mastropietro A, Caon M, Maldonado Fernandez L, Furfari F, Andreoni G, Rizzo G
Ageing population is growing faster in EU. ICT can provide solutions forActive Ageing; however, the success of novel ICT solutions depends on the userperception of their efficacy to support toward health promotion and global wellness.In this context, the H2020 project NESTORE (Non-intrusive Empowering Solutionsand Technologies for Older people to Retain Everyday life activity) will developan innovative, multidimensional, personalised e-coaching system to support healthyageing by: (1) Generating and sustaining motivation to take care of health; (2) Sug-gesting healthy nutrition and personalised physical and mental coaching, as well as social interaction, to prevent decline and preserve wellbeing. NESTORE started inSeptember 2017 and will last three years. It involves 16 partners from 7 European countries.DOI: 10.1007/978-3-030-05921-7_1
DOI: 10.5281/zenodo.4530897
DOI: 10.5281/zenodo.4530898
Project(s): NESTORE
Metrics:
See at:
ZENODO | ZENODO | zenodo.org | Lecture Notes in Electrical Engineering | CNR IRIS | CNR IRIS | link.springer.com
2008
Journal article
Open Access
CostGlue: simulation data exchange in telecommunications
Savic D., Potortì F., Furfari F., Pustisek M., Tomazic S., Bester J.
Exchanging simulation data among simulation practitioners is, to a great extent, hindered by the use of different kinds of data formats in simulation software packages. The purpose of the CostGlue project is to facilitate the exchange of simulation data in the field of telecommunications. We propose a common data interchange format and a data exchange model for raw simulation data, metadata and post-processing data. Based on this model, we additionally propose a framework, CostGlue, designed for packaging simulation output data into the common interchange format, launching post-processing plugins and exporting data into input formats for various third party tools. As a proof of concept we have implemented the framework as a software package and released it as free softwareSource: SIMULATION (S. DIEGO CALIF.), vol. 84 (issue 4), pp. 157-168
DOI: 10.1177/0037549708093715
Metrics:
Savic D., Potortì F., Furfari F., Pustisek M., Tomazic S., Bester J.
Exchanging simulation data among simulation practitioners is, to a great extent, hindered by the use of different kinds of data formats in simulation software packages. The purpose of the CostGlue project is to facilitate the exchange of simulation data in the field of telecommunications. We propose a common data interchange format and a data exchange model for raw simulation data, metadata and post-processing data. Based on this model, we additionally propose a framework, CostGlue, designed for packaging simulation output data into the common interchange format, launching post-processing plugins and exporting data into input formats for various third party tools. As a proof of concept we have implemented the framework as a software package and released it as free softwareSource: SIMULATION (S. DIEGO CALIF.), vol. 84 (issue 4), pp. 157-168
DOI: 10.1177/0037549708093715
Metrics:
See at:
SIMULATION | SIMULATION | CNR IRIS | CNR IRIS | sim.sagepub.com
2007
Conference article
Restricted
Storing and exchanging simulation results in telecommunications
Savic D., Potortì F., Furfari F., Bester J., Tomazic S., Pustisek M.
Though storing and exchanging simulation data is a rather simple task done by simulation practitioners, it is quite often a challenge as huge quantities of data are not uncommon, and conversion between different formats can be much time consuming. After examining some of the needs of the telecommunications simulation community, we describe the architecture of a working prototype - CostGlue - to be used as a general-purpose archiver and converter for large quantities of simulation data. The software architecture of the CostGlue tool is modular therefore allowing further development and contributions from other research sphere of activity. The core of the tool - CoreGlue - is responsible for communicating with the database. It acts as a unified interface for writing to the database and reading from it. Specific functions like import and export of data and different mathematical calculations are represented as a set of self-described modules, which are loaded as necessary. The graphic user interface is introduced as a web application for the simplicity of use and effective remote access to the application. The software package CostGlue is going to be released as free software with the possibility of further development.
Savic D., Potortì F., Furfari F., Bester J., Tomazic S., Pustisek M.
Though storing and exchanging simulation data is a rather simple task done by simulation practitioners, it is quite often a challenge as huge quantities of data are not uncommon, and conversion between different formats can be much time consuming. After examining some of the needs of the telecommunications simulation community, we describe the architecture of a working prototype - CostGlue - to be used as a general-purpose archiver and converter for large quantities of simulation data. The software architecture of the CostGlue tool is modular therefore allowing further development and contributions from other research sphere of activity. The core of the tool - CoreGlue - is responsible for communicating with the database. It acts as a unified interface for writing to the database and reading from it. Specific functions like import and export of data and different mathematical calculations are represented as a set of self-described modules, which are loaded as necessary. The graphic user interface is introduced as a web application for the simplicity of use and effective remote access to the application. The software package CostGlue is going to be released as free software with the possibility of further development.
See at:
fly.isti.cnr.it | CNR IRIS | CNR IRIS