Worldwide, hundreds of projects to redesign the Internet are in progress under the banner of the so-called Future Internet. Some argue that the most important thing is to the design to accommodate information exchanging, a.k.a. information-centrism. Others argue that the most important thing is to design to accommodate service-based applications. In this talk, we defend the idea that the most important thing is to design to integrate both aspects in a cohesive way. To do so, architectural blueprints should be able to solve indirections generally, to allow mobility and semantic rich search for services and contents, as well as location, hiring and dynamic invocation of services. We propose a single conceptual architecture capable of integrating the service- and information-centric approaches for the Future Internet. We call this approach as Internet of Information and Services (IoIS).
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Outline1. Contextualization2. Internet of Services (Service-Centrism)3. Internet of Information (Information-Centrism)4. Search and Indirection Resolution (SIR)5. Internet of Information and Services (IoIS)
2. Internet of Services (Service-Centrism) Some requirements and challenges are:
Life-cycling → dynamic, distributed, and cross-domain; Seamless → service describing, publishing, discovering and
negotiating will be necessary; How to search, discover and select candidate services? Which atributes are representative? How to make attributes searchable? Negotiation → necessary to establish SLAs (Service Level
Agreements);
The answer to some of these question depends on how information is treated on the architecture.
3. Internet of Information (Information-Centrism) Some requirements and challenges are:
To represent persistently and consistently information by means of Information Objects (IOs).
To access information independently of its location. To name contents (or its representation). To adequately manage content → versioning, encodings, copies
of identical content. To use name resolution schemes to find out locators. To allow disruptive and consented communications, e.g. publish/
subscribe (pub/sub) paradigm. To enable efficient, semantic rich, context-based information
search, manipulation and routing.
The answer to some of these question depends on how information is processed by architecture’ services.
4. Search and Indirection Resolution (SIR) The SIR has two other mechanisms have been specified on the
top of GIRS: Publish/Subscribe and Search
ID-based mappings are published/subscribed by entities using the following methods: Pub(ID_Publisher; Notify=ID_1...ID_n; <Mapping>); Sub(ID_Subscriber; Notify=ID_1...ID_n; <Key>);
The rendezvous is also ID-based.
Published legible names are used to enable semantic rich search and discovery of architectural inhabitants, i.e. substrates, content, and services.