Hybrid solutions to the feature interaction problem

In this paper we assume a competitive marketplace where the features are developed by different enterprises, which cannot or will not exchange information. We present a classification of feature interaction in this setting and introduce an on-line technique which serves as a basis for the two novel <i>hybrid</i> approaches presented. The approaches are hybrid as they are neither strictly off-line nor on-line, but combine aspects of both. The two approaches address different kinds of feature interactions, and thus are complimentary. Together they provide a complete solution by addressing interaction detection and resolution. We illustrate the techniques within the communication networks domain

Business-oriented development of telecommunication services

The development of software for distributed systems, e.g. telecommunication services, is a complex activity. Numerous issues have to be resolved when developing such systems, examples of which are language/system heterogeneity and remoteness of components. Interface definition languages (IDLs) are used as the basis for addressing some of these issues. IDLs allow for the specification of the syntactic aspects of the interfaces of the components in the system to be made. Whilst lending itself to issues of heterogeneity and location transparency, dealing with IDL as the basis for system development is not without its problems. Two of the main problems with IDL are its lack of behaviour and its lack of abstraction. Thus designers should not be constrained to work within the syntactic notations used to implement their systems, nor should they be unaided in how they might better design their systems. In this paper we show how these issues are being addressed in the TOSCA project in its development of a service creation and validation environment

Protocols versus objects: can models for telecommunications and distributed processing coexist?

This paper identifies two paradigms that influence the design of telematics systems nowadays: the protocol-centred and the object-centred paradigms. Both paradigms have been introduced to cope with interoperability, each in their own way. The coexistence of these paradigms can have an enormous impact on the design of telematics systems. This paper identifies some combined uses of both paradigms and some fundamental research problems related to the coexistence of these paradigm

Applying formal methods to standard development: the open distributed processing experience

Since their introduction, formal methods have been applied in various ways to different standards. This paper gives an account of these applications, focusing on one application in particular: the development of a framework for creating standards for Open Distributed Processing (ODP). Following an introduction to ODP, the paper gives an insight into the current work on formalising the architecture of the Reference Model of ODP (RM-ODP), highlighting the advantages to be gained. The different approaches currently being taken are shown, together with their associated advantages and disadvantages. The paper concludes that there is no one all-purpose approach which can be used in preference to all others, but that a combination of approaches is desirable to best fulfil the potential of formal methods in developing an architectural semantics for OD

An ideal IoT solution for real-time web monitoring

For the internet of things (IoT) to fully emerge, it is necessary to design a suitable system architecture and specific protocols for this environment. The former to provide horizontal solutions, breaking away the current paradigm of silos solutions, and thus, allowing the creation of open and interoperable systems; while the latter will offer efficient and scalable communications. This paper presents the latest standards and ongoing efforts to develop specific protocols for IoT. Furthermore, this paper presents a new system, with the most recent standards for IoT. Its design, implementation and evaluation will be also described. The proposed system is based on the latest ETSI M2M specification (ETSI TC M2M in ETSI TS 103 093 V2.1.1.http://www.etsi.org/deliver/etsi_ts/103000_103099/103093/02.01.01_60/ts_103093v020101p.pdf, 2013b) and the MQTT protocol (IBM, Eurotech in MQTT V3.1 Protocol Specification pp 1-42, http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/MQTT_V3.1_Protocol_Specific. pdf, 2010). With this solution it is possible to show how we can create new applications to run over it and the importance of designing specifically tailored for IoT communication protocols in order to support real-time applications.- This project was funded by Fundo Europeu de Desenvolvimento Regional (FEDER), by Programa Operacional Factores de Competitividade (POFC) - COMPETE and by Fundacao para a Ciencia eTecnologia, on the Scope of projects: PEstC/EEI/UI0319/2015 and PEstC/EEI/UI0027/2015. This paper is a result of the project "SmartEGOV: Harnessing EGOV for Smart Governance (Foundations, methods, Tools) / NORTE-01-0145-FEDER-000037", supported by Norte Portugal Regional Operational Programme(NORTE2020), under the PORTUGAL 2020 Partnership Agreement, through the European Regional Development Fund (EFDR).info:eu-repo/semantics/publishedVersio

Dynamic Services for Assisted Living Environments

Software technologies for assisted living systems can be derived from the more mature domain of pervasive computing and the relative emerging ambient intelligence field. We present herein our position about the need for interoperability enablers extending the software service paradigm and for dependability as key elements of assisted living software systems

Options for Securing RTP Sessions

The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This heterogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity, and source authentication of RTP and RTP Control Protocol (RTCP) packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP and gives guidance for developers on how to choose the appropriate security mechanism