Management and Networking Architectures

From FutureInternetWiki

Jump to: navigation, search

Management and Service Networking Architectures and Intrastructures - Cross Domain Topic for Future Internet Assembly

Contents

[edit] Working Group Manifest

Alex Galis - University College London <a.galis@ee.ucl.ac.uk> - 7th May 2008

Management and Service Networks Architectures (MANA) as enablers for Future Internet (FI) of Systems ( Networks, Services, Contents)


Problems: Many identified bottlenecks of the current Internet of Networks and Services including ossification and non-imbedded manageability.


Systemic Research Scope:

Define Service Networks Architectures (i.e. Connectivity & Computation Infrastructures & Resources) & self-management and controls of such resources

• Define Ubiquitous Virtual Resources & self-management of virtual resources- integrated and flexible usage of heterogeneous and assumable virtual resources for networking, computation, storage, content, mobility, etc

Define cross-domain (self) Management functions (i.e. networks, services, content) and cross-layers cooperative FI systems design for integrated management functionality, including: system lifecycle -, monitoring-, (re)configuration- , optimisation- , organisation- , performance- , adaptation- , context- , semantic- , security- , composition- , assurance- , negotiation- , repository- , SLA- , QoS- , billing- , * Functions-management)

Imbedding management functionality in all FI systems (i.e. InNetworks management, InServices management, InContent management)

Define and Manage Ubiquitous Virtual Resources - integrated and flexible usage of heterogeneous and assumable virtual resources for energy, networking, computation, storage, content, mobility, etc.

Dynamic deployment of (new)management functionality without interruption of FI systems’ and services’ operation (i.e. Pug-and-Play, UnPlug-and-Play, programmability)

Orchestration and integration of management functionality

Define Self-contextualisation for FI systems, services and resources

Define FI Autonomicity and Self-awareness

Minimise life-cycle FI system costs, minimise energy footprint

Orchestration and integration of management functionality

Relationships between Self Management & Self Governance


Approach:

• Leverage and influence effort in existing FP7 projects

• Improve synergies and added value with other research initiatives


Expected Results ( by December 2008):

• Identify key directions for future research projects

• Common position(s) on the necessary and prioritised research challenges and reference configurations

• Reference management architectures and infrastructures; alternate paths

• Define management of virtualised FI systems and services

[edit] Documents

[edit] Events

[edit] FIA Madrid actions

[edit] Proposal form

Subject Management and Service Networking Infrastructures and Architectures within the Future Internet
Scope (Max 5 lines text)

• Management of Ubiquitous Virtual Resources - including the integrated and flexible usage of heterogeneous and assumable virtual resources for energy, networking, computation, storage, content, mobility, etc.

• Cross-domain Self Management functions and cross-layer cooperative Future Internet systems design providing integrated management functionality, including: system lifecycles, monitoring, (re)configuration, optimisation, organisation, performance, adaptation, context, semantics, security, composition, assurance, negotiation, repository, SLA, QoS, billing, functions-management; minimising life-cycle Future Internet system costs, minimising the energy footprint

• Embedding management functionality in all Future Internet systems (i.e. InNetworks management, InServices management, InContent management)

• Dynamic deployment of (new)management functionality with no interruption of Future Internet systems’ and services’ operation (i.e. Plug-and-Play, UnPlug-and-Play, programmability)

• Orchestration and integration of management functionalities


Initiator domain Networks + Services WG
Priority from the originator domain1
Duration of the parallel session 4 hours
Other domains required to participate and howNetworks, Services, Content
Possible endorsement/support from other domainsNetworks, Services
Personal tools