[Fiware-i2nd] [fiware I2ND] a look at I2ND and S3C assets and possible architecture

[Corici, Marius-Iulian]

Hello,

Please find attached a tentative integration between the picture from the meeting in Berlin and Jeanpierre's one including only the S3C related interfaces. 

Not clearly depicted: each asset integrated into S3C has a counterpart in the mobile device which may or may not be part of the new development in CDI. 

Also the interconnection with the cloud gateway remains a bit in the grey area. Is the CE a user endpoint from an operator perspective? If yes, then it can be grouped with the CDI. Is the CE an operator managed node to which content has to be transferred? If yes, then it can be better considered as part of the open network endpoints, thus fitting better to be handled with intra-operator communication mechanisms. 

Any comments are more than welcomed. See you in aprox. three hours. 

Greetings,
Marius Corici


-----Original Message-----
From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Jean-Pierre Le Rouzic
Sent: Monday, January 23, 2012 10:54 AM
To: jozsef.varga at nsn.com; thomas-rolf.banniza at alcatel-lucent.com; castrucci at dis.uniroma1.it; pasquale.donadio at alcatel-lucent.com; marius.corici at fokus.fraunhofer.de; hans.einsiedler at telekom.de; fiware-i2nd at lists.fi-ware.eu; pierangelo.garino at telecomitalia.it
Subject: [Fiware-i2nd] [fiware I2ND] a look at I2ND and S3C assets and possible architecture

Hi all,

While traveling I tried to sketch how NetIC and S3C assets could be interconnected and what kind of APIs it would offer as a whole, and what is missing in descriptions.
I found that the NetIC and S3C are indeed well connected as we should expect.
A central element is OpenEPC, I will come back later to that.
The connection toward CDI (devices) exists but should probably be enriched.
The connection to CE (cloud edge aka domestic platform) is unclear for me.

The interfaces to devices seems to be offered mainly by the three following assets: Device connection platform (indeed), DAE, Seamless Network Connectivity.

On the overall it seems to me there are three layers for the two tasks assets: 
(a) The upper is comprised of "Api mediation layer", "Network ID management" and as example of implementation for this upper part we found "Telecom AS" and "VoiceMail enabler".
(b) The middle layer is in fact OpenEPC
(c) The lower layer is composed of DCP, DAE, NOX, SNC, RM, NEV.

This lower layer itself interfaces at a lower layer to:
- 3GPP/TISPAN IP access network functions
- OpenFlow enabled routers
- Other IP routers
- Non IP routers (for example MPLS)

A picture is attached to this email.

Please send me your feed back.

Best regards,

Jean-Pierre
-------------- next part --------------
A non-text attachment was scrubbed...
Name: S3C asset integration.pptx
Type: application/octet-stream
Size: 283654 bytes
Desc: S3C asset integration.pptx
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120124/0ce391f6/attachment.obj>