1 / 11

FI-WARE Interface to Networks and Devices (I2ND) July 2011

High-level description. FI-WARE Interface to Networks and Devices (I2ND) July 2011. Connected Devices Interfacing (CDI). The CDI GE maps to software running on the devices providing APIs for accessing device capabilities, resources, contextual information and locally stored contents.

nascha
Download Presentation

FI-WARE Interface to Networks and Devices (I2ND) July 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. High-level description FI-WAREInterface to Networks and Devices (I2ND)July 2011

  2. ConnectedDevicesInterfacing (CDI) • The CDI GE mapsto software runningonthedevicesproviding APIs for accessing device capabilities, resources, contextual information and locally stored contents

  3. ConnectedDevicesInterfacing (CDI) • The architecture of the CDI GE implements a Connected Device Interfacing Layer (CDIL) providng a set of CDIL-NET and CDIL-APP interfaces • The CDIL may be implemented for a concrete device platform (i.e., device architecture, supported programming paradigm, device Operating Sytem, etc.) However, a CDIL-PAL interface will be specified aiming at providing an abstraction of the underlying device platform, thus enabling part of the CDIL implementation to be portable across several families of devices • While the CDIL-NET and CDIL-APP interfaces will be mandatory for implementations of the CDIL in order to claim compliance, the CDIL-PAL will not.

  4. ConnectedDevicesInterfacing (CDI) • Communication: • Network Status • QoS and QoEmeasurement • DeviceServices: • Access to sensor info (GPS, accelerometer, …) • Access toDevicefeatures(battery, display, memory, …) • Interactionwithotherdevicesusing Short Range Radio orproximitytechnologies • Management of Privacy and Security Aspects • Remote Management • Personal/Data Services • Userprofile, identity • Access to Personal Information Management (PIM): Calendar, Contacts, Tasks, … • Access toLocallystored data • Messagingcapabilities • Media Services • Graphicsrendering • Streamingfeatures

  5. Interfaces to Cloud Proxies 1 Gb/s LAN ADSL link to Cloud Services in the Cloud Intermediatestoragecapacities Computingcapacities Cloud proxy / Gateway PCs Tablets TV sets Game Consoles Home Network

  6. Interfaces to Cloud Proxies External API OtherProxies Cloud 1 Internal API Ad-hoc communications protocols Virtual Machines 3 2 4 Protocol adaptation VM management Outside communication 5 6 Home system management 10 7 End-device communication Cloud proxy GE 9 Permanent storage 8 Cloud proxy End devices

  7. Network Information and Control (NetIC) • The Network Information and Control (NetIC) Generic Enabler will provide to FI-WARE chapters as well as Usage Area applications and services the means to optimally exploit the network capabilities, by means of the implementation of APIs towards networking elements • NetIC will provide an abstraction of the physical network resources, as well as the capability to control them (up to certain limitations given by the physical resources’ owner and operator) • The NetIC Generic Enabler is expected to provide access to the following functions: • Interface Control: This function will provide information about the status of a network element interface. Callers may also be able to change selected parameters. An example would be interface activation or deactivation. • Topology: This function will provide abstract information about the nodes, edges, and how they are interconnected. Furthermore it may allow the modification of network topology. An example for the latter case would be the setup of a virtual network.

  8. Network Information and Control (NetIC) • The NetIC Generic Enabler is expected to provide access to the following functions (cont.): • Path Statistics: This function will allow querying the properties of an end-to-end path. An example query function would be an estimation of the available bandwidth on a path, or its packet end-to-end delay. • Path Control: This function will provide mechanisms to change the current status of a path. The realization of this function as well as its actual scope of operation will be technology dependent due to, e.g., the different realization of packet-oriented and circuit-switched networks. It will affect the setup, modification, and teardown of paths. • Traffic Statistics: Various types of information about the network usage may be of interest. This function will provide access to such statistics and potentially a control over the monitoring process. • Traffic Control: This function will allow influencing, e.g., the handling of different traffic types in the network (e.g. priorization of traffic according to DiffServ). This enables differentiated provisioning of QoS.

  9. Service, Capability, Connectivity, and Control (S3C) • The Service, Capability, Connectivity, and Control (S3C) GE will provide an interface to the Evolved Packet Core (EPC) network control layer for Fixed-Mobile-Convergence • Evolved Packet Core (EPC) is a new IP connectivity control platform enabling wireless seamless access to a wide range of diverse networks (including LTE, UMTS, WiMAX, WiFi etc.)

  10. Service, Capability, Connectivity, and Control (S3C) • Functional Blocks withinthe S3C GE: • Network Event Management (NEM) • Resource Management • Network Identity Management (NIM) • Operator SA4C (OSA4C) including Legal Interception (LI) • Connectivity Management Entity (CME) • Multicast/Broadcast (MC/BC) Management (MC-BC-M) • Network Data Caching and Aggregation (NDCA) • Small Data Pull/Push (SDPP) • Network Context Data Management (NCDM) • Inter Carrier Management (ICM)

  11. Thank You !!

More Related