A Practical Framework of Realizing Actuators for Autonomous Fault Management in SOA
DOI: 10.1109/SERVICES-I.2009.28 Conference: Services - I, 2009 World Conference on
Due to the key features of service-oriented architecture (SOA); blackbox-nature of services, heterogeneity, service dynamism, and service evolvability, fault management in SOA is known to be more challenging than conventional system management. An efficient way of managing faults in SOA is to apply principles of autonomic computing (AC), of which process is specified in MAPE. The first two phases of MAPE are to monitor target systems and diagnose faults to determine underlying cause. The other two phases are to plan healing/actuation methods and to execute them. Devising methods to remedy service faults which can run in autonomous manner is a hard problem, mainly due to the remoteness and the limited visibility and controllability. In this paper, we present a practical framework to design actuators which can be invoked autonomously. By considering the relationships among fault, cause, and actuator, we derive the abstract and concrete actuators. For some essential concrete actuators, we present their algorithms which can be implemented in practice. We believe our proposed service actuation framework makes the realization of autonomous service management more feasible.
Conference Paper: A Service-Based Approach to Designing Cyber Physical Systems.[Show abstract] [Hide abstract]
ABSTRACT: A Cyber-Physical System (CPS) is defined as integrations of computation and physical processes. In CPS, downsized embedded devices monitor and manage the physical process. Mobile Internet Device (MID), as a portable handheld device designed for mobility providing a down-graded computing capability, can be used as a strong candidate for client-side devices in CPS. Since these physical devices have limited resources, it is not possible to execute complex computation and processes. To cope with this challenge, we apply Service-oriented Architecture (SOA) or Cloud Computing (CC) concepts to CPS, called a service-based CPS. To realize a service-based CPS, we first define overall architecture with three tiers. And, we present key methods to design each tier in the architecture. The design methods are defined to deal with design challenges of CPSs such as dynamic composition, dynamic adaptation, and high confidence CPS management. Then, we perform a case study to show applicability of our approach. With this approach, we hope that CPS can even handle complex and resource-consuming physical processes with a downsized MID.9th IEEE/ACIS International Conference on Computer and Information Science, IEEE/ACIS ICIS 2010, 18-20 August 2010, Yamagata, Japan; 01/2010
- [Show abstract] [Hide abstract]
ABSTRACT: Cloud Computing (CC) is emerged as an effective reuse paradigm, where software functionality, hardware computing power, and other computing resources are delivered in the form of service. Mobile Internet Device (MID), as a portable handheld device, becomes a strong candidate for client-side computing. MID has a limited resource and computing power, hence, it is not deploy the applications which require complex computation and large amount of resources. The MID feature of limited resource forbids deploying and running complex software application on MID, and a key concept of CC is to deploy all the computing resources are placed on the provider side. Hence, by applying CC concepts to the MID environment, disadvantages derived from limited resource can be overcome. Therefore, we first identify key features of MID applications. To overcome a drawback of MID, limited resource, we present our justification of applying CC to MID environment and key methods which are raised in applying CC to MID environment.Proceedings of the 4th International Conference on Ubiquitous Information Management and Communication, ICUIMC 2010, Suwon, Republic of Korea, January 14-15, 2010; 01/2010
Data provided are for informational purposes only. Although carefully collected, accuracy cannot be guaranteed. The impact factor represents a rough estimation of the journal's impact factor and does not reflect the actual current impact factor. Publisher conditions are provided by RoMEO. Differing provisions from the publisher's actual policy or licence agreement may be applicable.