Dear Ricardo,
To continue the thread, there remain some doubts regarding the HLD content related to the IoT Resource Management section from our side as well.
Before going on, let me say that I fully agree with your earlier comments that any un-clarities should have been addressed during the document review phase, and also that your efforts in clarifying the subject matter as in the thread below, are much appreciated.
However, as we progress through the project and requirements are being derived from the HLD to see how our assets could best fit these, further questions arise.
We did a best effort in mapping the assets so far (meanwhile v33 in the Forge), and many things are clear, but it is sometimes difficult to understand the "big picture" based on the HLD (there's some inconsistencies and mixing of terminology, IMHO), and we still have some questions that need to be resolved before we can reliably refine our asset evaluation.
To ease things, below I´ve included my understanding of how the components and GE's fit together (based on Excel comments and the discussion thread), but as mentioned, there are some gaps and questions (in-line).
It would be great if you could provide additional comments in-line over the descriptions and questions.
Many thanks in advance,
Best regards,
Maarten
Discovery & Resolution of Things GE
Retrieves lists of services that expose resources related to particular things.
QUESTION: According to the diagram, it's the other way around: resources expose services. Is the diagram incorrect?
Accepts: Requests from users based on a general description of a service.
Provides: Lists of services
Uses: Thing Resolution component, Things & IoT Service Monitoring component, and Things Manager component.
Used by: northbound clients / users
Thing Resolution component
Discovers things, either through a general or an exact description.
Accepts: A general or exact description of what is needed
Provides: A handle to the thing
Uses: IoT Resources & Services Discovery component of Services & Resources GE, in case there is no clear description, by means of the IoT Catalog and IoT Resource Directory
QUESTION: What component handles the resolution if there is a clear description?
Used By: Discovery & Resolution of Things GE
QUESTION: What is understood by the word "infrastructure" in the context of Infrastructure Resolution?
QUESTION: What is the input for the resolution, in case we provide a clear description of the Thing? I suppose the name+type of the Thing?
Thing & IoT Service Monitoring component
Manages dynamic associations between entities, their resources and the management services exposed by the resources
QUESTION: Also App Services (see diagram)??
QUESTION: does it also support update/insert/etc. operations???
Accepts: Resource description?
Provides: Handle to thing?
Uses: Services & Resources GE to retrieve the thing to which resources are associated, i.e. the thing that is managed by the device that hosts the resource.
Used by: Thing Resolution???
Things Manager component
Manages static associations between entities and their resources
QUESTION: what about their services (app / management)?
Accepts: Handles to things and resources to update/insert/etc.
Queries for resources / things
Provides: Information about resources / things
Uses: -
Used by: Services & Resources GE
QUESTION: Are the Thing & IoT Service Monitoring and Things Manager components the same, except that one does dynamic and the other static management? Or are they fundamentally different?
QUESTION: The GE deals with "retrieving lists of services" (HLD), but it is unclear which subcomponent actually returns this list. Does it also return other things than services?
Services & Resources GE
HLD does not provide a description, other than that it is consists of the components described below.
Offered in both async and sync versions.
IoT Resource Directory
Device registry, status, location, capabilities, etc. etc.
Accepts: Registering devices
Provides: Device info
Uses: -
Used by: the different components
Directory Handler
Southbound interface of IoT Resource directory with IoT Communications.
IoT Resource & Service Discovery
Dynamic Catalog + Directory lookup based on context information.
Accepts: Requests from IoT Data Handling
Requests from Thing Resolution (Discover & Resolution of Things GE)
Provides: * "... provide access to services associated to things, allowing web services to find these resources"
QUESTION: Surely, instead of "services associated to things" it is meant to be "services associated to resources"? (otherwise, it is unclear where "... these resources" refer to).
* Things and their static/dynamic associations with other things and resources
* Information to the Data/Context Management GE (i.e. Data/Context Management Chapter)
Uses: -
Used by: Thing Resolution component of Discovery & Resolution of Things GE
IoT Catalog & Location
QUESTION: The HLD talks about "Resource Description components", I cannot find a description of this anywhere else in this section or the other chapters - would it be possibly to clarify these components?
My guess is that these are the inputs (generically or clearly defined) submitted by the client in order to find things / services, i.e. Context Information. Is this assumption correct?
Determine which of the different instances of the entities can support a user request (according to HLD)
QUESTION: An Entity == Hardware Device? If so, can a device conceptually have multiple instances within FIWARE-IoT?
A helper that is only used when IoT Resource & Service Discovery component does a two-stage lookup (Directory + this component) when the user supplies a generic description of a thing via the Thing Resolution component in the Discovery & Resolution GE.
Accepts: Generic lookups
Provides: Handles to things?
Uses: -
Used by: IoT Resource & Service Discovery
From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras
Sent: jueves, 13 de octubre de 2011 16:18
To: Bisztray, Denes (NSN - HU/Budapest)
Cc: 'fiware-iot at lists.fi-ware.eu'
Subject: Re: [Fiware-iot] clarification on resource management GEs
Dear Dénes,
please let me include the rest of the people in cc: because I think this email could be interesting for everybody (@ll: read below please), otherwise your descriptions in the Excel file would not be in line with the functionalities expected/defined in the Architecture.
Dénes, only one additional comment regarding the 'Thing Resolution' block:
The information from the things (or the actuation capabilities to modify the things environment) is provided by sensor/actuators that are included over the homogenous term of resource.
Consequently, the Thing Resolution function task is to discover which resources are the ones providing the information/actuation capability over a Thing. For example, let's assume that a box has attached a temperature sensor, consequently the Things resolution will be the entity providing the mapping of (Temperature (box) --> Sensor X). However, not all the mappings are static: for example if the box does not have a temperature sensor, but it is placed in a room that has a temperature sensor, the temperature of the box could be provided by the sensor located in the room.
So 'IoT Resources & Services Discovery' can be considered a subset of the 'Thing Resolution' component, providing support to the Infrastructure Resolution process.
br,
Ricardo.
Ricardo de las Heras wrote:
Dear Dénes,
sorry but I answer to you briefly because I have a meeting now, we can continue later, but I don't understand why none of you paid attention to T5.2 architecture before the election of the assets, these type of question are also coming now from the rest of the parters ...:(
I clarify it in-line:
Bisztray, Denes (NSN - HU/Budapest) wrote:
Dear Ricardo,
Thanks for the excel sheet. I found those notes, but it helped to clear the picture what exactly I don't understand. There are several GEs mentioned in the Excel that are not to be found in the latest versions (i.e. Data/Context Management GE). Currently I summed up my understanding of the two GEs as follows. I just wrote down in simple terms, please help to clarify why the Discovery and Resolution of Things is different.
Services and Resources GE
o IoT Resource & Service Discovery: OK , THIS IS THE DISCOVERY COMPONENT
· dynamic discovery based on context information.
· Provides context information towards Data/Context Management GE (there is no such GE, what is the updated name?)
o IoT Resource Directory: DIRECTORY OR RESOURCES STORING THEIR STATUS AND CAPABILITIES
· This is the data store with all the device related context and other data.
o Directory Handler: YES, THIS IS THE INTERFACE TO THE DIRECTORY
· Southbound exposure interface.
o IoT Catalog and Location: THIS IS A COMPONENT THAT WOULD BE USED ONLY IF THE DISCOVERY IS IMPLEMENTED IN TWO STEPS: CATALOG AND DIRECTORY STRUCTURES, OTHERWISE IT HAS NOT ANY FUNCTION.
· Discovery again, but with different type of search criteria (should be integrated into the IoT Resource & Service Discovery)
Discovery and Resolution of Things GE
Thing Resolution Component DISCOVERY AND INFRASTRUCTURE RESOLUTION IS NOT THE SAME, ONLY ONE EXAMPLE NOW:
* DISCOVERY: I NEED THE TEMPERATURE OF THIS ROOM, TRY TO FIND A SENSOR CAPABLE OF PROVIDING ME THAT MEASURE.
* IFR. RESOLUTION: GIVE ME DENES' AMBIANCE TEMPERATURE =>> THIS IS THE TEMPERATURE OF THE ROOM WHERE IS DENES, SO YOU NEED SEMANTIC CAPABILITIES.
· Yet another resolution component. Not clear exactly in what way is it different then the IoT Resource & Service Discovery
o Thing and IoT Service Monitoring: MONITORS THE DYNAMIC ASSOCIATIONS ENTITIES-RESOURCES (CAR MOVING ON THE STREET, ASSOCIATING ITS POSITION TO THE STREET WHERE IT IS LOCATED EVERY TIME.
· Same as the IoT resource directory. It maintains the service links and status.
o Things Manager: MANAGES ENTITIES, RESOURCES, THEIR STATIC ASSOCIATIONS
· Same as IoT Resource Directory and Thing and IoT Service Monitoring. Stores context data and updates it.
Best,
Dénes
I HOPE IT HELPS YOU TO CLARIFY IT IN SOME WAY NOW, OTHERWISE WE CAN CONTINUE LATER,
If you have any feedback with this model please let me know,
CHEERS;)
RICARDO.
From: ext Ricardo de las Heras [mailto:rheras at tid.es]
Sent: Thursday, October 13, 2011 1:05 PM
To: Bisztray, Denes (NSN - HU/Budapest)
Subject: Re: clarification on resource management GEs
Dear Denes,
OK, yes, in some cases it seems they provide similar functionalities,
I think it was one of the main problems when the parters tried to describe how their assets provide those functionalities,
I don't know if you have read the comments on the cells (2nd column) included in the Excel file, because there I've tried to clarify more in deep those functional blocks.
For me the main concern was about the Resource Directory and the Directory Handler, becuase in the step of definition we already had some doubts about the differences between them.
The fact was we defined Directory Handler for providing the API for managing the Resource Directory repository, so really the functionality is included in the Resource Directory.
Please review the comments on the Excel file and contact me again if you have doubts after reading it, I'd try to clarify the blocks,
best,
Ricardo.
Bisztray, Denes (NSN - HU/Budapest) wrote:
Hi Ricardo,
I'm reviewing the IoT architecture and was wondering about functonality of the various GEs in the resources management chapter. There are several components in the GEs that seem to have similar functionality.
Can you detail the exact difference between the Services and Resources GE and the Discovery and Resolution of Things GE? Both seems to do the same repository/name resolution/routing/update management. Furthermore the components within the Services and Resources GE seems to be redundant as well.
Best,
Dénes Bisztray, PhD
Senior Research Engineer
Nokia Siemens Networks
--
-------------------------------------
Ricardo de las Heras
M2M Research Project Manager
E-mail: <mailto:rheras at tid.es> rheras at tid.es
Phone1: (+34) 983 367625
Phone2 OCS: (+34) 91 31 29511
Telefónica I+D <http://www.tid.es>
-------------------------------------
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
--
-------------------------------------
Ricardo de las Heras
M2M Research Project Manager
E-mail: <mailto:rheras at tid.es> rheras at tid.es
Phone1: (+34) 983 367625
Phone2 OCS: (+34) 91 31 29511
Telefónica I+D <http://www.tid.es>
-------------------------------------
--
-------------------------------------
Ricardo de las Heras
M2M Research Project Manager
E-mail: <mailto:rheras at tid.es> rheras at tid.es
Phone1: (+34) 983 367625
Phone2 OCS: (+34) 91 31 29511
Telefónica I+D <http://www.tid.es>
-------------------------------------
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111021/c58a1566/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy