Internet of Information and Services (IoIS): A Conceptual Integrative Architecture for Future Internet

IN TE R N E T OF IN FOR M ATION A N D SERVIC ES
(IOIS ) : A C ON C E P TU A L IN TE GR ATIVE
AR C H ITE C TU R E FOR TH E FU TU R E
INTERNET

Antônio Marcos Alberti
Agostinho Manuel Vaz
Bruno Magalhães Martins
Getúlio Emílio Oliveira Pereira
Renann de Oliveira Barbedo Ponte
Rodrigo Carneiro Brandão

© Antônio M. Alberti 2011

terça-feira, 6 de dezembro de 2011

Outline
1. Contextualization
2. Internet of Services (Service-Centrism)
3. Internet of Information (Information-Centrism)
4. Search and Indirection Resolution (SIR)
5. Internet of Information and Services (IoIS)



 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, i.e. service-centrism.

 Who is right?



 We defend the idea that the most important thing is to design to
integrate both aspects in a cohesive way.

 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).



 Software design → it is changing from component-based to
service oriented design: service-centrism.

 Main argument: above a certain level of abstraction everything
can be viewed as a service → Internet of Services.

 “Internet of Services – Supporting the service economy (70% of
GDP in modern societies)”, Villasante 2009.

 Some initiatives are: NESSI, FISO, SOA4ALL, SCube,
RESERVOIR, SLA@SOI.



 The idea → the applications are flexibly and dynamically
constructed by the composition of distributed software services
or utilities.

App
S8 S9
S7 S6 S5
S4 S3 S2 S1



 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.



 Information as a key ingredient in design.

 Information is in everywhere, i.e. contracts, location, police, IDs,
descriptors, naming, etc.

 Main argument: above a certain level of abstraction “Information
is everything and everything is information” (PSIRP, 2009).

 Some initiatives are NetInf, PSIRP, CCN, XIA, NDN.



 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.




So, both approaches have strong sinergies.

How to integrate them?



 We believe that indirection resolution is a fundamental service
for all other architectural ingredients.

 We specified (using UML) a Generic Indirection Resolution
System (GIRS) based on DHTs (Distributed Hash Tables).

 We designed a GIRS-based Search and Indirection Resolution
(SIR) system to enable integrated ID-based search and
discovery.



 The following assumptions were made to design the GIRS:
 (i) Virtual entities have some binary patterns that can be used to
create unique identifiers.

 (ii) To facilitate usage by people, all entities could have readable
names, in natural language.

 (iii) All entities could have information objects that describes them.

 (iv) The entities are related each other via dynamic ID-based
mappings.

 (v) The ID-based mappings are published/subscribed by entities.



 Each GIRS dynamic mapping contains a pair:
 key = Entity ID,
 value = Entity Itself or another IDs.

 The GIRS stores mappings among any architectural entities that
are uniquelly identified.




<>F>7;GD
*"+,-./" HE>6F12?2>67I !"#$%$&' '()

812@>=1 )$*+%#!'

89:372;71 !"#$%&'(

4567167 ,-!&*.+/

01123
<13=2>?752 A$<(8++BB
JD'5K2>F5DL2;6KM5ND(67O6>5DPQD(G:127>ND#R!!

A;3CDE96=7>56



 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.


 Example Scenario: Contracting a Video Processing Service for
Some Content (1/2)

!"#$%& ()*+)* !"#$%'
;4:%&'()(<=;'>?@(A+,+4( ;4:%&G()(<=;'>?@(*+,%"(
!%#$%/B H/"0%11"/B
2%/C+0%&!()(2=ID%E%

!"#$%#$&'()(*+,%"($"(-%(
./"0%11%,

6%10/+.$"/&'7()(6%10/+.$"/("8( 6%10/+.$"/&G7()(6%10/+.$"/("8(
$9%(:+,+4(0%#$%/ $9%(C+,%"(./"0%11"/

2%/C+0%&G()(*+,%"(
2%/C+0%&'()(A+,+4(!%#$%/D%E%
H/"0%11"/D%E%

6%10/+.$"/&'F()(6%10/+.$"/("8( ,%&-$.-/"%01%&23)*$/4% 6%10/+.$"/&GF()(6%10/+.$"/("8(
$9%(5"1$(' &5"#$/-6"%789%: $9%(5"1$(G
;<&=>?%@ABB

23-1$/4$%&'()(5"1$(' 23-1$/4$%&!()(2%/C%/ 23-1$/4$%&G()(5"1$(G



 Example Scenario: Contracting a Video Processing Service for
Some Content (2/2)

!"#$%& ,A.%B/0,123()*+45)3&6%
8"$4C@D123()*+45)3'
()*+)* !"#$%'
%7123(E&6(E&;
;4:%&'()(<=;'>?@(A+,+4( ;4:%&G()(<=;'>?@(*+,%"(
!%#$%/B H/"0%11"/B
2%/C+0%&!()(2=ID%E%

!"#$%#$&'()(*+,%"($"(-%( ,F.%(/0,123()*+45)3'6
./"0%11%, %7123(E&;

,-.%(/0,123()*+45)3&6
%712389:)3';

6%10/+.$"/&'7()(6%10/+.$"/("8( ,G.%8"$4C@,123()*+45)3'6 6%10/+.$"/&G7()(6%10/+.$"/("8(
,<.%=)>?@712389:)3'6% %7123(E&;.
$9%(:+,+4(0%#$%/ $9%(C+,%"(./"0%11"/
2)#5*4>$"*3'-6%
123()*+45)3';
,U.%8"$4C@,123()*+45)3&6
%7123(E&;. 2%/C+0%&G()(*+,%"(
2%/C+0%&'()(A+,+4(!%#$%/D%E%
H/"0%11"/D%E%

6%10/+.$"/&'F()(6%10/+.$"/("8( H%&I$JI4"%KL%&?0)*$46% 6%10/+.$"/&GF()(6%10/+.$"/("8(
$9%(5"1$(' &M"#$4IN"%O9P%Q $9%(5"1$(G
18&RSE%<T--

23-1$/4$%&'()(5"1$(' 23-1$/4$%&!()(2%/C%/ 23-1$/4$%&G()(5"1$(G



Thank You!

More Information?

antonioalberti.blogspot.com



Internet of Information and Services (IoIS): A Conceptual Integrative Architecture for Future Internet

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (15)

Semelhante a Internet of Information and Services (IoIS): A Conceptual Integrative Architecture for Future Internet

Semelhante a Internet of Information and Services (IoIS): A Conceptual Integrative Architecture for Future Internet (20)

Mais de Antonio Marcos Alberti

Mais de Antonio Marcos Alberti (20)

Último

Último (20)

Internet of Information and Services (IoIS): A Conceptual Integrative Architecture for Future Internet