________________________________ From: Einsiedler, Hans Sent: Donnerstag, 8. September 2011 20:42 To: fiware-i2nd at lists.fi-ware.eu Subject: RE: [Fiware-i2nd] [FIWARE 7.4 S3C] What I understand about about S3C architecture Dear all, please find attached the assets from Deutsche Telekom. I am still working on an additional one. Cheers, Hans Message Classification: [ ] Public [ ] Private [X] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary ________________________________ From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of jeanpierre.lerouzic at orange-ftgroup.com Sent: Mittwoch, 7. September 2011 09:32 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] [FIWARE 7.4 S3C] What I understand about about S3C architecture Hi all, >From what I saw on the email list for S3C (WP7.4) there are three partners proposals. I may have missed other, sorry for that. I think for myself it's important to know how those proposals relate to each other. S3C goal is to bridge the services realm with the non virtualized Telecom networks. So as Marius-Julian recalled S3C is mainly a bridge between a north interface to the service realm and a south bridge to non virtualized network such as LTE/EPC. Let say as Fokus did in its Epics that there are three layers in S3C * Exposure * Core * Network What features do we have? Can we at least group proposals by these layers? We know that: * Exposure layer: o Fokus will expose context of the devices offered in an aggregated manner by the network operator, including location, device status and user activity and network context from nearby network nodes as well as network events which would influence my service delivery o Orange will provide on a API management layer (SLA, AAA), a Web/Telecom gateway, a Telecom AS, partial OneAPI enabler for LTE, Voice messaging platform. * Core: o Fokus controls when and how the devices connect to the network as well as the resources allocated to each device for the best delivery of their data flows according to the requirements of the applications (AAA and security , SLA) * Network: o Fokus will optimise data exchanged with the mobile device even though communication has specific characteristics such as small messages, broadcast or multicast. o Ericsson Device Connection platform contains API's for Reporting of statistics of connection quality and usage, Remote device management, What is your opinion, what would you change? Best regards, Jean-Pierre -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20110909/9b60ae9b/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 110902_DTAG_assets_v0.01.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 917681 bytes Desc: 110902_DTAG_assets_v0.01.docx URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20110909/9b60ae9b/attachment.docx>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy