Hyperlinked Entities: decentralised micro-services that are inherently inter-operable (Paulo Chainho, Altice Labs). Presented at TADSummit 2016, 15-16 nov, Lisbon in Stream 3 Project reTHINK: Decentralised Communications

1. 1
TAD Summit
Hyperlinked Entities: Decentralized Microservices
Paulo Chainho, November 15th 2016
TAD Summit

2. 2
Hyperty
Microservice (Independently deployable Business Capability) similar to user
agents or bots, perform tasks on user's behalf
An instance is associated to a “User” through an identity
The Identity is decoupled from the Service Provider
2
Hyperty – User
Association
Hyperty – User
Association

3. 3
No need to standardise Service Network Protocols or Service APIs
{
"id": "HelloObject",
"type": "object",
"required": ["hello"],
"additionalProperties": false,
"properties": {
"scheme": {
"constant": "hello"
},
"hello": {
"type": "string"
}
}
}
Service Interoperability with agreements on the data formats, only.
Inherently Inter-operable

4. 4
Hyperty Descriptor
Describes Hyperty Business Capabilities in terms of:
- Supported Data Schemas
- Supported (Hyperty)Resources

5. 5
Write
O
JSON Data
Object
Communication via Data Synchronisation
Streams
Read Changes
Read Changes
Reporter
Observer
Observer
Observer
A
hello://example.com/201601290617
hyperty://example.com/sdfg-fdjhgj
B
C
D
hyperty://example.io/hfgdjhfg-jkhkjjdf
hyperty://foo.net/hfgdjhfg-jkhkjjdf
hyperty://example.org/hfgdjhfg-jkhkjjdf

6. 6
Connector Hyperty
Hyperties supporting Connection schema are able to handle WebRTC Peer Connections
independently of the signalling protocol used. The Connection schema is defined from the
W3C WebRTC data model.
The URL Scheme for Connection Data Objects is "connection" (example:
"connection://example.com/201601290617")
A
Connection
B
Connection

7. 7
A Context B
Context Hyperty
C
D
Hyperties supporting Context Data Schema are able to produce or consume
Context Data, usually collected from sensors. Compliant with Jenning’s IETF Draft
Sensor Markup Language (SenML).
The URL Scheme for Context Data Objects is "context“. Example:
context://example.com/room/temperature201601290617").

8. 8
DEMO

9. 9
HOW?

10. 10
Decentralized
 A Decentralized Resource Oriented Messaging Framework is used for
communication.
 Publish/subscribe and request/response messaging patterns are
supported.
10

11. 11
Message Delivery Layers
11
Hyperty Runtime Hyperty Runtime
Msg Node
Msg BUS
Sandbox
Msg BUS
Mini
BUS
HH
Sandbox
Mini
BUS
HH
Domain level
Message Delivery
Runtime level
Message Delivery
Sandbox level
Message Delivery
Sandbox
Mini
BUS
HH
Sandbox
Mini
BUS
HH
Native Standard
Hyperty
JSON Messaging
Any Messaging
Protocol
(Protofly)
P2P

12. 12
Protocol on-the-fly – Protofly
 Protocol on-the-fly leverages the code on-demand support by Web runtimes (e.g.
Javascript)
 The most appropriate protocol stack is dynamically selected loaded and instantiate
during run-time
Protostub
Protostub

13. 13
Data Synch Stream Routing Path
Data Synchronisation
Routing Path
Add Listeners to setup
Data Sync Routing Path
Data Sync Routing
Path Management
between Msg Node
and Runtimes

14. 14
Trust Model
1-Intercept
Outgoing Message
3-Msg with
Assertion
4-Intercept
Incoming
Message
6-Message
with Assertion
Validated
5-Validate
Assertion
2-Generate
Assertion
• Identity tokens are generated, inserted in intercepted Messages sent by Hyperties, and
validated by recipient Hyperty Runtimes before delivered to the target Identity.
• Identity management procedures are performed according to applicable policies
managed by the end-user.

15. 15
H1
P1
Load
Hyperty
H3
Register Hyperty Instance
H1
Service Provider
Message Node
Registry
Catalog
H1 P1
Edge Server Runtime
H2
Messaging Communication
between Hyperties
User
Device Runtime
IDP
Proxy
Identity Provider
Generate
Assertions
Validate
Assertions
reTHINK Service Delivery Framework
Global registry
trusted circleDiscover

16. 16
INTER-DOMAIN
rethink.tlabscloud.com
Msg Node
Catalog
H2
Hyperty
Instances
Registry
P1
Hyperty Sandbox
H2
Protostub Sandbox
P1
Msg bus
Hyperty Sandbox
H1
Protostub Sandbox
P1
Msg bus
hysmart.rethink.ptinovacao.pt
Msg Node
Catalog
H1
Hyperty
Instances
Registry
BA
Protostub Sandbox
P2
P2
Protostub Sandbox
P2
Media / data
Each side connected to own domain – using own Hyperty implementation

17. 17
Thank You!
https://github.com/reTHINK-project/startup
Paulo Chainho
This work has received funding from the European Union’s Horizon 2020 research and innovation program under grant agreement No 645342,
project reTHINK.