[Fiware-iot] R: Tracker and Materializing Wiki

Guerra Sabrina sabrina.guerra at telecomitalia.it
Fri Jun 15 18:55:17 CEST 2012


Hi Denes and Lorant,
thanks for your work in which you've reorganized the backlogs. We've analyzed the issues assigned to me and we report our observations:

·         Many issues are related to the Advanced Connectivity GE that, as far as I know, is not covered by any assets, both in the backend and in the gateway. They are
97<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=97&group_id=11&atid=193> FIWARE.Epic.IoT.Backend.AdvancedConnectivity.MobilityManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=97&group_id=11&atid=193>
101<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=101&group_id=11&atid=193> FIWARE.Epic.IoT.Backend.AdvancedConnectivity.TrafficFlowManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=101&group_id=11&atid=193>
104<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=104&group_id=11&atid=193> FIWARE.Epic.IoT.Backend.AdvancedConnectivity.QualityOfServiceControl<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=104&group_id=11&atid=193>
1840<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1840&group_id=11&atid=193> FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.MobilityManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1840&group_id=11&atid=193>
1841<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1841&group_id=11&atid=193> FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.SessionManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1841&group_id=11&atid=193>
1842<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1842&group_id=11&atid=193> FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.TrafficFlowManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1842&group_id=11&atid=193>
1843<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1843&group_id=11&atid=193> FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.QualityOfServiceControl<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1843&group_id=11&atid=193>
1861<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1861&group_id=11&atid=193> FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.M2MDeviceSessionManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1861&group_id=11&atid=193>
1862<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1862&group_id=11&atid=193> FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.NativeDeviceSessionManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1862&group_id=11&atid=193>

·         There are two issues that perhaps have a wrong name because the ConnectivityStatusManagement in my opinion is actually the DiscontinuousConnectivity in the Device Management GE
555<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=555&group_id=11&atid=193> FIWARE.Epic.IoT.Backend.AdvancedConnectivity.ConnectivityStatusManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=555&group_id=11&atid=193>
1844<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1844&group_id=11&atid=193> FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.ConnectivityStatusManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1844&group_id=11&atid=193>

·         About the Security GE I don't know who is the partner which will provide it. So there are two epics that are in the Security GE
102<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=102&group_id=11&atid=193> FIWARE.Epic.IoT.Backend.Security.AccessPolicyControl<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=102&group_id=11&atid=193>
1845<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1845&group_id=11&atid=193> FIWARE.Epic.IoT.Gateway.Security.AccessPolicyControl<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1845&group_id=11&atid=193>

·         A question for Ericsson: does your asset implement AddressTranslation module (that is: The IoT resources must be addressable both at application and at device/gateway level so there must be a mechanism to translate the incoming addresses to an internal unified platform address to identify each resource)?
558<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=558&group_id=11&atid=193> FIWARE.Epic.IoT.Gateway.DeviceManagement.AddressTranslation<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=558&group_id=11&atid=193>

·         Finally there are some themes that perhaps have an incorrect name. ConnectivityManagement should be AdvancedConnectivity and Service Control should be DeviceManagement
584<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=584&group_id=11&atid=193> FIWARE.Theme.IoT.Backend.ConnectivityManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=584&group_id=11&atid=193>
1868<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1868&group_id=11&atid=193> FIWARE.Theme.IoT.Gateway.ConnectivityManagement<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1868&group_id=11&atid=193>
585<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=585&group_id=11&atid=193> FIWARE.Theme.IoT.Backend.ServiceControl<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=585&group_id=11&atid=193>
1867<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1867&group_id=11&atid=193> FIWARE.Theme.IoT.Gateway.ServiceControl<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1867&group_id=11&atid=193>
Do you agree with our observations or do you have any other opinions?
Best regards,
Sabrina and Gian Piero

Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Bisztray, Denes (NSN - HU/Budapest)
Inviato: venerdì 15 giugno 2012 15:51
A: fiware-iot at lists.fi-ware.eu
Oggetto: [Fiware-iot] Tracker and Materializing Wiki


Dear All,

Lorant and myself compared the updated Materializing Internet of Things (IoT) Services Enablement in FI-WARE wikipage with the Forge Tracker. Now they are in complete sync.

1.      Please check the tracker in case we made some errors.

2.      Whenever someone makes changes to one, should change the other as well. Please keep this in mind.

Best,

Dénes

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.

[cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120615/a5c5eb72/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120615/a5c5eb72/attachment.jpg>


More information about the Old-Fiware-iot mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy