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

0",#%#1#&'2)+%&")-'3/'4/-/+&51"%+)67/,'8'02!49:;<='>&?&'3/'@)5)*A&B'C)"#)'D%#)'3&'C)E1+)FB'(%"),'G/*)%,B'H*)I%-

!,%)J0'K=<<'C155/*'C+L&&-'M'J1#1*/'0"#/*"/#'!*+L%#/+#1*/'N&*O,L&EB'P)/Q/&"B'C&1#L'R&*/)

!"#$%"$&%$&'"(%$(#)*#$+%$,(

+,#')+-,(.+'/&0,+

1,2&/,+(3&"%2(#'2)$&'"#($'($4,(/&+$)%2(

'.,+%$'+#

5##,##(,6.,+&7,"$#(%"0(/%2&0%$,(+,#)2$#8

1,3&",('*9,-$&/,#:(;'%2#:(+,#$+&-$&'"#8

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

,#,%+-4(=(

0,/,2'.7,"$(0&+,-$2>('"(

,6.,+&7,"$%2(3%-&2&$&,#

!"#$%&'()*+,$-'.-./*0$12*$3")$.4$566*,*'"1+78$!*1&'7/9$)2*'*$1).$-./+1+:*$4**0;"6<$,..-/$.66&'$0&'+78$/.=*$1*627.,.8#$*:.,&1+.7$-'.6*//>$

?'+1+6/$-'.-./*$12*$3.8+/+1+6$4&761+.7$"/$=.'*$"0*@&"1*0>

A"7#$;*,+*:*$12"1$+1$+/$1+=*$1.$'*0*/+87$12*$B71*'7*1$1.)"'0/$"$C&1&'*$B71*'7*1$DCBE>

F.)*:*'9$12+/$1+=*$12*$1*627.,.8#$,"70/6"-*$+/$@&+1*$0+44*'*71$4'.=$12*$GHI/$J+1$+/$=&62$=.'*$0#7"=+69$6.=-,*K$"70$0+:*'/*>

571.7+.$5,;*'1+$L$MHNN

O*627.,.8#$*:.,&1+.7$)+,,$0**-,#$"44*61$0*/+87/$12+/$1+=*>

P*/+87/$7**0$1.$"66.==.0"1*$1*627.,.8#$*:.,&1+.7$+7$"$4,*K+;,*9$2.=.8*7*.&/9$2.,+/1+69$"70$6.7:*'8*71$)"#>

?2",,*78*/$12"1$6"7$7.1$;*$"00'*//*0$1.0"#9$6.&,0$;*$+7$"$4*)#*"'/>

B=-"61/$.4$*:.,&1+.7$"'*$"1$,*"/1$0&",J4"6*1*0Q$12*#$6'*"1*$7.1$.7,#$=.'*$6"-"6+1#9$&;+@&+1#9$"70$6.77*61+:+1#9$;&1$",/.$=.'*$/6",";+,+1#$"70$6.=-,*K+1#>

A"<+78$DMP'+S+-/,'&"-%"/Q

N>$P+'*61$!RP$.:*'$"7$.-*'"1+.7",$/&;/1'"1*$'*/.&'6*$-'.:+0*'>

M>$B70+'*61$!RP$.:*'$"$0*:*,.-+78$4"6+,+1#$6.=-"1+;,*$)+12$"7$.-*'"1+.7",$/&;/1'"1*$'*/.&'6*$-'.:+0*'>

S>$B70+'*61$!RP$.:*'$"$12+'0$-"'1#$*K-*'+=*71",$4"6+,+1#$6.=-"1+;,*$)+12$"7.-*'"1+.7",$/&;/1'"1*$'*/.&'6*$-'.:+0*'>

T1"<*2.,0*'/Q$U+'1&",$V-*'"1.'$DUVE9$T&;/1'"1*$!*/.&'6*$W'.:+0*'$DT!WE9$T.,&1+.7$W'.:+0*'$DTWE9$"70$XK-*'+=*71",$C"6+,+1#$DXCE>$

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

Architecture for the Future Internet

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.

It relies on published bindings among self-certified names (SCNs) to capture entities and information relationships.

SCNs that are unique in some scope can be used as identifiers.

Interested entities recursively subscribe public SCN-bindings in order to discover the published information.

Two services (1 and 2) are using IoIS components inside a domain. (1) Service 2 builds four bindings. One relates its ID to a descriptor. The others relate its ID to the names “Message”, “Server”, and “Message Server”. Then, Service 2 sends all those bindings to be published; (2) The PSS forwards the bindings to the domain GIRS; (3) The GIRS selects the appropriate HTS to store them; (4) Service 1 asks the SDS about a partner to compose an application that requires message forwarding. Let’s assume it queries “Message Service”; (5) The SDS subscribes the names “Message”, “Service”, and “Message Service” via PSS; (6) The PSS forwards to GIRS; (7) The GIRS discovers the adequate HTS where they could be stored. (8) The SDS receives only the existent bind- ing between Service 2 ID and the name “Message”. It subscribes this ID and discovers Service 2 descriptor. It subscribes the descriptor and verifies if it fits on the “Message Service” context; (9) It answers the Service 1 with the Service 2 <ID, descriptor> binding. After that, the Service 1 publishes an SLA offer (not shown in figure) and the PSS notifies the Service 2 about this new publication. The Service 2 subscribes the SLA and the PSS notifies the Service 1 about this subscription. If the SLA is accepted, the Service 2 publishes it again with its own ID and asks PSS to notify the Service 1. This indicates that they both agreed.

Highlighting the Proposal by an Example

• HTS (Hash Table System): A set of processes that stores name-based bindings among entities.

• GIRS (Generic Indirection Resolution System): A process used to decide the most appropriate Hash Table to store some name-based binding.

• PSS (Publish/Subscribe System): It does the rendezvous between publisher and subscriber.

• OBS (Orchestration Broker System): It helps simple services to search, discover, negotiate, and contract service partners.

• RS (Reputation System): It is responsible to determine entities reputation based on the feedbacks received from partners in established SLAs.

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

Architectural Components

This paper presented some Future Internet design choices aimed to gracefully merge a set of selected ingredients, including information- and service-centric ones. Entities can discover each other as well as their published content by performing recursive subscriptions of published SCN-based bindings.

Conclusion

[Ongoing Research]

Antonio Marcos Alberti, Agostinho Vaz, Rodrigo Brandão, Bruno Martins

Instituto Nacional de Telecomunicações - Inatel. 510 João de Camargo. Santa Rita do Sapucaí, Minas Gerais, Brazil