Generic support for distributed applications

In the late 1980s, software designers introduced middleware platforms to support distributed computing systems. Since then, the rapid evolution of technology has caused an explosion of distributed-processing requirements. Application developers now routinely expect to support multimedia systems and mobile users and computers. Timely response to asynchronous events is crucial to such applications, but current platforms do not adequately meet this need. Another need of existing and emerging applications is the secure interoperability of independent services in large-scale, widely distributed systems. Information systems serving organizations such as universities, hospitals, and government agencies require cross-domain interaction. To meet the needs of these applications, Cambridge University researchers developed middleware extensions that provide a flexible, scalable approach to distributed-application development. This article details the extensions they developed, explaining their distributed software approach and the support it has provided for emerging applications     

ARMADA Middleware and Communication Services

Real-time embedded systems have evolved during the past several decades from small custom-designed digital hardware to large distributed processing systems. As these systems become more complex, their interoperability, evolvability and cost-effectiveness requirements motivate the use of commercial-off-the-shelf components. This raises the challenge of constructing dependable and predictable real-time services for application developers on top of the inexpensive hardware and software components which has minimal support for timeliness and dependability guarantees. We are addressing this challenge in the ARMADA project.ARMADA is set of communication and middleware services that provide support for fault-tolerance and end-to-end guarantees for embedded real-time distributed applications. Since real-time performance of such applications depends heavily on the communication subsystem, the first thrust of the project is to develop a predictable communication service and architecture to ensure QoS-sensitive message delivery. Fault-tolerance is of paramount importance to embedded safety-critical systems. In its second thrust, ARMADA aims to offload the complexity of developing fault-tolerant applications from the application programmer by focusing on a collection of modular, composable middleware for fault-tolerant group communication and replication under timing constraints. Finally, we develop tools for testing and validating the behavior of our services. We give an overview of the ARMADA project, describing the architecture and presenting its implementation status.     

一种中间件服务容错配置管理方法

提出一种基于运行时刻软件体系结构的容错管理方法,支持开发者和管理员针对不同中间件服务失效定制合适的故障检测和修复机制.首先,运行时刻软件体系结构自动构造构件依赖视图和错误传播①视图,为理解和分析整个系统的可靠性提供全局视图;然后,操作运行时刻软件体系结构配置容错机制;最后利用AOP技术将容错机制插装到中间件中,使其具备指定的容错能力.上述过程在一个可视化工具的辅助下半自动实施,并在J2EE中间件上得到验证.     

Interactive middleware architecture for lifelog based context awareness

Due to the development of IT convergence, a wide variety of information is being produced and distributed rapidly in digital form. Lifelog based context awareness is a technology that provides a service automatically based on perceived situational information in ubiquitous environments. To offer customized services to users, the technology of acquiring lifelog based context information in real time is the most important consideration. We propose the interactive middleware architecture for lifelog based context awareness in distributed and ubiquitous environments. Conventional middleware to support ubiquitous environments stores and manages the situational information and service content acquired by centralized storage or a DBMS. Centralized situational information and service content management may impede the autonomy of mobile nodes and the interoperation between different middle software. The proposed method designs a system that can distribute and manage situational information in mobile nodes using mobile devices in distributed and ubiquitous environments and share the service content between interactive middleware through publication. The application system designed in this study was used in a scenario providing situational perception based mobile service and proved to be useful.     

Middleware challenges ahead

Middleware research and development has reached the end of its first major phase, and new requirements are arising that are so fundamentally different that they will lead to new-generation middleware systems. Facing dynamic modifications in distributed systems technology, middleware developers are striving to support applications that meet the technical challenges of ubiquitous computing     

Utilizing architectural styles to enhance the adaptation support of middleware platforms

