Blog of Random Thoughts and Pictures

Looking back on a project that is 4WARD

September 6th, 2010

The ICT 4WARD project has come to a close and it’s time to reflect on what was been billed as a clean slate project which was to combine sets of radical architectural approaches towards the future Internet, building on a strong mobile and wireless background to design inter-operable and complementary families of network architectures.

4WARD was my first project in the FP7 programme, and was quite different from the FP6 projects that I participated in, FP7 has been an interesting experience to say the least! Work on the proposal started in the summer of 2006, and took 8 months to complete, and then another 8 months were taken with its review and contract negoations with the project itself starting in ernest on Janurary 1st 2008.
30 months later, after 7 project meetings stretching from Lisbon to Stockholm and in excess of 32,000km travelled, upteen conference calls and many many more wiki updates, I come to the end of 4WARD.
Well I have to say I worked with some hugely talented people in the project, with Patsy, Zohra, Chris and Eamonn making huge strides to further our research in component based architecture, domain specific languages and in-network management, and all of this work is reflected in the delieverables of 4WARD, which are the main visable output from a project.
D-2.1 Technical Requirements
D-2.2 Draft Architectural Framework
D-2.3.0 Mechanisms for Generic PathsArchitectural Framework: new release and first evaluation results
D-2.3.1 Final Architectural Framework

D-4.1 Definition of Scenarios and Use Cases
D-4.2 In-Network Management Concept
D-4.3 In-network management design
Papers are also a clear output form the project and I collaborated on 6 specific 4WARD papers:
1. In the paper “Towards a New Architectural Framework; The Nth Stratum Concept“, we presented our new architectural framework called the Nth Stratum concept, which takes a holistic approach to tackle these new needs and requirements on a future communication system.
2. In the paper “A Framework for In-Network Management in Heterogeneous Future Communication Networks“, we proposed the radically new paradigm of in-network management, which targets the embedding of self-management capabilities deep inside the network nodes. In this paper, we focus on our framework for in-network management, which allows management logic to be embedded and executed within network nodes. Based on a specific use-case of bio-inspired network management, we demonstrate how our framework can be exploited in a network failure scenario using quorum sensing and chemotaxis.
3. In the paper “Mobility Scenarios for the Future Internet: The 4WARD Approach”, we highlight the 4WARD research approach to make a vision of a “network of information” reality. New system design methods for customized architectures on flexible network platforms will be combined with the capabilities of virtualization of all network resources including the wireless access. Together with a new generic path concept for flexible interconnection of objects of any type and a new paradigm for naming, addressing and managing mobile objects, the envisaged “network of information” model will be constructed.
4. In the paper “Architectural Principles and Elements of In-Network Management” we propose the in-network management (INM) paradigm, which adopts a clean slate design approach to the management of future communication networks that is brought about by evolutionary design principles. The proposed paradigm builds on embedded management capabilities to address the intrinsic nature, and hence, close relationship between the network and its management. At the same time, INM assists in the gradual adoption of embedded self-managing processes to progressively achieve adequate and practical degrees of INM. We demonstrate how INM can be exploited in current and future network management by its application to P2P networks.
5. In the paper “An Introduction to Network Stack Design using Software Design Patterns” we present our architectural framework which proposes a component-based architecture consisting of building blocks of reusable functionality, components that allow the construction of these building blocks and the composition of complex functionality, control elements facilitating communication between blocks, and a repository of building blocks. The architecture allows for rapid composition of federations of components, enabling an easy transition from present network infrastructure towards the future Internet and realizing the on-demand creation and configuration of protocol stacks for components.
6. In the paper “A Case Study for defining Interoperable Network Components using MDD”, we present a case study using Model Driven Development addressing interoperability requirements in next generation networks. Our approach focuses on the specification of a high level Contract Domain Specific Language we combine Component-based Software Engineering for the design with our long-term experience of network resource management and performance optimisation. Part of our case study is a tool chain that supports the network engineers who deploy next generation networks.
None of these papers would have seen the light of day without the kind support and drive of my co-authors who included Patsy, Zohra, Sven, Chris, Eamonn, Sasi, Dmitri, D. Dudkowski, M. Brunner, G. Nunzi, C. Mingardi, C. Meirosu, S. Engberg, M. Söllner, C. Görg, K. Pentikousis, J. Mª Cabero Lopez, P. Bertin, M. Johnsson, J. Huusko, T. Frantti, F-U Andersen and T-M-T. Nguyen. I have gained many friends going through this process.
Finally the one surprise output from the project has been the open source release on the CBA concept, which has been the seed for OpenTinos. All in all I see the support of OpenTinos keeping me quite busy in the coming months.

Technical Requirements for the Future Internet and Definition of scenarios and use cases for In_Network Management

December 12th, 2008

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, 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”.
I’ve given a more general overview of the document on on the main TSSG 4WARD page. Just to say most of my contribution in this document was towards the consolidation of the WP2 new architecture requirements and the WP4 in-netwrk management requirements.
In WP2 we are developing an architecture framework that is flexible enough for specifying and realising a new family of interoperable network architectures with varying degrees of desired properties according to the needs of the targeted networking scenario (e.g., in a backbone network, a sensor network, or a mobile ad hoc network) while ensuring certain common principles and properties (e.g. interoperability, security, mobility, quality of service). Hence this framework has to take into account a multitude of network variants in order to facilitate the design of the “best” network for each task, each device, each customer, and each technology.
I also had a part to play in pulling together the requirements for WP4 for In-Network Management in which 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”. The guiding principles to achieve this goal are decentralisation and self-organisation.
The realisation of the In-Network Management paradigm includes developing a network management plane that self-configures and dynamically adapts to changes in networking conditions. The plane provides communication and coordination primitives for a range of distributed management functions.
4WARD In-Network Management addresses these challenges by introducing a thin, pervasive layer which performs core management functionalities already inside the network, but which can be complemented by additional management functionality outside the network where necessary.
For more information in relation to this 4WARD In-Network Management there is an public deliverable available D4.1 Definition of scenarios and use cases [pdf]
I must admit it is still early in the project and there are a number of significant advances being made, however at times it feels as though there are some many things happening in parallel its hard to keep up with everthing going on.