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

[Jean-Pierre Le Rouzic]

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: CAM_0407.jpg
Type: image/jpeg
Size: 284350 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120123/f6bd628a/attachment.jpg>