Hi Chris and all, Thanks for sharing this document. I understand that you proposed a process to assess the Epics and user stories, vs. the assets and resources. My feeling is that a very concrete step, thanks Chris. What I don't understand is on which description you want to base this process because I don't think the current assets and epics give a lot of information about I2ND. If we can't describe what I2ND does in a very concrete and easy to understand way, all efforts to write user stories are moot IMO. Let me try first to look at the DoW and second to look at the Epics, and finally provide some suggestions about what is I2ND and what is missing. · In the DoW introduction it's written that: "Interface to the Network and Devices - the open interfaces to networks and devices, harmonizing the connectivity needs of services built on top of the platform." So in my personal picture of I2ND it consists of specifications for network and devices interfaces. · Later in the DoW (B.1.1.4.5) it's mentioned that: A fundamental challenge for the implementation of the required interfaces is that the network functionality is typically distributed over different elements potentially implemented internally in different ways (in multi-vendor environments), and that the interfaces have to take into account the constraints of different providers (in multi-network service scenarios) as well as legal and regulatory requirements. Which makes sense for me if I2ND is about interfaces. · This is further enforced with the following text (1) Interfaces to end devices (addressed by connected device), (2) interfaces to gateways (cloud proxy), (3) interfaces to connectivity functions inside the network (open networking), and (4) interfaces to services offered by the network operators (network services). When I look at the Epics I can see: · FIWARE.Epic.I2ND.S3C.ExposedNetworkInformation defines the exposure API for information from the access and core network towards applications such as location, device status, user activity, network events. (mostly an event API). · EPIC.FIWARE.I2ND.S3C.CoreNetworkControl customizes the IP connectivity according to the requirements of the applications (mostly security features) · EPIC.FIWARE.I2ND.S3C.CoreNetworkDeviceManagement enables the core network to remotely manage connection of devices to the network (A network to device API) · EPIC.FIWARE.I2ND.S3C.NetworkLevelDataDelivery optimizes the data delivery through network for specific services e.g. unicast, time tolerant communication, groups, multicast and/or broadcast, small messages (a content transport API) · FIWARE.Epic.I2ND.S3C.SMS+MMS ENABLERS is basically a subset of GSMA's OneAPI · FIWARE.Epic.I2ND.S3C.Telecom platform_1 manages Telecom calls, conference, voice interaction through a very high level API · FIWARE.Epic.I2ND.S3C.API mediation_1 deals with publishing, discovering and exposing APIs to stakeholders as well as managing some non functional aspects such as provisioning and monitoring. · FIWARE.Epic.I2ND.S3C.WSC_1 provides seamless integration of Telco services in devices Now let's draw some conclusions and a rough picture of I2ND : · Conclusion: o I can't see an EPIC that makes it possible for a Fi-Ware service to deal with devices. But there are two candidates; § EPIC.FIWARE.I2ND.S3C.CoreNetworkDeviceManagement but it is described as a network to device API, so probably we miss a service to network on top of this EPIC. § WSC_1 probably could be this missing API on top of CoreNetworkDeviceManagement. o Where are interfaces to gateways in EPICS? Orange proposed to work on that depending on requirements from Technicolor, but there is no requirements at the moment. o About Open Networking APIs probably there is no EPIC about it at the moment as "The open networking functional component deals with interfaces that provide open access to the forwarding functions of network nodes and thus enable a certain level of programmability within the network, e.g., concerning flow processing, routing, addressing, and resource management." o When it come to network services APIs I think there are several APIs that cover that: § At a low level (ExposedNetworkInformation, CoreNetworkControl, NetworkLevelDataDelivery) § At a higher level: SMS+MMS ENABLERS, Telecom platform_1, API mediation_1, WSC_1 · Rough picture Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Woods, Chris Envoyé : mercredi 26 octobre 2011 19:10 À : Garino Pierangelo (pierangelo.garino at telecomitalia.it) Cc : fiware-i2nd (fiware-i2nd at lists.fi-ware.eu) Objet : [Fiware-i2nd] FW: Executing on Task 7.1 Hi All, As discussed on our call I've uploaded the generic version of the execution document I have been discussing with Pier. You can find this generic document here: https://forge.fi-ware.eu/docman/view.php/10/543/Generic+Execution+I2ND.docx For completeness, and openness - I've included the link to my original document, and Pier's comments below. This is a work in progress. I'd really appreciate any improvements you may suggest. Thanks, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Wednesday, October 26, 2011 8:55 AM To: Woods, Chris Subject: R: Executing on Task 7.1 Hi Chris, at last I could have a look to your very good document, reflecting in some aspects what we defined and tried to do in the past months (but we never described in a document...), I have added some comment in it from my side, and updated the doc on the Forge site at https://forge.fi-ware.eu/docman/view.php/10/530/Executing+on+the+Connected+Device+Interface-pg.docx Generally speaking, I do entirely agree with your proposal, the main concern I have is however that some of the proposed steps should have been already performed in the past months of project activity (and some were actually more or less done, please check the document https://forge.fi-ware.eu/docman/view.php/10/538/CDI_status_2.doc ), so we need to understand whether we can 'skip' (or assume as done) some of them to stay aligned with the overall project timeline (we'll discuss today in the call), or rather we decide to take our time to face all the steps in a more consistent way, causing however some delay to the whole project. My suggestion at the moment would be that we attempt to 'survive' with current not perfectly linear situation, where e.g. some assets are already available even though a real assessment was not done, and for the first release (expected by April) we identify a minimum set of functionality to be implemented which doesn't require too many detailed analysis (and maybe matching some functionality already available...); then we'll restart with next iteration (e.g. including those requirements/epics coming from the other FI-PPP Use Case Projects) with a more complete and organized process as you propose. I propose we share this document with all the CDI partners, and define together how to proceed. We can tell about this in the call in few minutes time... BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] <mailto:[mailto:chris.woods at intel.com]> Inviato: lunedì 24 ottobre 2011 18:15 A: Garino Pierangelo Oggetto: Executing on Task 7.1 Hi Pier, As discussed on the phone last week I've converted our previous email discussion (attached) into a discussion document. It is available on the forge at the following location: https://forge.fi-ware.eu/docman/view.php/10/530/Executing+on+the+Connected+Device+Interface.docx Thanks, Chris ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. 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. Rispetta l'ambiente. Non stampare questa mail se non è necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111027/ac3a0311/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111027/ac3a0311/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 12241 bytes Desc: image002.png URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111027/ac3a0311/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy