[Fiware-iot] task 7.1

[Mario.LOPEZRAMOS at fr.thalesgroup.com]

Hi everyone,

I tend to agree with what Gian Piero stated about I2ND chapter. I only have general remarks, so I will add them here :

In general, the terminology used in this chapter is very telco-oriented, and "device" means rather "connected hardware terminal with a user interface" for them (i.e. smartphones, tablets, PCs, TVs...). The contents does not describe how IoT resources such as unattended sensors and actuators should interface to the network.
The only mention to IoT is in the description of the "Device services" which may include "Short Range Radio" technologies to ease the interaction with IoT.

The following bullet points are my understanding of how IoT could fit in.

Option A : IoT resource = I2ND device

 *   We can assume that IoT devices are "devices" in the I2ND sense with less capabilities (i.e. no display, no personal data services, no media services).
 *   Following the NGN strata model (Figure 64 in page 167), IoT devices would be in one or more "technology-related control space" (IEEE 802.15.4, Wavenis...) under the control of an operator.
 *   The IoT gateways would have to implement the "Connected Device Interfacing" on behalf of the resource-constrained IoT nodes.
 *   Depending on the business model, the 2 types of technology-independent mandatory interfaces to devices they could also make sense for IoT :
    *   CDIL-NET : Interface to network services owned by network operators
    *   CDIL-APP - Interface to applications created by application developers : if we assume that applications can be deployed to IoT devices (e.g. a request to publish temperature for next 24h can be considered running an application)

Option B : IoT gateway = I2ND device, IoT resource = subsystem of a I2ND device

 *   If we assume that an application is delivered by a network of IoT nodes as a whole, we can
 *   However, we would not benefit of the standard interfaces which would make sense for individual IoT nodes, such as checking network status, battery, remote management, etc.


Unfortunately, I won't be able to attend tomorrow's telco. Thursday is bank holiday in France, and many of us are taking a few days off.

Best regards,

--
Mario LOPEZ-RAMOS
Thales Communications & Security

e-mail: mario.lopezramos at fr.thalesgroup.com<mailto:mario.lopezramos at fr.thalesgroup.com>
Tel: +33 (0)1 46 13 32 10
Fax: +33 (0)1 46 13 26 86
Add: 160 bd de Valmy - BP 82 - 92704 Colombes Cedex - France


> -----Message d'origine-----
> De : fiware-iot-bounces at lists.fi-ware.eu
> [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de
> Fici Gian Piero
> Envoyé : mardi 12 juillet 2011 11:42
> À : Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu
> Cc : Nemeth, Lorant (NSN - HU/Budapest)
> Objet : [Fiware-iot] R: task 7.1
>
> Hi Lorant and everybody,
>
> I had a  look at the description of the task 7 (Interface to
> Networks and Devices - I2ND) and in particular at the work
> package 1 (Connected Devices Interfacing - CDI).
> You can find the file attached, since I do not know if all of
> you can access their document (I had it from Pier Garino that
> is the task leader).
>
> In the task 7 they defined 4 GEs:
> (1) Connected Device Interfacing (CDI), i.e. Interfaces to
> end devices (addressed by connected device),
> (2) Cloud Edge (CE), i.e. interfaces to gateways (cloud proxy),
> (3) Network Information & Control (NetIC), i.e. interfaces to
> connectivity functions inside the network (open networking),
> (4) Service, Capability, Connectivity and Control (S3C), i.e.
> interfaces to services offered by the network operators
> (network services).
>
> All of these GEs have relations with our platform (in
> particular CDI and CE) and the I2ND descriptions are very
> complete and ambitious, but there is no explicit link to our
> platform. It looks like the applications/services use
> directly those interfaces, or better they do not mind if
> there is something in between.
>
> Maybe I was not able to understand correctly their
> descriptions, but I see that we put in our figures a
> relationship with the other tasks (not only Interface to the
> Networks, but also Data & Context Management Services;
> Security, Privacy, Trust; Applications & Services Ecosystem
> and Delivery Framework) but I2ND did not put any
> relationships with us.
>
> I think it is worth to try to understand together with them
> how they see the overall picture of the FI-WARE architecture.
> I already contacted directly my colleague Pier Garino for a
> brief exchange of ideas but unfortunately (well, not really
> :-) I will be away for the rest of the week on vacation and I
> will be back on July 19th, so any further information will be
> delayed to next week. (I will not participate to the weekly
> call conference tomorrow, sorry).
>
> I hope these short notes are clear enough. :-)
>
> Bye,
> Gian Piero
>
>
> -----Messaggio originale-----
> Da: fiware-iot-bounces at lists.fi-ware.eu
> [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di
> Farkas, Lorant (NSN - HU/Budapest)
> Inviato: lunedì 4 luglio 2011 13:26
> A: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu
> Cc: Nemeth, Lorant (NSN - HU/Budapest)
> Oggetto: [Fiware-iot] task 7.1
>
> Dear Sabrina and Gian Piero,
>
> Could you please check potential overlaps of IoT
> communications with task 7.1 from the Interface to the
> Networks and express an opinion about it?
>
> Thanks & br,
>
> Lorant
> _______________________________________________
> Fiware-iot mailing list
> Fiware-iot at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware-iot
>
> Questo messaggio e i suoi allegati sono indirizzati
> esclusivamente alle persone indicate. La diffusione, copia o
> qualsiasi altra azione derivante dalla conoscenza di queste
> informazioni sono rigorosamente vietate. Qualora abbiate
> ricevuto questo documento per errore siete cortesemente
> pregati di darne immediata comunicazione al mittente e di
> provvedere alla sua distruzione, Grazie.
>
> This e-mail and any attachments is confidential and may
> contain privileged information intended for the addressee(s)
> only. Dissemination, copying, printing or use by anybody else
> is unauthorised. If you are not the intended recipient,
> please delete this message and any attachments and advise the
> sender by return e-mail, Thanks.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20110712/db95f88d/attachment.html>