4WARD

Overview:
In essence, the CBA prototype consists of a fully functional componentised IPv4 network stack and the ancillary supporting infrastructure. The network stack is implemented as a set of software components. A component typically is a well-defined unit such as a protocol e.g. TCP is a single component. These components are then deployed as an OSGi based application within an application server (Spring DM Server).

The CBA network components (ARP, IP, TCP, UDP,...) have been ported from the JNode operating system. These OSGi components are then grouped into an application instance for deployment within the SpringDM [spring-09] application server. These application instances are entirely isolated and self-contained from each other in the application server allowing for multiple network stack instances to co-exist in isolation - in other words multiple network stacks running independently. The underlying network medium “ethernet” is provided by using Extensible Messaging and Presence Protocol (XMPP) as a network network overlay across which the stacks can communicate.

The CBA network stack applications function as completely independent and isolated virtual nodes. Further components (e.g. traffic generators) can be added into the OSGi applications which then use the CBA stack to perform the inter-node network communication.

Java New Operating system Design Effort (JNode) [jnode-09] is an open-source project to create a Java platform operating system. The project has taken the unique direction of creating all the software in java itself, with the exception of some assembly language to boot and load the system. JNode has an entirely java based Internet Protocol, version 4 (IPv4) network stack which has been proven in the field.

The OSGi framework [All07] is a module system for Java that implements a complete and dynamic component model, something that does not exist in standalone Java Virtual Machine (JVM) environments. Applications or components (coming in the form of bundles for deployment) can be remotely installed, started, stopped, updated and uninstalled without requiring a reboot; management of Java packages/classes is specified in great detail. Life cycle management is done via APIs which allow for remote downloading of management policies. The service registry allows bundles to detect the addition of new services, or the removal of services, and adapt accordingly.

License
LGPL : http://www.gnu.org/licenses/lgpl.html
The reason behind the selection of the LGPL license is based primarily on the code base that has been ported from the JNode project. The JNode project uses the LGPL license. All modified source code must remain under this license and it is efficient to keep additional source code contributed by WIT under the same license as they may be intermixed within the same organisational packages.

This license has also facilitated the fostering of partnership with the JNode project for future development and cooperation. The JNode project can import code updates from the WIT code base and vice versa in order to progress network protocol functionality.
The LGPL license will apply to all users of the code base. This also includes the partners within 4WARD as the LGPL already applies to existing (modified) code from the JNode project.

Availability
The source code for the CBA prototype is contained under the url of the readme file: https://www.tssg.org/4WARD/opensource/README.txt

At this location a set of jar files for the protoytpe are stored in the directory. All that's provided here is either 4WARD written code or code which has been modified from the JNode open source project.

org.tssg.actions.ping-sources-1.0.0.jar
org.tssg.bootstrap.agent-sources-1.0.0.jar
org.tssg.bootstrap.api-sources-1.0.0.jar
org.tssg.bootstrap.driver-sources-1.0.0.jar
org.tssg.config.dao-sources-1.0.0.jar
org.tssg.config.stack-sources-1.0.0.jar
org.tssg.driver.net.idrive-sources-1.0.0.jar
org.tssg.org.jnode.driver.net.loopback-sources-1.0.0.jar
org.tssg.org.jnode.net.arp-sources-1.0.0.jar
org.tssg.org.jnode.net.ethernet-sources-1.0.0.jar
org.tssg.org.jnode.net.ipv4-sources-1.0.0.jar
org.tssg.org.jnode.net.ipv4.config-sources-1.0.0.jar
org.tssg.org.jnode.net.ipv4.icmp-sources-1.0.0.jar
org.tssg.org.jnode.net.ipv4.layer-sources-1.0.0.jar
org.tssg.org.jnode.net.ipv4.resolver-sources-1.0.0.jar
org.tssg.org.jnode.net.ipv4.tcp-sources-1.0.0.jar
org.tssg.org.jnode.net.ipv4.udp-sources-1.0.0.jar
org.tssg.org.jnode.net.support-sources-1.0.0.jar
org.tssg.socket.tcp-sources-1.0.0.jar
org.tssg.socket.udp-sources-1.0.0.jar
org.tssg.support.jnode-sources-1.0.0.jar
org.tssg.transport.im-sources-1.0.0.jar
org.tssg.transport.im.configmanager-sources-1.0.0.jar
org.tssg.transport.im.logger-sources-1.0.0.jar

