enjoying multimedia communications, taking advantage of advanced software services, buying and selling, keeping in touch with family and friends,
enjoying multimedia communications, taking advantage of advanced software services, buying and selling, keeping in touch with family and friends,
terminals, servers, etc. CPUS, etc. and handlers (software programs/routines) that generate and treat as well as query
and access Data storage of data: refers to memory, buffers, caches, disks, etc. and associated logical data structures.
as the onset of the phenomenon will still cause thousands of cache servers to request the same documents from the original site of publication. 3. 3 Transmission Limitations The fundamental restrictions that have been identified in this category are:
Software & Service Architectures & Infrastructures, D4: Networked Enterprise & Radio frequency identification (RFID) and F5: Trust and Security.
Foundations for the Study of Software Architecture. ACM SIGSOFT Software engineering Notes 17,4 (1992) 17 Papadimitriou, D.,et al.
and sharing a common physical substrate of communication nodes and servers managed by multiple infrastructure providers.
and servers Towards In-Network Clouds in Future Internet 21 Fig. 1. In-Network Cloud Resources within the network.
Together these distributed systems form a software-driven network control infrastructure that will run on top of all current networks (i e. fixed
System virtualisation separates an operating system from its underlying hardware resources; resource virtualisation abstracts physical resources into manageable units of functionality.
which virtual machines can be relocated dynamically to any physical node or server regardless of location, network,
The virtualisation plane consists of software mechanisms to abstract physical resources into appropriate sets of virtual resources that can be organised by the Orchestration Plane to form components (e g.,
and software for their state, present their capabilities, or collect configuration parameters. A monitoring mechanism and framework was developed to gather measurements from relevant physical and virtual resources and CCPS for use within the CISP.
This can include common operations such as getting the state of a server with its CPU
and network components of a server host, were created. We can also measure the same attributes of virtualised hosts by interacting with a hypervisor to collect these values.
, physical nodes and servers) subject to constraints determined by the Orchestration Plane. The Management Plane is designed to meet the following functionality:
and continuous migration of virtual routers into hosts (i e. physical nodes and servers) subject to constraints determined by the Orchestration Plane.
and issued as open source 10, which aims to create a highly open and flexible environment for In-Network Clouds in Future Internet.
Full design and implementation of all software platforms are presented in 10. vcpi (Virtual Component Programming interface is the VP's main component dealing with the heterogeneity of virtual resources
control and management of programmable or active sessions over virtual entities, such as servers and routers.
4 Conclusion This work has presented the design of an open software networked infrastructure (In-Network Cloud) that enables the composition of fast and guaranteed services in an efficient manner,
Virtualisation Plane (VP), Management Plane (MP), Knowledge Plane (KP), Service Plane (SP) and Orchestration Plane (OP). The resulting software-driven control network
Virtualising physical network and server resources has served two purposes: Managing the heterogeneity through introduction of homogeneous virtual resources and enabling programmability of the network elements.
Platforms and Software systems for an Autonomic Internet. IEEE Globecom 2010; 6-10 dec.,, Miami, USA (2010) 4. Galis, A.,et al.:
Towards the Future Internet, IOS Press, Amsterdam (2009) 5. Chapman, C.,et al.:Software Architecture Definition for On-demand Cloud Provisioning.
ACM HPDC, 21-25, Chicago hpdc2010. eecs. northwestern. edu (June 2010) 6. Rochwerger, B.,et al.:
IOS Press, Amsterdam (2009), http://www. iospress. nl/16. Berl, A.,Fischer, A.,De Meer, H.:
DIMA (Distributed IP Mobility Approach) 35 can also be considered as a core-level scheme by allowing the distribution of MIP Home Agent (the normally isolated central server) to many and less powerful interworking servers called Mobility
a special information server is required in the network, which can also Flat Architectures: Towards Scalable Future Internet Mobility 45 be centralized or distributed.
and Alex Galis2 1 Waterford Institute of technology WIT Telecommunications Software and Systems Group TSSG, Co. Waterford, Ireland {jmserrano, sdavy, mjohnsson, wdonnelly}@ tssg. org
by replacing a plethora of proprietary hardware and software platforms with generic solutions supporting standardised development and deployment stacks.
Section VII presents the summary and outlook of this research. Finally some bibliography references supporting this research are included. 2 Challenges for Future Internet Architectures This section focuses on interdisciplinary approaches to specify data link and crossdomain interoperability to,
the software that manages them, and the actors who direct such management. In federation management end-to-end communication services involve configuring service
In the current Internet typical large enterprise systems contain thousands of physically distributed software components that communicate across different networks 27 to satisfy end-to-end services client requests.
middleware and hardware levels (3. Analysis) that can be gathered, processed, aggregated and correlated (4. Mapping) to provide knowledge that will support management operations of large enterprise applications (5. Federated Agreements)
62 M. Serrano et al. 6. 2 Federation of Network and Enterprise Management Systems Typical large enterprise systems contain thousands of physically distributed software components that communicate across different networks
Challenges in this scenario relies on how monitoring at the network level can provide knowledge that will enable enterprise application management systems to reconfigure software components to better adapt applications to prevailing network conditions.
and Outlook In the future Internet new designs ideas of Federated Management in Future Internet Architectures must consider high demands of information interoperability to satisfy service composition requirements being controlled by diverse,
Algorithms and processes to allow federation in enterprise application systems to visualize software components, functionality and performance.
or redeploy software components realizing autonomic application functionality. Guidelines and exemplars for the exchange of relevant knowledge between network and enterprise application management systems.
Platforms and Software systems for an Autonomic Internet. In: IEEE Globecom 2010, Miami, USA, 6-10 december (2010) 14.
IOS Press, Amsterdam (2009) 24. Feldmann, A.:Internet clean-slate design: what and why? ACM SIGCOM Computer Communication Review 37 (3)( 2007) 25.
software artifacts and humans connected to it. The RWI assumes that the information flow to
or application software that intends to interact with Resources and Eoi. Providing the services and corresponding underlying information models to bridge the physical
and the software components implementing the interaction endpoints from the user perspective (Resource End point REP). Furthermore,
and their relationships in the RWI system model A REP is a software component that represents an interaction end-point for a physical resource.
A REP Host is a device that executes the software process representing the REP. As mentioned before,
a computer in the network or an embedded server may act as the REP host for a resource,
The system is based on the OSGI service middleware and consists of two main sub systems: the service platform openaal and the ETALIS Complex event processing system (icep. fzi. de.
i e. eventdriven one. 4. 3 PECES The PECES architecture PECES provides a comprehensive software layer to enable the seamless cooperation of embedded devices across various smart spaces on a global scale in a context-dependent
The PECES middleware architecture enables dynamic group-based communication between PECES applications (Resources) by utilizing contextual information based on a flexible context ontology.
Although Resources are not directly analogous to PECES middleware instances, gateways to these devices are more resource-rich
and can host middleware instances, and can be queried provided that an application-level querying interface is implemented.
must be running the PECES middleware before any interaction may occur. Both one-shot and continuous interactions are supported between components
/A According to W3c Semantic Sensor Network Ontology Observation&measuremen t, role, agent, service and resource ontologies PECES Implicit via middleware Expressive (based on ontologies),
Role-based access control for individual middleware components N/A EPC and value-added sensing EPCIS standard SENSEI Execution manager responsible for maintenance of long lasting requests
References ASPIRE Advanced Sensors and lightweight Programmable middleware for Innovative RFID Enterprise applications, FP7, http://www. fp7-aspire. eu/CONET Cooperating Objects Noe,
univocally and persistently identify the resources within IDN-middleware independent of their physical locations; in the lower layer are used Uniform Resource Locators (URL) to identify resource replicas as well as to access them.
The implementations of IDN-SA are a set of different software modules one module for each layer.
Each module, implemented using an HTTP server, will offers a REST interface. The interaction between IDN-compliant applications and IDN-SA follows the HTTP protocol as defined in REST architectural style too.
IOS Press, Amsterdam (2010) 2. Ayers, D.:From here to There. IEEE Internet Comput 11 (1), 85 89 (2007) 3. European commission Information Society and Media.
a Scalable Middleware Infrastructure for Smart Data Integration, in D. In: Giusto, D.,et al. eds.)
The Effects of Layering and Encapsulation on Software Development Cost and Quality. IEEE Trans. Softw.
example of Resources include services, contents, terminals, devices, middleware functionalities, storage, computational, connectivity and networking capabilities, etc.;
for the sake of brevity, simply referred to as"Cognitive Framework")adopting a modular design based on middleware"enablers".
It can be realized through the implementation of appropriate Cognitive Middleware-based Agents (in the following referred to as Cognitive Managers)
Indeed the software nature of the Cognitive Manager allows a transparent integration in the network nodes.
5) The transparency and the middleware (firmware based) nature of the proposed Cognitive Manger architecture makes relatively easy its embedding in any fixed/mobile network entity (e g.
Moreover, the Cognitive Managers functionalities (and, in particular, the Cognitive Enabler software) can be added/upgraded/deleted through remote (wired and/or wireless) control.
The framework has been implemented as a Linux Kernel Module and it has been installed in test-bed machines and in a legacy router1 for performance evaluation.
and two IEEE 802. 3u links at 100 Mbit/s. Fig. 3. Test scenario 1 We have modified the firmware of a Netgear router (Gigabit Open source Router with Wireless
Also can be created other kinds of classification, such as hardware, software and network, among others. Some one of them (not all) can be used as resources in others relevant literature.
The benefits for the use of the propositional logic for network formalization is the implementation facility in software and hardware.
For the communication between the layers running in a Distributed Operating system, without the traditional sockets used in TCP IP,
by the direct use of the Raw Socket to communicate with the Distributed Operating system, without the use of IP, TCP, UDP and SCTP.<
IOS Press, Amsterdam (2009) 32 Tselentis, G.,et al.:Towards the Future Internet-Emerging Trends from European Research.
IOS Press, Amsterdam (2010) 33 Tsiatsis, V.,Gluhak, A.,Bauge, T.,Montagut, F.,Bernat, J.,Bauer, M.,Villalonga, C.,Barnaghi, P
IOS Press, Amsterdam (2010) 34 Vissers, C.,Logrippo, L.:The Importance of the Service Concept in the Design of Data communications Protocols.
Another dimension of a service provider's win is decreased a traffic volume from its own content servers and reduced load of the servers,
Peers and the ETMS servers, providing rating information, are located in these stub-ASES, which are interconnected via a hub-AS containing the initial seed.
since the software has already been developed for the initial scenario and it is simply a matter of deploying
one issue today is how to choose what path to use between two servers amongst the many possibilities-MPTCP naturally spreads traffic over the available paths.
In this example, traffic between the two servers (at the bottom) travels over two paths through the switching fabric of the data centre (there are four possible paths.
(which involves the OS vendor updating their stack) and adoption (which means that MPTCP is actually being used
and deployment is decided mainly by the OS (Operating system) vendor and not the end user.)Therefore we believe that a more promising initial scenario is an end user that accesses content, via wireless LAN and 3g, from a provider that controls both end user devices and content servers 26 for example,
Nokia or Apple controls both the device and the content server, Nokia Ovi or Apple App store.
Benefits: MPTCP improves resilience -if one link fails on a multi-homed terminal, the connection still works over the other interface.
Both the devices and servers are under the control of one stakeholder, so the end user‘unconsciously'adopts MPTCP.
For instance, it is necessary to think about the benefits and costs for OS vendors, end users, applications and ISPS (Internet service providers.
The CDN server sends premium packets (perhaps for IPTV) as Conex-Not-Marked or Conex-Re-echo.
and then the host's software would automatically send the user's premium traffic (Voip say) as Conex-enabled.
Roll out of the software should be cheaper, therefore the expected benefits of the deployment can be less.
Every user can immediately use the new (virtualised) software, so effectively a large number of users can be enabled simultaneously.
if there is some problem with the new software. Virtualisation is not suitable for all types of software, for instance new transport layer functionality, such as MPTCP and CONEX,
needs to be on the actual devices. 142 P. Eardley et al. There is an analogy with the digitalisation of content
HTTP Extensions for Simultaneous Download from Multiple Mirrors, draft-ford-http-multi-server, work in progress (2009) 25.
such as processing and storage capabilities of servers and networking infrastructure. For example, routing table memory of core Internet routers can be considered a public good that retail ISPS have an incentive to over-consume by performing prefix de-aggregation with Border Gateway Protocol (BGP.
when multiple candidate servers are available, a consumer may prefer the one offering better Qos,
while a provider selects the server that minimizes its cost; e g.,, this is possible if the provider operates a local DNS service.
Due to economies of scale the thin-client paradigm, where most applications run on a remote server, is considered to achieving energy savings but to the disadvantage of the server provider.
However under some assumptions, Wifi hotspots can consume much less energy than UMTS (Universal mobile telecommunications system) networks.
One challenge for the technologists designing new hardware, software systems, and platforms, however, is to be aware that technology is not value-free,
Towards the Future Internet-Emerging Trends from European Research, IOS Press, Amsterdam (2010) 16. Trilogy:
The concept of Platform-as-a-service provides joint development and execution environments for software and services, with common framework features and easy integration of functionality offered by third parties.
and provide an outlook to their mitigation, embedded in a systematic security risk management process. In cloud computing,
and can refer to abstractions of any granularity, such as software components, individual nodes, or ASES.
5th international workshop on Software engineering and middleware, pp. 98 105 (2005) 8. Merkle, R.:Secrecy, authentication,
Rep (2008), http://www. tcs. hut. fi/Software/PLA/new/doc/PLA HW FINAL REPORT. pdf 25. Lagutin, D.:
It will be essential to integrate various activities that need to be addressed in the scope of secure service engineering into comprehensive software and service life cycle support.
yet the Future Internet stretches the present know how on building secure software services and systems:
and reassessed continuously. 1. 2 The Need for Engineering Secure Software Services The need to organize,
integrate and optimize the research on engineering secure software services to deal effectively with this increased challenge is pertinent and well recognized by the research community and by the industrial one.
and damaged reputation. 1. 3 Research Focus on Developing Secure FI Services Our focus is on the creation and correct execution of a set of methodologies, processes and tools for secure software development.
approving that the developed software is secure. Assurance must be based on justifiable evidence, and the whole process designed for assurance.
integrating the former results in (5) a risk-aware and cost-aware software development life-cycle (SDLC),
The first three activities represent major and traditional stages of (secure) software development: from requirements over architecture and design to the composition and/or programming of working solutions.
and methodologies for software construction as well as researching about new ways to take this complexity into account in a holistic manner.
The design phase of the software service and/or system is a timely moment to enforce
The software architecture encompasses the more relevant elements of the application, providing either a static or/and a dynamic view of the application.
which comprise software elements, the externally visible properties of those elements, and the relationships among them. 182 W. Joosen et al.
assess and reason about security mechanisms at an early phase in the software development cycle. The research topics one must focus on in this subarea relate to model-driven architecture and security, the compositionality of design models and the study of design patterns for FI services and applications.
Until this point in the software and service development process, different concerns security among them of the whole application have been separated into different models,
A design pattern is a general repeatable solution to a commonly occurring problem in software design.
both from a general perspective and from a security perspective for security-critical software systems. 4 Security Support in Programming Environments Security Support in Programming Environments is not new;
Securing Future Internet Service is inherently a matter of secure software and systems. The context of the future internet services sets the scene in the sense that (1) specific service architectures will be used,
and (3) a broad range of programming technologies will be used to develop the actual software and systems.
Some of these properties have been embedded in the security specific elements of the software design; other may simply be high priority security requirements that have articulated such as the appropriate treatment of concurrency control and the avoidance of race conditions in the code,
Middleware Aspects. The research community should re-investigate service-oriented middleware for the Future Internet
with a special emphasis on Engineering Secure Future Internet Services 185 enabling deployment, access, discovery and composition of pervasive services offered by resource-constrained nodes. 4. 2
Lock-free wait-free algorithms for common software abstractions (queues, bags, etc. are one of the most effective approaches to exploit multi-core parallelism.
Programming support must include methods to ensure the adherence of a particular program to well-known programming principles or best-practices in secure software development.
Assurance will play a central role in the development of software based services to provide confidence about the desired security level.
seamlessly informing and giving feedback at each stage of the software life cycle by checking that the related models
Obviously the security support in programming environments that must be delivered will be essential to incept a transverse methodology that enables to manage assurance throughout the software and service development life cycle (SDLC.
security assurance and risk and cost management during SDLC. 5. 1 Security Assurance The main objective is to enable assurance in the development of software based services to ensure confidence about their trustworthiness.
Our core goal is to incept a transverse methodology that enables to manage assurance throughout the software development life cycle (SDLC.
penetration testing that leverages on the high-level models that are generated in early stages of the software life cycle,
and cost aware SDLC should be based on an incremental and iterative process that is accommodated to an incremental software development process.
While the software development proceeds through incremental phases, the risk and cost analysis will undergo new iterations for each phase.
and cost analyses will propagate through the software development phases and become more refined. In order to support the propagation of analysis results through the phases of the SDLC Engineering Secure Future Internet Services 189 one needs to develop methods and techniques for the refinement of risk analysis documentation.
In order to accommodate to a modular software development process, as well as effectively handling the heterogeneous and compositional nature of Future Internet services,
Work partially supported by EU FP7-ICT project NESSOS (Network of Excellence on Engineering Secure Future Internet Software Services and Systems) under the grant agreement n. 256980.
Software Architecture In practice, 2nd edn. Addison-Wesley, Boston (2003) 3. Bauer, L.,Ligatti, J.,Walker, D.:
An agent-oriented software development methodology. Autonomous Agents and Multi-Agent Systems 8, 203 236 (2004) 6. Clavel, M.,da Silva, V.,de O. Braga, C.,Egea, M.:
SPAQU'08 (Int. Workshop on Software Patterns and Quality)( 2008) 18. Lazouski, A.,Martinelli, F.,Mori, P.:
and public acceptance. 1 Introduction The vision of the Internet of Services (Ios) entails a major paradigm shift in the way ICT systems
In the Ios, services are business functionalities that are designed and implemented by producers, deployed by providers,
However, the new opportunities opened by the Ios will only materialize if concepts, techniques and tools are provided to ensure security.
thereby significantly improving the all-round security of the Ios. In this chapter, we give a brief overview of the main scientific and industrial challenges for such verification tools,
and public acceptance of the Ios. We proceed as follows. In Sections 2 and 3, we discuss, respectively,
a layer of software modules that carry out the translation from application-level specification languages (such as BPMN and BPEL,
and that could have allowed a malicious web server to impersonate a user on any Google application.
and Outlook As exemplified by these case studies and success stories, formal validation technologies can have a decisive impact for the trust
and security of the Ios. The research innovation put forth by AVANTSSAR aims at ensuring global security of dynamically composed services
These advances will significantly improve the all-round security of the Ios, and thus boost its development and public acceptance.
Web Services Business Process Execution Language vers. 2. 0 (2007), http://docs. oasis-open. org/wsbpel/2. 0/OS/wsbpel
-v2. 0-OS. pdf 25. Pnueli, A.:The Temporal Logic of Programs. In: Proceedings of the 18th IEEE Symposium on Foundations of Computer science, pp. 46 57.
Cloud computing goes beyond technological infrastructure that derives from the convergence of computer server power, storage and network bandwidth.
Following its software-plus-services strategy announced in 2007 Microsoft has developed in the past years several Saas cloud services such as the Business Productivity Online Suite (BPOS.
Sharing resources such as operating systems, middleware, or actual software requires a case-by-case design of isolation mechanisms.
In particular the last example of Software-as-a-service requires that each data instance is assigned to a customer
this machine may use a database server (Middleware isolation) and provide services to multiple individual departments (Application isolation).
software quality plays an important role in avoiding disruptions and service outages: Clouds gain efficiency by industrializing the production of IT services through complete end-to-end automation.
or recover from software and hardware failures. For building such resilient systems, important tools are data replication,
Trustworthy Clouds Underpinning the Future Internet 219 5 Outlook The Path Ahead Cloud computing is not new it constitutes a new outsourcing delivery model that aims to be closer to the vision of true utility computing.
Proceedings of the 4th International Workshop on Large scale Distributed systems and Middleware, Z urich, Switzerland. LADIS'10, pp. 12 17.
and visualize the use of their data stored in a remote server or in the cloud.
, servers, services, applications) provided by the cloud that are provisioned rapidly with a minimal management effort
such as setting and comparing user preferences with server privacy policies, expressing conditions on complex secondary usage cases,
In fact, this sticky policy will be sent to the server and follow the data in all their lifecycle to specify the usage conditions.
supporting a multilevel nested policy describing the data handling conditions that are applicable for any third party collecting the data from the server.
when a server storing personal data decides to share the data with a third party Obligations: Obligations in sticky policies specify the actions that should be carried out after collecting
it checks if there is any access restriction for the data before sending it to any server.
a data provider recovers the server's privacy policy in order to compare it to its preferences and verify
If a third party requests some data from the server, the latter becomes a data provider and acts as a user-side engine invoking access control and matching modules,
In other words, we suppose that the server enforces correctly the sticky policies, but, actually, nothing prevents him from creating a back door in his database
Trust and tamper-proof software delivery. In: Proceedings of the 2006 international workshop on Software engineering for secure systems.
A Resource Adapter (a concept similar to device drivers) wraps a domain's resource API in order to create a homogeneous API defined by Panlab.
an auction site prototype modeled after ebay. com. It provides a virtualized distributed application that consists of three components, a web server, an application server, a database and a workload generator,
Furthermore it can be deployed in a virtualized environment using Xen server technology, which allows regulating system resources such as CPU usage and memory,
and using Xen server technology to regulate CPU usage. During this scenario the adaptive admission control and resource allocation algorithm is tested against network metrics, like round trip time and throughput.
During the setup, the researcher wants to test http proxy software written in C programming language that implements an admission algorithm.
-Linux machines for the RUBIS based work load generators-A Linux machine for the hosting the algorithm unit,
capable of compiling C and Java software-Linux machines for running XEN server where on top will run the RUBIS Web app
compile the software and execute it. The user will not have access to the RUBIS resources
all the components are managed based on Virtual machines by a XEN server. The implemented RAS instantiate all these Virtual machines and configure the internal components according to end-user needs.
Figure 3 displays the RADL definition for the RUBIS application server. The Configuration Parameters section describes the exposed parameters to the end user.
and outlook to the enhancements of federated facilities. 2 Experiment Objectives and Requirements for a Concurrent Multipath Transport Alternative multipath transport services in future federated networks might employ concurrent or consecutive
and installation of arbitrary software but is distributed only within Germany, has limited a access, and currently provides no federation method.
Booking of Resources With the SFA software it was possible to book nodes in Planetlab, Planetlab Europe and in the VINI Testbed.
and use arbitrary software on the G-Lab nodes. We assume that such features are of interest for many experimenters,
and software tools to the public and to share their experience. Further, free T-Rex seeks to employ standardized instruments to improve the comparability and openness of scientific results in the field of future Internet research.
in order to experiment on the improvement of Qos features by using the Self-NET software for self management over a Wimax network environment.
which is a software tool that generates traffic at both Uoa end machines. This is a Java based platform that manipulates two independent entities,
and Self-NET software federation (ITGLOG), printing and plotting specific metrics (ITGDEC, ITGPLOT) and remotely controlling the traffic generation (ITGAPI).
The experiment required development of an additional BS control software and deployment of IP routing
We implemented A BS control software (i e. NECM) to allow dynamically collect Wimax link information from the BS
IOS Press, Amsterdam (2010) 7. Airspan homepage, http://www. airspan. com 8. Distributed Internet traffic Generator, http://www. grid. unina. it/software
Manageability of the current network typically resides in client stations and servers, which interact with network elements (NES) via protocols such as SNMP (Simple Network Management Protocol).
Furthermore, the diversity of services as well as the underlying hardware and software resources comprise management issues highly challenging, meaning that currently,
IOS Press, Amsterdam (2009) 10. Organization for Economic Co-operation Development (OECD: The Seoul Declaration for the Future of the Internet Economy.
open-source multimedia framework, player and server, http://www. videolan. org/vlc J. Domingue et al. Eds.):
In 7, the issue of server selection is being investigated by proposing a node selection algorithm with respect to the worst-case link stress (WLS) criterion.
The Cloud technologies are emerging as a new provisioning model 2. Cloud stands for ondemand access to IT hardware or software resources over the Internet.
and the service middleware layer. Each layer is responsible for implementing different functionalities covering the full end-to-end service delivery from the service layer to the physical substrate.
a service middleware layer is introduced to fully decouple the physical infrastructure from the service level.
Network Control Plane NIPS Network+IT Provisioning Services PIP Physical Infrastructure Provider SML Service Middleware Layer VI Virtual Infrastructure VIO Virtual
These procedures are based on a strong inter-cooperation between the NCP+and the service middleware layer (SML) via a serviceto-network interface, named NIPS UNI during the entire VI service life cycle.
These requirements describe not only the characteristics of the required connectivity in terms 19 http://www. ens-lyon. fr/LIP/RESO/Software/vxdl/home. html 316 P. Vicat
The overall architectural blueprint complemented by the detailed design of particular components feeds the development activities of the GEYSERS project to achieve the complete software stack
and evaluate prototypes of the different software components creating and managing optical virtual infrastructures. The other goal is to evaluate the performance and functionality of such a virtualized infrastructure in a realistic production context.
The economic importance of the service sector is a major motivation for services research both in the software industry and academia.
but cloud computing is acknowledged generally to be the provision of IT capabilities, such as computation, data storage and software on-demand, from a shared pool, with minimal interaction or knowledge by users.
-Platform as a service providing services for software vendors such as a software development platform or a hosting service.
e g. the offering of a software service requires infrastructure resources, software licenses or other software services.
, business, software, and infrastructure) on the other. With a set of four complementary use case studies, we are able to evaluate our approach in a variety of domains
) supports arbitrary service types (business, software, infrastructure) and SLA terms, (3) covers the complete SLA and service lifecycle with consistent interlinking of design-time, planning
business, software and infrastructure. The framework communicates to external parties, namely customers who (want to) consume services
Service Managers (infrastructure and software), deployed Service Instances with their Manageability Agents and Monitoring Event Channels.
Infrastructure-and Software Service Managers contain all service-specific functionality. The deployed Service Instance is the actual service delivered to the customer
Business SLA Manager Software SLA Manager Infrastructure SLA Manager Business Manager Service Evaluation Infrastructure Service Manager Software Service Manager Customer
3rd Party Manageability Agent Infrastructure Service<<provider relations>><negotiate>><customer relations>>Monitored Event Channel<<control/track>><evaluate>><prepare/manage>><prepare/manage>><publish>><adjust>>Manageability Agent Software Service<<adjust>>deployed infrastructure service deployed software service<<negotiate>>framework core
The ERP hosting use case (Section 4) contains many aspects of a software cloud. 3. 3 Interlinkage with System Management SLA-driven system management is the primary approach discussed in this paper.
We assume a virtualisation-enabled data centre style configuration of server capacity, and a broad range of services in terms of relative priority, resource requirement and longevity.
Software services could potentially be selected by choosing a virtual machine template which contains pre-loaded applications,
but software layer considerations are considered not core to this Use Case and are dealt more comprehensively with in the ERP Hosting Use Case.
Such a solution typically consists of a software package (an application) but also some business-level activities,
At the next level, there are the actual software applications, such as for example a hosted ERP SOFTWARE package. At the next level, there are the required middleware components
which are used equally for different applications. At the lowest layer, there are the infrastructure resources, delivered through an internal or external cloud.
Each service layer is associated with a dedicated SLA, containing service level objectives which are specific to this layer.
The Application SLA is mainly about the throughput capacity of the software solution, its response time,
The Middleware SLA specifies the capacity of the middleware components, the response time guarantee of the middleware components
and the costs required for the offering. The Infrastructure SLA specifies the characteristics of the virtual or physical resources (CPU speed, memory,
the application, the middleware, and the infrastructure artefacts. From a technical perspective, the most difficult piece in the realization of the whole use case was the knowledge discovery about the nonfunctional behaviour of the different components, e g. the performance characteristics of the middleware.
We collected a set of model-driven architecture artefacts, measurements, best practise rules and managed to consistently interlink them
additionally Service Aggregator integrates software layer (from SLA@SOI framework architecture. And finally Bank prototype is implemented using the top layer, business.
In this way it is necessary to outline also is executed the provision of Telco web service wrappers by Software SLA Manager in an application server
SMS wrappers deployed in the application server of the corresponding virtual machine has to connect and execute different tasks with core mobile network systems that are behind Telefónica Software Delivery Platform (SDP).
The compo 336 J. Butler et al. nents that can be connected also in the use case are the monitors of the services (SMS and Infrastructure services.
while typical software/hardware guarantee terms constraint the quality of each single execution of a service, in this use case the guarantee terms constraint the average value of KPIS computed for hundreds of executions
and capabilities on arbitrary service artefacts, including infrastructure, network, software, and business artefacts. Four complementary industrial use cases demonstrated the applicability and relevance of the approach.
Last, we plan to open up our development activities via an Open source Project. The first framework version fully published as open source can be found at 5. Open Access.
This article is distributed under the terms of the Creative Commons Attribution Noncommercial License which permits any noncommercial use, distribution,
LNCS, vol. 6369, Springer, Heidelberg (2010) 5. SLA@SOI Open source Framework. First full release by December 2010, http://sourceforge. net/projects/sla-at-soi 6. SLA@SOI project:
Using the TCP IP protocols architecture there are some limitations for the software-driven control network infrastructure
can also contribute to the translations of the MBT (Model-based Translator) software package, by the use of the FINLAN formal representation in OWL.
The Autoi open source implements a scalable and modular architecture to the deployment, control and management of active sessions used by virtual entities.
Based on the Autoi Java open source, in the ANPI demo, the ANPISDD class is prepared to use the IP and TCP (port 43702) protocols.
as in the following sample code extracted from the ANPISDD. java code. 348 E. Santos et al. public class ANPISDD extends Thread {private Serversocket server;
+""s1=server. accept(;.With the use of the FINLAN library this communication can be done replacing the IP
Nevertheless, the future intentions are to implement the FINLAN ontology in Linux operating system kernel level,
since the methods proposed would be available at the operating system level. 4 Conclusions This paper has presented the FINLAN ontology works in a collaboration perspective with some Future Internet projects.
Future work will implement the FINLAN ontology at the Linux kernel level and run performance
Platforms and Software systems for an Autonomic Internet. In: IEEE Global Communications Conference (2010) 14 Rubio-Loyola, J.,Astorga, A.,Serrat, J.,Lefevre, L.,Cheniour, A.,Muldowney, D.,Davy, S.,Galis
so that software agents are able to process and reason with the information in an automatic and 352 J. Domingue et al. flexible way.
and consuming of functionalities of existing pieces of software. In particular, WSDL is used to provide structured descriptions for services, operations and endpoints,
which links service descriptions with users ratings, tags and comments about services in a separate server.
This addressing scheme should be easily resolvable such that software clients are able to access easily underlying descriptions.
Architectural styles and the Design of Network-based Software Architectures. Phd Thesis, University of California (2000) 8. Mcilraith, S. A.,Son, T. C.,Zeng, H.:
Third, the todays'software technologies support the creation and composition of services while being able to take into account information regarding the transport/terminal contexts
the SM@SP instructs the SP/CP servers how to mark the data packets. The information to be used in content aware classification can be:
AS1 AS2 AN HB SP/CP server AS3 VCAN1/MQC1 VCAN2/MQC2 VCAN3/MQC3 L2, L3, L4 headers High level headers
or co-locating CP's content servers in NPS'premises, nevertheless, an individual CC may also be a private CP.
IOS Press, Amsterdam (2009) 4. Schönwälder, J.,et al.:Future Internet=Content+Services+Management. IEEE Communications Magazine 47 (7), 27 33 (2009) 5. Zahariadis, T.,et al.:
IOS Press, Amsterdam (2009) 6. Huszák, Á.,Imre, S.:Content-aware Interface Selection Method for Multi-Path Video Streaming in Best-effort Networks.
IOS Press, Amsterdam (2009) 8. Martini, M. G.,et al.:Content Adaptive Network Aware Joint Optimization of Wireless Video Transmission.
IOS Press, Amsterdam (2009) 10. Anderson, T.,et al.:Overcoming the Internet Impasse through Virtualization. Computer 38 (4), 34 41 (2005) 11.
due to a bandwidth bottleneck at the server side from which all users request the content.
MDC combined with path/server diversity offers robust video delivery over unreliable networks and/or in peer-to-peer streaming over multiple multicast trees.
Performance evidence of software proposal for Wavelet Video Coding Exploration group, ISO/IEC JTC1/SC29/WG11/MPEG2006/M13146, 76th MPEG Meeting, Montreux
and search engines are expected to be able to understand underlying semantics in content and match it to the query.
and these combinations require the federation and integration of appropriate software building blocks. A new generation of enterprise systems comprising applications
fine-tuned to the needs of enterprise users by leveraging a basic infrastructure of utility-like software services.
Future Internet, Future Enterprise Systems, component-based software engineering, COTS, SOA, MAS, smart objects, FINES, FINER. 1 Introduction In recent years, software
and realising enterprises software applications. In essence, while enterprise management and planning services will be increasingly available from the‘cloud',in a commoditised form,
the Internet of Services (Ios), Internet of things (Iot) and smart objects, Internet of Knowledge (Iok), Internet of People (Iop.
Together, they need to cooperate in developing a new breed of services, tools, software packages, interfaces and user interaction solutions that are not available at the present time.
In particular on the first and the second GRC that concern the development of new FINESS capable of offering to the business experts the possibility of directly governing the development of software architectures.
if such software architectures will correspond to the enterprise architectures, and will be composed by elements tightly coupled with business entities.
seen as the new frontier to software components aimed at achieving agile system architectures. Section V provides some conclusions
methods and tools, supporting the idea that large software systems can be created starting from independent, reusable collections of preexisting software components.
This technical area is referred often to as Component Based Software engineering (CBSE. The basic idea of software componentization is quite the same as software modularization,
but mainly focused on reuse. CBSE distinguishes the process of"component development"from that of"system development with components 9. CBSE laid the groundwork for the Object oriented Programming (OOP) paradigm that in a short time imposed itself over the preexisting modular software development techniques.
OOP aims at developing applications and software systems that provide a high level of data abstraction and modularity (using technologies such as COM,.
, NET, EJB and J2ee. Another approach to componentization is that of the Multi Agent Systems (MAS),
heterogeneous, interacting software agents. Agents mark a fundamental difference from conventional software modules in that they are inherently autonomous and endowed with advanced communication capability 10.
On the other side, the spread of the Internet technologies and the rising of new communication paradigms, has encouraged the development of loosely coupled and highly interoperable software architectures through the spread of the Service-Oriented approach,
and the consequent proliferation of Service-Oriented Architectures (SOA). SOA is an architectural approach whose goal is to achieve loose coupling among interacting software services, i e.,
, units of work performed by software applications, typically communicating over the Internet 11. In general, a SOA will be implemented starting from a collection of components (e-services) of two different sorts.
Some services will have a‘technical'nature, conceived to the specific needs of ICT people; some other will have a‘business'nature,
where business expert can directly manage a new generation enterprise software architectures. Cloud computing represents an innovative way to architect
and the hardware and system software in the datacenters that provide those services 12. Cloud computing may be considered the basic support for a brand new business reality where FINERS can easily be searched,
to ease software development processes. Conversely, we propose to base a FINES architecture on building blocks based on business components.
with the protocols for issuing (as client) or responding (as server) to request messages. It is structured according to the grounding of OWL-S. 2 http://esw. w3. org/Sweoig/Taskforces/Communityprojects/Linkingopendata 3 Universal Resource Identifier,
Iot, Ios, Multi-Agent Systems, Cloud computing, Autonomic Systems) and, in parallel, some key areas of the enterprise that will start to benefit of the FINES approach.
Environmental Modelling & Software 24 (5)( 2009) 9. Crnkovic, I.,Larsson, S.,Chaudron, M.:Component-based Development Process and Component Lifecycle.
Component-oriented software development, Special issue on alaysis and modeling in software development, pp. 160 165 (1992) 11.
IOS Press, Amsterdam (2010) 16. Papazoglou, M. P.:Web Services: Principles and Technology. Prentice-hall, Englewood Cliffs (2007) 17.
and in the server farms is considered not since no special equipment is deployed in the GSN.
in comparison to electronic equipments such as routers and aggregators 4. The migration of virtual data centers over network nodes is indeed a result of a convergence of server and network virtualizations as virtual infrastructure management.
MANTICORE II continued in the steps of its predecessor to implement stable and robust software while running trials on a range of network equipment.
PDU Servers (Dell Poweredge R710) To core network Wind power node architecture (Spoke) Switch (Allied Telesis) Raritan UPS (APC) PDU Servers (Dell
wind and solar types) 424 K. K. Nguyen et al. by green energy and adjust the network to the needs controlled by software.
such as routers and servers, is considered not, because no special hardware equipment is used in the GSN.
The solar panels are grouped in bundles of 9 or 10 panels, each panel generates a power of 220-230w.
The wind turbine system is a 15kw generator. After being accumulated in a battery bank, electrical energy is treated by an inverter/charger in order to produce an appropriate output current for computing and networking devices.
Within each node, servers are linked by a local network, which is connected then to the core network through GE transceivers.
then pushes Virtual machines (VMS) or software virtual routers from the hub to a sun or wind node (spoke node) when power is available.
which is a new software platform specific for dealing with the delivery of computing infrastructure 5. Figure 3 compares the layered architecture of the GSN with a general architecture of a cloud comprising four layers.
such as storage servers and application servers linked by controlled circuits (i e.,, lightpaths. The Platform Control plane corresponds to the Core Middleware layer,
implementing the platform level services that provide running environment enabling cloud computing and networking capabilities to GSN services.
The Cloud Middleware plane corresponds to the User-level Middleware, providing Platform as a service capabilities based on Iaas Framework components 5. The top Management plane or User level focuses on application services by making use of services provided by the lower layer
Such a migration is required for large-scale applications running on multiple servers with a high density connection local network.
This results in a reconfiguration of a large number of servers and network devices in a multi-domain environment.
and that each server has up to 16 processors, 20 servers can be moved in parallel. If each VM consumes 4gbyte memory space,
the time required for such a migration is 1000sec. The migration of data centers among GSN nodes is based on cloud management.
and converges server and network virtualizations. Whilst most of cloud management solutions in the market focus particularly on computing resources,
An orchestration middleware is built to federate clouds across domains, coordinate user registration, resource allocation, stitching,
and leverage and interoperate with software outside of the GSN. Along with the participation of international nodes, there is an increasing need of support for dynamic circuits on GSN
including virtual servers and virtual routers and/or virtual switches interconnecting the servers. Such a virtual data center can be hosted by any physical network node, according to the power availability.
There is a domain controller within each data center or a set of data centers sharing the same network architecture/policy.
Extending the Argia software with a dynamic optical multicast service to support high performance digital media.
section 5 presents conclusions and an outlook. 2 City and Urban Development Challenges In the early 1990s the phrase"smart city"was coined to signify how urban development was turning towards technology,
middleware and agent technologies as they become embedded into the physical spaces of cities. The emphasis on smart embedded devices represents a distinctive characteristic of smart cities compared to intelligent cities
large scale ontologies and semantic content Cloud services and software components City-based clouds Open and federated content platforms Cloud-based fully connected city Smart systems based on Internet of things Smart power management Portable systems Smart systems enabling integrated solutions e g. health
and care Software agents and advanced sensor fusion; telepresence Demand for e-services in the domains outlined in Fig. 1 is increasing,
There is a critical gap between software applications and the provision of e-services in terms of sustainability and financial viability.
Open source communities may also substantially contribute to the exchange of good practices and open solutions.
and developers. 444 H. Schaffers et al. 5 Conclusions and Outlook In this paper we explored the concept of smart cities as environments of open
and its particular components, Internet of things (Iot) and Internet of Services (Ios), can become building blocks to progress towards a unified urban-scale ICT platform transforming a Smart City into an open innovation platform.
and at the service level (Ios as a suit of open and standardized enablers to facilitate the composition of interoperable smart city services).
and interoperable communication protocols where physical and virtual things are integrated seamlessly into the information network 5. The Internet of Services (Ios):
namely Iot and Ios, can be essential building blocks in future Smart Cities open innovation platforms.
and Ios as ICT Building blocks for Smart Cities In the analysis from Forrester research 9 on the role that ICT will play in creating the foundation for Smart Cities,
Ios evolution must be correlated undoubtedly with Iot advances. Otherwise, a number of future Smart City services will never have an opportunity to be conceived due to the lack of the required links to the real world.
and challenges of implementing Iot and Ios at the city scale. Starting with the benefits of Iot technologies, they are twofold:
Considering now the Ios, it must be stressed that it is recognized widely (see for example 12) that the real impact of future Iot developments is tied heavily to the parallel evolution of the Ios. So,
a Smart City could only become a true open innovation platform through the proper harmonization of Ios and Iot.
Thus the integration of innovative principles and philosophy of Ios will engage collective end-user intelligence from Web 2. 0
The technological challenge of developing the Ios has been assumed at EU level, and actions are being initiated to overcome the undesirable dissociation between technological
Experimental Testbeds Ad hoc WSN Deployments Iotresources (sensor & actuator networks) Ios resources Testbed 1 USN-Enabler Service 1 Adaptation& Homogeneization Testbed
Control Layer GSDP SDP Entity exposure Service exposure Ios federation level Iot federation level NGN/Telco2. 0 Web2. 0 Service
Layer Fig. 1. Global Service Delivery Platform (GSDP) integrating Iot/Ios building blocks 3 Developing Urban Iot Platforms At present, some works have been reported of practical implementations
This capability will allow a seamless link between Iot and Ios, as discussed in Section 2. Also relevant will be the definition of open APIS,
and the proper basement for the new heterogeneous sensor network infrastructures needed to enable an evolving FI based on the Iot and Ios paradigms.
Node WISELIB User Developed App Tinyos Contiki Sunspot Opencom Middleware Mobility support Horizontal support Federation support Security, Privacy and Trust Fig
research and service oriented initiatives on both Iot and Ios areas as WISEBED 25, SENSEI 8 and the USN Iot Platform (presented in Section 3) including Web 2. 0 and Telco 2. 0 design principles.
the Smartsantander middleware) that provide the functionality described by these requirements and is expected to accommodate additional requirements coming up from the different smart city services (use cases).
through Iot and Ios, for creating new real-life applications and services is huge in the smart city context.
providing the key components required to intertwining Iot and Ios worlds. Referred Iot USN platform is currently being evolved with the addition of new capabilities
) Towards the Future Internet, IOS Press, Amsterdam (2009) 17. Fisher, S.:Towards an Open Federation Alliance.
Overtext Web Module V3.0 Alpha
Copyright Semantic-Knowledge, 1994-2011