I2ND Interface to Networks and Devices Hans J. Einsiedler (Deutsche - - PowerPoint PPT Presentation

http://www.fi-ware.eu http://www.fi-ppp.eu

I2ND – Interface to Networks and Devices

Hans J. Einsiedler (Deutsche Telekom) and the I2ND team

FI Core Platform Architecture: main chapters

Operations Trust and Security Functionality

Developer tools

Service delivery Cloud Hosting Internet

• f Things

Support Services

I2ND = Interface to Network and Devices

I2ND General Architecture

• Four Classes of Interfaces (FI-WARE Generic Enablers)
• CDI: Connected Devices Interfacing
• CE: Cloud Edge
• NetIC: Network Information and Control
• S3C: Service, Capability, Connectivity, and Control

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 3rd Party Developers

CDI partial support – the follow will be available for the release R2.3:

QoE Device Orientation Device Motion Geolocation QoS File System Access Gallery Sensor Discovery Contacts File System Access

Sub-GEs ready end of March

QoE Device Orientation Device Motion Geolocation

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

Home automation: Local intelligence in the cloud proxy keeps the regulation active even if the data link falls down

• Cloud based application lots of

features, remote access, link with other apps…

• AirCo

Mgmt Remote control High level application

Mini local application

!"#$

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

Open Flow Network Module GEi available by end of March Netic API Handler: RESTful interface for other NetIC functional modules Programmable network functionalities Abstraction of resources Statistics extractor: SNMP based Traffic statistics Links statistics Node Statistics Planned for Release R2.3: Network Synchronization: Retrieve network information Further GEi’s planned for Release R2.3 Virtual Network Provider Network Element Virtualizer Topology Information Module

NetIC Openflow Network NetIC API Handler Applications World S3C GE, other network

• rchestrator

Statistics extractor Network Synchron i-zation

Availability of NetIC Sub-GEs

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

FI-WARE Testbed @Sevilla S3C Testbed @Berlin NetIC NetIC S3C GW

UCPs

S3C GW Legend Generic Enabler Customers Device (sensor, mobile phone, actor etc.) Cloud Edge Cloud Edge Devices with CDI functionality 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).

Access of S3C environment – Case 2

FI-WARE Testbed @Sevilla S3C Testbed @Berlin NetIC NetIC S3C GW

UCPs

S3C GW Legend Generic Enabler Customers Device (sensor, mobile phone, actor etc.) Cloud Edge Cloud Edge Devices with CDI functionality UCP accesses the GEs in the FI-WARE testbed through UCP devices and the S3C testbed and uses S3C GE.

Access of S3C environment – Case 3

FI-WARE Testbed @Sevilla S3C Testbed @Berlin NetIC NetIC S3C GW

UCPs

S3C GW Legend Generic Enabler Customers Device (sensor, mobile phone, actor etc.) Cloud Edge Cloud Edge Devices with CDI functionality Mix of case 1 and case 2.

Thank you!

• I2ND team