I2ND – Interface to Networks and Devices Hans J. Einsiedler (Deutsche Telekom) and the I2ND team http://www.fi-ware.eu http://www.fi-ppp.eu
FI Core Platform Architecture: main chapters Internet Support Service delivery Cloud Hosting of Things Services Trust and Security Functionality Developer Operations tools I2ND = Interface to Network and Devices
I2ND General Architecture Four Classes of Interfaces (FI-WARE Generic Enablers) � NetIC: Network Information and Control � CDI: Connected Devices Interfacing � S3C: Service, Capability, Connectivity, and Control � CE: Cloud Edge The interfaces � Expose corresponding network state information to the user � Offer a defined level of control and management � Aim to overcome limitations of today's network and device interfaces � Combining different worlds: � Telecommunication services (Session Initiation Protocol – SIP – speaking) � Web-services (Simple Object Access Protocol – SOAP – speaking) � Openness to other Future Internet worlds �
Connected Devices Interfacing (CDI)
CDI Architectural Overview
List of Sub-GEs for 3 rd Party Developers CDI partial support – Sub-GEs ready end of March � QoE the follow will be available for � Device Orientation the release R2.3: � QoE � Device Motion � Device Orientation � Geolocation � Device Motion � Geolocation � QoS � File System Access � Gallery � Sensor Discovery � Contacts � File System Access Implementations are available for the Android operating system!
Cloud Edge (CE) Overview SPM: The Service Platform Manager Interface VES: The Virtual Environment System RM: The Resource Monitoring System RC: The Resource Controller System
The CE / Cloud Proxy Example: In a home environment ������������ ��������� ��� ����������� ������� ���� ����� �������������� �������� ����������
CE Use case High level application ������������ ��������� ������ �������� !���"�#$ ����� Remote Mini local application control Home automation: � Local intelligence in the cloud proxy � AirCo keeps the regulation active even if the Mgmt data link falls down � Cloud based application � lots of features, remote access, link with other apps…
CE Availability [1] 3 versions of the cloud proxy: � Release R1.3 (July 2012): � simplified version without RC & RM � no integration with the cloud (the “Cloud Operator” module is simulated with a PC) � available as a PC SW (over a standard Linux distribution) or on a dedicated HW (super gateway) � Release R2.3 (July 2013 – Beta in April 2013): � all features implemented � (depending on the open calls): integration with the cloud � OSGi available as a dedicated VM � running on a dedicated HW (small “CE-marked” box) � April version will be a beta (will be updated in July). Available upon special request (preview) � Release R3 or earlier (Dec 2013): � more stable version � includes more features (to be discussed) accordingly to the UC needs
CE Availability [2] Hardware version of the Cloud Proxy: The CP will only be available as a HW+SW box (after April 2013). � Available to anybody wanting to use/evaluate it (partner or not) � Sold without profit (price tbd, in the 150€ range) � Small quantities are available for free for the FIWARE partners (mainly I2ND/IoT/Cloud WP) � Based on an existing (ie: under mass-production) HW, it is CE-market and can be used in home environment with “normal users”. Specs: x86 ATOM CPU, 4GB storage (flash), 2GB RAM, small form factor (~80x200x150mm), USB2 ports (supports webcam, hard disk, Zigbee dongle).
CE Availability [3] The cloud proxy is delivered with: � An install manual � A User’s & programmers guide � An API guide � Some examples implemented as VMs (full source + comments): � A simple web server (“hello world” app) � A simple NAS (small file server – NFS & Samba) � A simple home automation example (using OSGi or not) � A data caching proxy example using cloud-based services (the user can use the CP as a cache device while uploading content to the net) � An OSGi framework has been implemented by TID as a VM running on the Cloud Proxy.
Network Information and Control (NetIC)
NetIC GE for Developers Four different Sub-GEs available each featuring a different functional architectural block � Virtual Network Provider � remote installation, accessible via public IP address � Network Element Virtualizer � remote installation, accessible via public IP address � Open Flow Network Module � source code for self-installation � Topology Information Module � source code for self-installation
Availability of NetIC Sub-GEs Open Flow Network Module GEi � available by end of March � Netic API Handler: � RESTful interface for other NetIC functional modules � Programmable network functionalities S3C GE, other Applications � Abstraction of resources network World orchestrator � Statistics extractor: � SNMP based � Traffic statistics � Links statistics NetIC API Handler � Node Statistics Network NetIC Statistics � Planned for Release R2.3: Synchron extractor i-zation � Network Synchronization: � Retrieve network information Further GEi’s planned for Release R2.3 � Virtual Network Provider � Network Element Virtualizer Openflow Network � Topology Information Module
Service, Capability, Connectivity, and Control (S3C)
Sub-GEs of S3C Availability for March � OpenEPC, features available in March Planned for the release R2.3: � SMS+MMS Enabler � Seamless Network Connectivity � Network Identity Management � API Mediation � TelekomAS Planned for the release R3.3 � Positioning Enabler � Inter-operator interface (ETICS)
Access of S3C environment – Case 1 UCP accesses the GEs of the FI-WARE and the S3C testbed but no physical access of UCP devices to the S3C testbed (device information are provided by I2ND). FI-WARE Testbed @Sevilla Legend S3C GW Generic Enabler Customers Device (sensor, mobile UCPs phone, actor etc.) S3C GW NetIC NetIC S3C Testbed Cloud Cloud @Berlin Edge Edge Devices with CDI functionality
Access of S3C environment – Case 2 UCP accesses the GEs in the FI-WARE testbed through UCP devices and the S3C testbed and uses S3C GE. FI-WARE Testbed @Sevilla Legend S3C GW Generic Enabler Customers Device (sensor, mobile UCPs phone, actor etc.) S3C GW NetIC NetIC S3C Testbed Cloud Cloud @Berlin Edge Edge Devices with CDI functionality
Access of S3C environment – Case 3 Mix of case 1 and case 2. FI-WARE Testbed @Sevilla Legend S3C GW Generic Enabler Customers Device (sensor, mobile UCPs phone, actor etc.) S3C GW NetIC NetIC S3C Testbed Cloud Cloud @Berlin Edge Edge Devices with CDI functionality
I2ND team Thank you! ��
Recommend
More recommend