References:
[jnode-09] JNode Open Source Project. 2009. url: http://www.jnode.org.
[All07] OSGi Alliance. OSGi Service Platform, Core Specification, Release 4, Version 4.1.
OSGi Alliance, 2007. isbn: 9789079350018.
[spring-09] SpringDM - OSGi based Application Server. 2009. url: http://www.springsource. com/products/dmserver

4WARD Partners Involved:
WP2: WIT (TSSG) – Sole Generator of code-base.

CBA lead Patsy Phelan commented on today's release "Awesome".

The deliverable D-4.3 In-network management design is available for review and comment.

This deliverable D-4.3 reports on 4WARDs work developing the novel paradigm of In-network Management (INM), aimed specifically at the effective management of large, dynamic networks.

Its basic enabling concepts are decentralization, self-organization, and autonomy. The idea is that management tasks are delegated from management stations outside the network to the network itself. The INM approach therefore involves embedding management intelligence in the network, or, in other words, making the network more intelligent. The managed system now executes management functions on its own. It performs, for instance, reconfiguration or self-healing in an autonomic manner.

This deliverable describes the main results of WP4 achieved during the second year of the 4WARD project and it complements deliverable D-4.1, which presents use cases illustrating the potential of INM capabilities. First, it contains the design of the INM framework, an enabler of management functions that defines a set of architectural elements from which any distributed and embedded management structure can be created. Second, it presents algorithms for situation awareness in real-time and self-adaptation that provide a subset of management functions that we regard as important and challenging for the management of the future Internet. Third, it outlines our work towards an INM prototype due in June 2010.

Finally, the document reports on the results of WP4 INMs close collaboration with other WPs in the 4WARD project.

This summer school programme was devised by the 4WARD team to provide courses, labs, presentations, PhD poster sessions, panel discussion, and invited talks on the topic of the Future Internet, by leading experts from European projects and other international partners.

Links to the presentations and invited talks can be found on the main website for the summer school. which include

* Future Internet Architecture by: Martina Zitterbart, Universität Karlsruhe (TH), Germany;
* Views on the Future Internet by: Norbert Niebert, Ericsson, Germany;

* Future Internet Research in Europe by: Paulo de Sousa, European Commission;

* Special Invited Plenary Short Course: (CCN) Content Centric Networking by: Van Jacobson, PARC Research, USA;

* Security and Dependability Issues of the Future Internet by: Syed Naqvi, CETIC, Belgium;

* Network Virtualization by: Stephan Baucke, Ericsson EDD, Germany;

* What QoS for the Future Internet? by: James Roberts, Orange Labs, France;

* Accessing WiFi Networks from Moving Vehicles by: Samir R. Das, Stony Brook, University SUNY, NY U.S.A.,

* Recursive Network Archtitecture by: Joe Touch, USC/ISI, USA;

Some of the course material is also avaialble on
* ORBIT Hands-on-Tutorial by: Ivan Seskar, WINLAB, Rutgers University, USA

* Mobility and Multiaccess in Emerging Internet Architectures by: Kostas Pentikousis, VTT Technical Research Centre of Finland, Finland

Towards a Network of Information by: Kostas Pentikousis, VTT Technical Research Centre of Finland, Finland

* Delay Tolerant Networking by: Carsten Bormann, University of Bremen, Germany; and Ioannis Psaras, University of Surrey, United Kingdom

* ANA - 'Autonomic Network Architecture' Tutorial and Lab by: Christian Tschudin; Christophe Jelger; and Ghazi Bouabene, University of Basel

* Network Virtualization by: Panagiotis Papadimitriou, Lancaster University, United Kingdom; Yasir Zaki, University of Bremen, Germany; Liang Zhao, University of Bremen, Germany, Asanga Udugama, University of Bremen; Ingo Grothues, Ericsson EDD, Germany; and Carmelita Görg, University of Bremen, Germany

* From Distributed Management to In-Network Management by: Rolf Stadler, KTH Royal Institute of Technology, Stockholm, Sweden; and Danny Raz, The Technion, Haifa, Israel

* Interdomain Routing and Traffic Engineering by: Pedro A. Aranda Gutiérrez, Telefónica I+D, Spain

Business Models of the Future Internet by: Mario Kind, Deutsche Telekom AG, Laboratories, Germany

* Interference Management in Wireless Networks by: Samir R. Das, Stony Brook University, SUNY, NY U.S.A.

* The Generic Path by: Hagen Woesner, TU Berlin, TKN, Germany

The deliverable D4.2 In-Network Management Concept is available for review and comment.

