[Fiware-iot] Fi-WARE overall IoT Architecture updated Wiki-page (needs your review)

[Tobias Jacobs]

Dear Carlos,

Thanks a lot for your excellent work on the overall IoT architecture.

I have a few comments

-          A number of minor typos and spelling inconsistencies I have corrected directly on the wiki page

-          The interface between IoT Broker and PubSub is NGSI10.

-          I am a bit confused about the name of the PubSub Broker. At some places it is called Context Broker GE, and I have been criticized in the peer review for calling it "PubSub". Still I am not sure what the official GE name is, but we should make sure we use the official name...

-          Architecture Overview: It is written
"The deployment of the architecture of the IoT Service Enablement chapter is typically distributed across a large number of Devices, several Gateways and the Backend. The Generic Enablers described in this chapter, shown in the figure below, implement functionalities distributed across IoT resources hosted by devices, IoT Gateways and in the IoT Backend."
How about changing this to something less repetitive:
"The deployment of the IoT Service Enablement chapter is typically distributed across a large number of Devices, several Gateways and the Backend. The set of Generic Enablers described in this chapter, shown in the figure below, is partitioned into IoT Gateway Enablers and IoT Backend Enablers"

-          ETSI M2M: it should be mentioned that European ETSI M2M has now become part of the even broader, world-wide oneM2M standardization efforts.

-          I changed quite a bit in the NGSI section, as I found it not so clear. It is still a very brief section, but hopefully more clearly describes the relation between NGSI entities and FI-WARE devices and things.

-          upper/lower case spelling of "thing/Thing" should be consistent. My feeling is that the majority of us prefers the uppercase variant. Personally I do not have a strong preference.

Best regards
Tobias

From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of CARLOS RALLI UCENDO
Sent: Montag, 15. April 2013 16:38
To: fiware-iot at lists.fi-ware.eu
Subject: [Fiware-iot] Fi-WARE overall IoT Architecture updated Wiki-page (needs your review)

Dear colleagues,

As previously discussed, and after completing the peer-reviews process as all other chapters, I'm now updating the overall IoT architecture Wiki-page.
All changes are what we agreed in our F2F meeting, checked also with the project Chief architect (Juanjo) and they are described below.
My idea is to consolidate them by the end of the week so they can be included in the deliverable to be sent to the EC (I agreed with my colleagues managing the whole deliverable edition how to do it in this timeframe).

I'm doing this at this URL in the public Wiki where we can agree the final version this week and then copy&paste to the actual one:
 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_(IoT)_Services_Enablement_Architecture_NEW

Obviously, the original one accessible to vey else is at:
http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_(IoT)_Services_Enablement_Architecture


***** Summary of changes:
1. Include in the introduction the two domains of GEs we are considering at IoT.
Explain if they are mandatory/optional and how many can be deployed in a specific scenario.
Explain behavior, the fact that some features are duplicated between both domains and thus providing optimization (traffic, time-response) and enabling services-at-the-edge.

2. Explain how apps developers will access to IoT GEs (i.e. Directly through our APIs and/or configuring connectivity to Data/Context PubSubCB)
3. In the "Nota Bene." remove "Iot Gateway" item as long as Backend is not described there too.
4. Update the overall architecture figure.
   The idea is to simplify it providing a similar one compared to other chapters. Also include all updates discussed in our recent F2F meeting in Paris.
   Important note from Carlos: I need to do and update the FMC diagram (I used the figure in my .ppt presented in Madrid April's Architects Week).
    I would appreciate if someone may help on this ...
5. Update the Gateway description in the architecture section.
   State it is an optional element in Fi-WARE IoT model.
   Important: the previous sentence " The IoT gateway will support all the IoT backend features, taking into consideration "   is *NOT* true anymore, as long as we are defining for instance a direct interface from GW Protocol Adapter to GW Data Handling for highly constraint gateway devices. Therefore, now the sentence looks like:
 "The IoT gateway will not always support all the IoT backend features, taking into consideration..."
6. Update the interaction with the Security chapter to take into account the new FI-WARE security access model.
7. Update the Architecture Description (i.e. The GEs we propose, specify and develop) for both the Backend and the Gateway Domain.
  This is a key point as it is the main entry point where UCs will see that we have significantly changed our GEs structure.
  Similarly to the presentation I made in the architects week (where our PO was present) I included some traceability notes that I consider useful during this Fi-PPP Phase II (so no previous UC from Phase I can complain that something disappeared or changed and they got lost).

I will propose this mail as a point in the agenda of our next conf.call.
Thanks for reading it in advance so we can have a useful discussion then.

Best regards,
--

------------------------------------------------------------------------------------------------------------------------

Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>)

Cell: +34696923588

Twitter: @carlosralli

IPv6 Blog: http://the-internet6.blogspot.com.es

Product Development & Innovation (Telefónica Digital)

Telefónica I+D SAU

Madrid, Spain

------------------------------------------------------------------------------------------------------------------------

Follow FI-WARE project (Future Internet Services Core Platform):

Website:  http://www.fi-ware.eu

Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

Twitter: @fiware

LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932

------------------------------------------------------------------------------------------------------------------------

________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130416/bd9f5257/attachment.html>