Architectures and infrastructures

From FutureInternetWiki

Jump to: navigation, search

Contents

[edit] Manifesto

Architecture and Infrastructure as means of convergence for the Future Internet

The Internet has changed society and is increasingly shaping social communities and business interactions. The Internet has evolved from the largely static Information Super Highway of the 90’s to a critical infrastructure supporting all aspects of life in the 21st Century. Internet applications increasingly require a combination of capabilities from traditionally separate technology domains to deliver the flexibility and dependability required by users.

The next decade will introduce remarkable progress in a wide range of pervasive technologies culminating in the introduction of the Future Internet. Beyond technological aspects, the Future Internet is likely to have a profound effect on our society, from a societal, organisational or business perspective.

The EIFFEL Think-Tank report (http://www.future-internet.eu), which was released in December 2006, defines the Future Internet to be a global, open platform and identifies a number of drivers for the next generation Internet, such as emphasis on mobility, the anticipated changes in scale of connected devices, increases in bandwidth, increase in digitised media, increasing importance of security and evolution of services to more adaptability, and awareness of user context and preferences.

To achieve the objectives of the Future Internet at least five communities need to converge and cooperate: Networks, Internet of Things, Internet of Services, Content and Media, and Security. The objective is to identify, understand and resolve convergence challenges between these technology domains and to give Europe the lead edge over other competing global initiatives.

Image:FI_main_components.jpg

Figure 1 Future Internet: converging domains

The purpose of this Working Group is to identify architectural and infrastructural concerns that will make the Future Internet a reality. Architecture and Infrastructure are the foundations on which Future Interne applications will be developed.

Typical characteristics of the architecture and infrastructure of the Future Internet in terms of the five communities identified in Figure-1 are:

  • Networks <to be filled by the networking community>
  • Internet of Things <to be filled by the relevant community>
  • Internet of Services:
    • Service architecture and infrastructures aim at standardise the way services are built, offered and consumed. There is a clear need for introducing a Reference Service Architecture for materializing the Future Internet.
    • The Reference Architecture should be defined in order to allow any business domain, business of any size, and technology to engage in a collaborative and dynamic society.
    • Implementing a Reference Architecture is not a single shot effort but an incremental process with should involve many participants both from academia and industry.
  • Content and Media <to be filled by the relevant community>
  • Security <to be filled by the relevant community>

With the full involvement of the FP7 Projects, and particularly of those who are members of the Future Internet Assembly, this Working Group will proceed step by step starting from identifying relevant results of each project, and by then clustering the results in common and shared items which will be the initial components of the Architecture and Infrastructure of Future Internet.

[edit] Documents

[edit] FIA Madrid actions

[edit] Proposal form

SubjectArchitectures and infrastructures
Scope (Max 5 lines text)Identify architectural and infrastructural concerns that will make the Future Internet a reality. The main issues covered would include: network layer vs services layers; mobility; dynamicity; security; awareness of user context; relationship to business value chains and socio-economic aspects.
Initiator domainServices
Priority from the originator domain2
Duration of the parallel session90 minutes
Other domains required to participate and howNetworks
Possible endorsement/support from other domainsEdit me
Personal tools