This deliverable reports on our progress towards developing the paradigm of In-network Management (INM), a clean-slate approach to network management, aimed specifically at the effective management of large, dynamic networks, where a low rate of interaction between an outside management entity and the network will be required. The idea is that management tasks are delegated from management stations outside the network to a self-organizing management plane inside the managed system. This is enabled through decentralization, self- organization, embedding of functionality and autonomy. Under this paradigm, the managed system executes functions –locally or end-to-end– on its own and performs, for instance, reconfiguration or self-healing in an autonomic manner. It reports results of its action to an outside management system or triggers exceptions if intervention from outside is needed.

The deliverable describes the main results of WP4 achieved during the first year of the project and it complements deliverable D-4.1, which presents use cases illustrating the potential of INM capabilities. It contains a first version of the INM framework design, which defines the structure of the management plane inside the network, supports the embedding of management functions and provides reusable components to compose collaborating self- managed entities. Second, it presents a set of algorithms and concepts developed for real- time management, with emphasis on distributed monitoring in large-scale dynamic environments. Third, it reports on work that demonstrates the feasibility of rapid re- configurability for selected management algorithms and functions under the INM paradigm. Extensive simulations have demonstrated the effectiveness of the approach and have quantified key trade-offs.

The report ends with an outlook of the project plans for the second year, where effort will be devoted to proving the technical feasibility through prototype implementation of selected functions and integration of the work with that other WPs.

The deliverable D2.2 Draft Architectural Framework is available for review and comment.

This particular document presents a first stage and intermediate summary of WP2 work with respect to an Architecture Framework, and attempts to model new Network Architectures, highlighting 4WARD defined concepts, terms and the basic constructs in this arena.

In the context of the Future Internet it is envisioned that different network architectures can coexist and share a common infrastructure. These network architectures can be specifically tailored to particular user or application requirements and, furthermore, can take into account the characteristics of the available networking resources.

The 4WARD Architecture Framework provides two views on network architectures and its resources:
(i) the macroscopic view mainly focuses on structuring the network at a higher level of abstraction and introduces the concept of Strata as a flexible way to layer the services of the network; and
(ii) the microscopic view concentrates more on the functions needed in the network, their
selection and composition to Netlets that are instantiated in the physical nodes of the
network.

The Design Process represents the workflow ranging from a business idea as a starting point to the design of network architecture models (NAM) and software architecture models (SAM). This is followed by the instantiation and operation of a network architecture fulfilling the detailed technical requirements derived from the business idea. At this point in time, the Component Based Architecture (CBA) comes into play. It represents the link between the modelling of the network architecture to its deployment in a platform specific implementation.

Even though the main phase’s goals of the Design Process have been specified, it however needs more work on specific details including, for example, the transition steps between the three major phases of detailed technical requirements analyses, NAM design and SAM design. Moreover, aspects related to the interoperability and composition of functions will be more detailed in the second year of the project. This also holds for the specification of the Design Repository. Although the described Design Process is seen as an off-line process (it is not applied during the run-time), the network architecture that are designed during this Design Process may be highly adaptable during run-time allowing the easier introduction of networks services during networks run-time.

The composition of functionalities has focused on the way functions needed to fulfil a detailed technical requirement derived from the initial business idea can be composed. This forms the basis for the definition of protocols to be applied in order to meet the specific requirements. Some first examples on how to efficiently combine very basic functionalities to build new protocols and Netlets have been also described.

In order to evaluate the applicability of the Architecture Framework, three use cases were defined and utilized as application examples. The use cases were selected in a way that they reflect challenging requirements that are foreseen in the Future Internet, mainly with focus on the integrated support of QoS, security and mobility. They were applied to the macroscopic view as well as to the microscopic view. They will be used for further re-fined evaluations. In this context more precise evaluation criteria will be formulated based on what has been reported in D2.1

The task of WP2 is to derive an Architecture Framework that allows for an efficient and effective design of tailored network architectures. In order to evaluate this, the Framework has to be applied to different challenges. In this respect, the developments of other WPs of 4WARD were explored in some detail. Note, however, that the developments within WP2 and those of the other WPs reflect work in progress. As a first conclusion, most of the solutions being developed in other WPs of 4WARD are well represented within the Architecture Framework being defined in WP2. More details need to be derived in the following period of the 4WARD project.

