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


Published on

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 redesign to accommodate information exchanging, a.k.a. information- centrism. Others argue that the most important thing is to redesign to accommodate service-based applications, i.e. service-centrism. Who is right? This paper defends the idea that the most important thing is to redesign to integrate both aspects cohesively — we call this approach Internet of Information and Services (IoIS). Poster at Conference at Future Internet 2012, Seoul, Korea.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

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

  1. 1. !,%)J0K=<<C155/*C+L&&-MJ1#1*/0"#/*"/#!*+L%#/+#1*/N&*O,L&EBP)/Q/&"BC&1#LR&*/) Internet of Information and Services (IoIS): A Conceptual Integrative Architecture for the Future Internet [Ongoing Research] Antonio Marcos Alberti, Agostinho Vaz, Rodrigo Brandão, Bruno !"#$"%&()*+&,!-./*#% Martins Instituto Nacional de Telecomunicações - Inatel. 510 João de 0",#%#1#&2)+%&")-3/4/-/+&51"%+)67/,802!49: Camargo. Santa Rita do Sapucaí, Minas Gerais, Brazil ;<=>&?&3/@)5)*A&BC)"#)D%#)3&C)E1+)FB(%"),G/*)%,BH*)I%- IoIS is an integrative approach for combining information-centrism, service-centrism, publish/subscribe paradigm, name-based binding, searching and discovery, and distributed hash tables in an unique architecture. It is the core of a broad architecture called NovaGenesis. A"7#$;*,+*:*$12"1$+1$+/$1+=*$1.$*0*/+87$ !"#$%&()*+,$-.-./*0$12*$3")$.4$ self-certified names (SCNs) to capture entities and It relies on published bindings among information relationships. 566*,*"1+78$!*1&7/9$)2**$1).$-./+1+:*$ 12*$B71*7*1$1.)"0/$"$C&1&*$B71*7*1$DCBE> 4**0;"6<$,..-/$.66&$0&+78$/.=*$ SCNs that are unique in some scope can be usedF.)*:*9$12+/$1+=*$12*$1*627.,.8#$ 1*627.,.8#$*:.,&1+.7$-.6*//>$ as identifiers. ,"70/6"-*$+/$@&+1*$0+44**71$4.=$12*$GHI/$J Interested entities recursively subscribe public SCN-bindings in order to discover the ?+1+6/$-.-./*$12*$3.8+/+1+6$4&761+.7$"/$ +1$+/$=&62$=.*$0#7"=+69$6.=-,*K$"70$ published information. =.*$"0*@&"1*0> 0+:*/*> Highlighting the Proposal by an Example Architectural Components Two services (1 and 2) are using IoIS components inside a domain. (1) Service 2 builds • HTS (Hash Table System): A set of processes four bindings. One relates its ID to a descriptor. The others relate its ID to the names that stores name-based bindings among entities.O*627.,.8#$*:.,&1+.7$)+,,$0**-,#$"44*61$0*/+87/$12+/$1+=*> bindings to “Message”, “Server”, and “Message Server”. Then, Service 2 sends all those be published; (2) The PSS forwards the bindings to the domain GIRS; (3) The GIRS • GIRS (Generic Indirection Resolution System): A"<+78$DMP+S+-/,&"-%"/Q selects the appropriate HTS to store them; (4) Service 1 asks the SDS about a partner to A process used to decide the most appropriateP*/+87/$7**0$1.$"66.==.0"1*$1*627.,.8#$*:.,&1+.7$+7$"$ it queries compose an application that requires message forwarding. Let’s assume Hash Table to store some name-based binding.4,*K+;,*9$2.=.8*7*.&/9$2.,+/1+69$"70$6.7:*8*71$)"#> “Service”, and “Message Service”; (5) The SDS subscribes the names “Message”, N>$P+*61$!RP$.:*$"7$.-*"1+.7",$ “Message Service” via PSS; (6) The PSS forwards to GIRS; (7) The GIRS discovers the • PSS (Publish/Subscribe System): It does the /&;/1"1*$*/.&6*$-.:+0*> subscriber. adequate HTS where they could be stored. (8) The SDS receives only the existent bind- rendezvous between publisher and?2",,*78*/$12"1$6"7$7.1$;*$"00*//*0$1.0"#9$6.&,0$;*$+7$"$4*) ing between Service 2 ID and the name “Message”. It subscribes this ID and discovers#*"/> 2 descriptor. It subscribes the descriptor and verifies if it fits on the “Message Service • OBS (Orchestration Broker System): It helps M>$B70+*61$!RP$.:*$"$0*:*,.-+78$4"6+,+1#$ Service” context; (9) It answers the Service 1 with the Service 2 <ID, descriptor> binding. simple services to search, discover, negotiate, After that, the Service 1 publishes an SLA offer (not shown in figure) and the PSS notifies 6.=-"1+;,*$)+12$"7$.-*"1+.7",$/&;/1"1*$ and contract service partners.B=-"61/$.4$*:.,&1+.7$"*$"1$,*"/1$0&",J4"6*1*0Q$12*#$6*"1*$7.1$ the Service 2 about this new publication. The Service 2 subscribes the SLA and the PSS */.&6*$-.:+0*>.7,#$=.*$6"-"6+1#9$&;+@&+1#9$"70$6.77*61+:+1#9$;&1$",/.$=.*$ 2 notifies the Service 1 about this subscription. If the SLA is accepted, the Service • RS (Reputation System): It is responsible to/6",";+,+1#$"70$6.=-,*K+1#> asks PSS to notify the Service 1. This indicates that publishes it again with its own ID and they both agreed. determine entities reputation based on the S>$B70+*61$!RP$.:*$"$12+0$-"1#$ feedbacks received from partners in established *K-*+=*71",$4"6+,+1#$6.=-"1+;,*$)+12$"7 SLAs. .-*"1+.7",$/&;/1"1*$*/.&6*$-.:+0*> • DS (Domain System): It aims to actively represent all the systems in a domain. • SDS (Search and Discovery System): It performs recursive subscriptions to the PSS and filters results according to semantics and context. Conclusion This paper presented some Future Internet design choices aimed to gracefully merge a set !"#$%"$&%$&"(%$(#)*#$+%$,( of selected ingredients, including information- 1, +,#)+-,(.+/&0,+ 3&" ,( !"#$%"$&%$&"(%$(#)*#$+%$,(+,#)+-,(.+/&0,+ * and service-centric ones. Entities can discover 5##,##(,6.,+&7,"$#(%"0(/%2&0%$,(+,#)2$#8 9, -$ & /, 1, each other as well as their published2&/,content;%by +(3 #: ( 2 #: &"% performing recursive subscriptions of published#$+&- 2(# (+, . 2)$& $& SCN-based bindings. ,+ " % $ #( $ + "# 8 # ($4 ,( /&+ $) %2(