Main Runtime Procedures for M2M Comm: complete and clean - Githubissues

reTHINK-project / core-framework

The main goal of WP3 is to provide the reTHINK core framework comprised by the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties.

Apache License 2.0

1 stars 0 forks source link

Main Runtime Procedures for M2M Comm: complete and clean #79

Closed pchainho closed 8 years ago

pchainho commented 9 years ago

https://github.com/reTHINK-project/core-framework/blob/master/docs/specs/runtime/dynamic-view/m2m-communication/readme.md

Complete with Runtime APIs functions and Messages samples using D2.2 Data Model. See this example

Split diagrams if too big

pchainho commented 9 years ago

what is the status?

aoncorici commented 9 years ago

I will finish it today or tomorrow, sorry, I thought I have 75, not 79.

aoncorici commented 9 years ago

some work done, need to complete with message samples. Need to decide which message. In the example given there is only one message depicted, not sure which one should I target. Maybe a new diagram to show the interaction with applications that are already present and want to have new hiperties loaded should be added. Need feedback.

aoncorici commented 9 years ago

have to update picture on the overview to reflect new names: QoS User Agent, for example. Will do that before Friday.

aoncorici commented 9 years ago

ready to close

pchainho commented 9 years ago

reopening since there are a few issues that makes the current description inconsistent:

the remote network service, as I understand it, is an option to use a remote catalog from the device manufacturer for maintenance purposes, not to support pub-sub which should be supported by the residential gateway
the context discovery and its associated Hyperty Producer is performed in the residential gateway registry
the bootstrap is performed before the context / Hyperty producer discovery, starting by downloading the gw protocol stub
for p2p communication the new device uses the producer protostub not the consumer protostub. Anyway, to make it simpler lets skip for now p2p communication / signalling since there are a few webrtc details to be solved first

Let's try to clarify these issues, first

aoncorici commented 9 years ago

dear Paulo,

I am not sure if you read the overview: https://github.com/reTHINK-project/core-framework/blob/master/docs/specs/runtime/dynamic-view/m2m-communication/m2m-comm-overview.md

where 1) text explains: remote Network Service, named here M2M Messaging Service, dedicated for M2M services like storing resources for sensing and actuating (Global M2M Resource Directory)

2) the context discovery and its associated Hyperty Producer is performed in the residential gateway registry. No. The discovery is made before from the global registry, text says: The Context Producer App holds reference to multiple hiperties that are registered into the (Global) Registry.

I know there were many changes and I think some review needs to be done. Can you please put together a document where we would be able to synchronize. In the doc we can have comments attached to text and we can solve them in 1 go, not constantly having an action on github. Anyway we will have to have a document at some point.