This D4.1 Definition of Scenarios and Use Cases for In-Network Management is the first deliverable coming out of the In-Network Management work package of 4WARD. It describes a core set of scenarios and use case that will guide the further work performed in the work package.
The goal of In-Network Management is to overcome limitations of traditional network management: it is developing engineering principles for automated configuration management, but also real-time monitoring functions that trigger adaptation of configuration. In-Network Management will support future large-scale networks that self-configure, dynamically adapt to external events and allow for low-cost operation. Its key idea is that management stations outside the network delegate management tasks to a self-organizing management plane inside the network.
In order to kick-off the work on In-Network Management a problem-driven approach has been adopted. As starting point for the research concrete scenarios and use cases have been selected that allow for a fundamental analysis of management problems encountered in the future Internet.
The four scenarios that have been selected highlight the wide range of challenges. They address self-management in wireless multi-hop networks, network management for a large operator network, management needs of home network environments, and management strategies availability under extreme conditions like catastrophes and natural disasters. For each scenario major use cases have been identified that analyse in more detail and on a concrete level the specific problems of that particular environment.
Based on the scenarios, evaluation criteria are derived that provide guidance for the follow-up activities in the work package and also offer the opportunity of a common ground for the cooperation between the other project work packages to help in the integration into a coherent overall framework of the various tracks of research performed by 4WARD.

This D2.1 is one of the 1st public deliverables of 4WARD [pdf] and it describes the technical requirements for a family of future global communication networks (referred to as “4WARD Framework” throughout the document), with the potential to supersede current telecommunication networks as well as the current “internet” in the long run, as identified in the first phase of the FP7 project “4WARD”.

First, the document describes briefly the mission and objectives of the project and the future network technology research areas in the work packages; as well as the followed methodology to collect the views from the different work packages. Then the aspects and the guidelines from the main non-technical perspectives (usage and services; socio-economics; regulation, governance and policy) are discussed. Based on those considerations, the overall technical requirements are derived and related to the views of the different technology areas as well as of the vertical technical themes (mobility, security, quality of service, inter-provider issues, and physical layer awareness). The detailed requirements are listed in the annex of the document.
The overall technical requirements for the 4WARD Framework listed in this document shall serve as a mandatory benchmark for the research directions and results expected by the project 4WARD, i.e. for the further design of specific 4WARD Networks, and may give useful guidelines for any activities towards a “Future Internet”.
The non-technical concerns are focusing on the expected demand created by new innovative services and applications, not only for a growing world population but also in a world of “connected things”. Special considerations have been given to the aspects of sustainability, awareness of environmental aspects, usability for everybody, and overcoming the shortages of the current internet concerning security, privacy vs. governance and control.

The technical requirements derived thereof are grouped around the following topics:
• services and application support for an information-centric network, covering also quality of services issues and usability
• mobility and wireless awareness,
• availability, scalability and extensibility
• interoperability, self-management, virtualisation
• security and privacy.
With this set of requirements as a starting point, further iterations during the design of specific 4WARD Networks will have to deal with an appropriate selection of these requirements still guaranteeing interoperability of dependent 4WARD Networks under the overall mission.

Summary of 4WARD

Today’s network architectures are stifling innovation, restricting it mostly to the application level while the need for structural change is increasingly evident. The absence of adequate facilities to design, optimize and interoperate new networks currently forces a convergence to an architecture that is suboptimal for many applications and that cannot support innovations within itself, the Internet. 4WARD overcomes this impasse through a set of radical architectural approaches built on our strong mobile and wireless background. 4WARD will improve the ability to design inter-operable and complementary families of network architectures. 4WARD enables the co-existence of multiple networks on common platforms through carrier-grade virtualization for networking resources. 4WARD will enhance the utility of networks by making them self-managing. 4WARD will increase their robustness and efficiency by leveraging diversity. Finally 4WARD will improve application support by a new information-centric paradigm in place of the old host-centric approach. These solutions will embrace the full range of technologies, from fibre backbones to wireless and sensor networks.

In this project the TSSG is working on two specific research themes. One is towards the architecture where the TSSG is developing an integrated framework to represent, design, implement and operate network architectures that all belong to a common family of interoperable network instances.

The second is towards in-network management were we are devising an embedded "default-on" management capability which is an inseparable part of the network itself. This capability will generate extra value in terms of guaranteed performance in a cost effective way, and will enable the networks to adjust themselves to different sizes, configurations and external conditions.

4WARD is currently Running and is funded by the European Union FP7 ICT work programme, under Call 1 to a total of €14.5 million euro. The project started in January of 2008 and will end in February 2010.

TSSG contact details
For more information contact miguelpdl@tssg.org or visit the TSSG website at http://4ward.tssg.org or the 4WARD website at http://www.4ward-project.eu/.

Tel: +353 51 302952
Tel: +353 51 302900
Fax: + 353 51 302901