DSpace About DSpace Software
 

DSpace at ICSY >
ICSY - Integrated Communication Systems Lab >
01: Publications / Publikationen >

Please use this identifier to cite or link to this item: http://dspace.icsy.de/handle/123456789/320

Title: Requirements Based Automatic Service Composition: A Demonstration
Authors: Schwerdel, Dennis
Khondoker, M. Rahamatullah
Veith, Eric MSP
Reuther, Bernd
Müller, Paul
Keywords: SONATE
Future Network Architectures
Automatic Service Composition
Functional Composition
Issue Date: Aug-2011
Publisher: 11th Würzburg Workshop on IP: Joint ITG and Euro-NF Workshop "Visions of Future Generation Networks" (EuroView2011)
Abstract: The current Internet architecture was designed decades ago. Back then the main goals of the architecture were stability, performance and of course its functionality. Current trends, e.g. mobile devices, cloud computing, energy efficiency pose new requirements that the current Internet architecture cannot fulfill. Rather than building new functionality on top of the Internet or adding more complexity to it by introducing even more conditional functionality the Future Internet should have a smarter way to deal with diverse requirements and environmental constraints. Future network architectures must be flexible both long-term and a short-term in order to evolve and adapt to changing application requirements and new transport technologies (fixed and/or mobile) with different capabilities, and should enable evolutionary changes of the network itself. Thereby long-term flexibility can be seen as the capability of a system to evolve with updated protocols and network capabilities. Short-term flexibility is understood as the capability of a system to adapt itself and react to network conditions and an application requirements [1]. The Service-Oriented Network Architecture [2] (SONATE) tries to handle these requirements and constraints by using concepts of modularity and service-orientation. As such, services are central elements of SONATE: A service reflects the effects of an activity rather than the algorithms and data structures that implement it. Thus, a service can be provided using different algorithms. A building block is a functional block that implements one distinct networking functionality. Examples for building blocks are retransmission mechanisms, data encryption algorithms, and monitoring functionality. Each building block usually has several effects like increasing the end-to-end delay or reducing the maximum payload size in addition to its main function. All the effects of a building block form the service which the building block provides. Since a service does not define the mechanism that is needed to provide it, several building blocks can provide the same service and are thus exchangeable. The services of multiple building blocks might be needed to provide the service which the application requested.
URI: http://dspace.icsy.de/handle/123456789/320
Appears in Collections:01: Publications / Publikationen

Files in This Item:

File Description SizeFormat
320_abstract_schwerdel_c.pdf117,67 kBAdobe PDFView/Open

Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.

 

Valid XHTML 1.0! DSpace Software Copyright © 2002-2007 MIT and Hewlett-Packard - Feedback