ContextModern middleware platforms provide the applications deployed on top of them with facilities for their adaptation. However, the level of adaptation support provided by the state-of-the-art middleware solutions is often limited to dynamically loading and off-loading of software components. Therefore, it is left to the application developers to handle the details of change such that the system’s consistency is not jeopardized.ObjectiveWe aim to change the status quo by providing the middleware facilities necessary to ensure the consistency of software after adaptation. We would like these facilities to be reusable across different applications, such that the middleware can streamline the process of achieving safe adaptation.MethodOur approach addresses the current shortcomings by utilizing the information encoded in a software system’s architectural style. This information drives the development of reusable adaptation patterns. The patterns specify both the exact sequence of changes and the time at which those changes need to occur. We use the patterns to provide advanced adaptation support on top of an existing architectural middleware platform.ResultsOur experience shows the feasibility of deriving detailed adaptation patterns for several architectural styles. Applying the middleware to adapt two real-world software systems shows the approach is effective in consistently adapting these systems without jeopardizing their consistency.ConclusionWe conclude the approach is effective in alleviating the application developers from the responsibility of managing the adaptation process at the application-level. Moreover, we believe this study provides the foundation for changing the way adaptation support is realized in middleware solutions.     

Clairvoyance: A framework to integrate shared displays and mobile computing devices

Supporting formal and informal meetings with digital information and ubiquitous software systems every day becomes increasingly mandatory. These meetings require that the integration of devices participating in the meeting and the information flow among them should be done as seamless as possible to avoid jeopardizing the natural interactions among participants. Trying to contribute to address such a challenge, this article presents a framework that allows devices integration and smooth information flow. This framework, named Clairvoyance, particularly integrates mobile computing devices and large-screen TVs through a mobile ad hoc network, and thus it eases the implementation of shared displays intended to be used in formal and informal meetings. Clairvoyance provides a set of services through an API, which can be used to develop ubiquitous applications that support meetings in particular scenarios. The preliminary evaluation of this framework considered its usage to implement a ubiquitous system that supports social meetings among friends or relatives. According to developers, the framework is easy to use and it provided all required services for such an application. The solution obtained was then utilized by end-users in simulated meetings. The evaluation results indicate that the Clairvoyance services were suitable to support the informal meetings, and that the devices integration and information flow were transparent for the end-users.     

Viewpoints of DSP software and service architectures

The software architecture of a future mobile telecommunication system consists of three main parts: system infrastructure services, middleware services and application services. Infrastructure services provide access technologies and networking services for the middleware services that again provide richer capabilities for wireless applications through mobile Internet. Architecture describes the organization of software systems, components, their internal relationships and connections to the environment. Reusing architectural structures benefits companies, because the architecture is a pivotal part of any system, and a costly one to construct. Architecture is documented and reused through architectural views that describe identified stakeholders and concerns, e.g. the purpose of a system, and the feasibility of constructing, deploying, evolving and maintaining it. Views conform to special viewpoints defined for the domain. This paper describes the viewpoints selected for developing the architecture of middleware services and digital signal processing software and provides a general framework for comparing viewpoints. Comparison and analysis of the defined viewpoints show that domain and system size are the dominant issues to be considered when architectural viewpoints are being selected.     

An overview of the Real-Time CORBA specification

A growing class of real-time systems require end-to-end support for various quality-of-service (QoS) aspects, including bandwidth, latency, jitter and dependability. Applications include command and control, manufacturing process control, videoconferencing, large-scale distributed interactive simulation, and testbeam data acquisition. These systems require support for stringent QoS requirements. To meet this challenge, developers are turning to distributed object computing middleware, such as the Common Object Request Broker Architecture, an Object Management Group (OMG) industry standard. In complex real-time systems, DOC middleware resides between applications and the underlying operating systems, protocol stacks and hardware. CORBA helps decrease the cycle time and effort required to develop high-quality systems by composing applications using reusable software component services rather than building them entirely from scratch. The Real-Time CORBA specification includes features to manage CPU, network and memory resources. The authors describe the key Real-Time CORBA features that they feel are the most relevant to researchers and developers of distributed real-time and embedded systems     

一种面向服务的权限管理模型

面向服务的体系结构(Service-Oriented Architecture,SOA)是设计和构建松耦合软件系统的方法,它可将基于中间件开发的分布式应用共享为Internet环境下的软件服务．传统中间件的用户权限系统具有较好的灵活性,基本满足封闭系统的安全需求．但在SOA模式下,难以满足不同节点和系统互相请求服务和共享资源过程中的授权．该文提出了一个面向服务的权限管理模型,通过支持用户之间的代理和提供一定的推理能力,为应用开发者提供了更完善的权限管理机制,并扩展了中间件跨越组织共享资源和服务的能力．该模型在一个J2EE应用服务器上被实现和验证．实验证明,该模型具有良好的灵活性和可扩展性,并且性能影响在合理的范围．     

