[Fiware-i2nd] [FIWARE 7.4 S3C] What I understand about about S3C architecture

[jeanpierre.lerouzic at orange-ftgroup.com]

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/20110907/9d20f81d/attachment.html>