EgoSpaces: facilitating rapid development of context-aware mobile applications

Today's mobile applications require constant adaptation to their changing environments, or contexts. Technological advances have increased the pervasiveness of mobile computing devices such as laptops, handhelds, and embedded sensors. The sheer amount of context information available for adaptation places a heightened burden on application developers as they must manage and utilize vast amounts of data from diverse sources. Facilitating programming in this data-rich environment requires a middleware that provides context information to applications in an abstract form. In this paper, we demonstrate the feasibility of such a middleware that allows programmers to focus on high-level interactions among programs and to employ declarative abstract context specifications in settings that exhibit transient interactions with opportunistically encountered components. We also discuss the novel context-aware abstractions the middleware provides and the programming knowledge necessary to write applications using it. Finally, we provide examples demonstrating the infrastructure's ability to support differing tasks from a wide variety of application domains.     

A pluggable middleware architecture for developing context-aware mobile applications

The proliferation of powerful smartphone devices provides a great opportunity for context-aware mobile applications becoming mainstream. However, we argue that conventional software development techniques suffer because of the added complexity required for collecting and managing context information. This paper presents a component-based middleware architecture which facilitates the development and deployment of context-aware applications via reusable components. The main contribution of this approach is the combination of a development methodology with the middleware architecture, which together bring significant value to developers of context-aware applications. Further contributions include the following: The methodology utilizes separation of concerns, thus decreasing the developmental cost and improving the productivity. The design and implementation of context-aware applications are also eased via the use of reusable components, called context plug-ins. Finally, the middleware architecture facilitates the deployment and management of the context plug-ins in a resource-aware manner. The proposed methodology and middleware architecture are evaluated both quantitatively and qualitatively.     

Integrated Development of Context-Aware Applications in Smart Spaces

When designing context-aware applications for smart spaces, developers must provide interface specifications for perceptual components, which often come from multiple vendors. The authors outline a set of structuring principles that leverage such specifications. IBM has introduced two tools that facilitate the development of smart space applications. Chilix is a middleware library for bridging disaggregated systems, and SitCom is an integrated development environment enabling context modeling, and simulation and lifecycle management of perceptual components. Chilix provides an attractive lightweight alternative to legacy middleware for distributed computing. SitCom supports perceptual component developers, service developers and context-modeling experts across the development life cycle.     

MobiPADS: a reflective middleware for context-aware mobile computing

Traditionally, middleware technologies, such as CORBA, Java RMI, and Microsoft's DCOM, have provided a set of distributed computing services that essentially abstract the underlying network services to a monolithic "black box." In a mobile operating environment, the fundamental assumption of middleware abstracting a unified distributed service for all types of applications operating over a static network infrastructure is no longer valid. In particular, mobile applications are not able to leverage the benefits of adaptive computing to optimize its computation based on current contextual situations. In this paper, we introduce the Mobile Platform for Actively Deployable Service (MobiPADS) system. MobiPADS is designed to support context-aware processing by providing an executing platform to enable active service deployment and reconfiguration of the service composition in response to environments of varying contexts. Unlike most mobile middleware, MobiPADS supports dynamic adaptation at both the middleware and application layers to provide flexible configuration of resources to optimize the operations of mobile applications. Within the MobiPADS system, services (known as mobilets) are configured as chained service objects to provide augmented services to the underlying mobile applications so as to alleviate the adverse conditions of a wireless environment.     

Deriving Long-Term Value from Context-Aware Computing

Modern businesses are increasingly dynamic in nature, which creates a need for computer systems that can sense and respond to rapid changes in the environment, or “context,” of the enterprise. This article presents the authors' vision of a context “ecosystem” that helps enterprises, applications, and developers respond to these dynamic changes and derive long-term value from context information. the ecosystem includes providers of raw context information, components that derive more abstract context information from lower level sources, middleware that provides systematic context services to applications, development tools, and contextaware applications.