A couple of M2M Research Activities in Telenor - A distributed M2M Service Platform. Stein Svaet, June 4, 2008

Transcription

1 A couple of M2M Research Activities in Telenor - A distributed M2M Service Platform Stein Svaet, June 4, 2008 (stein-wegard.svaet@telenor.com)

2 Outline What are we doing? Reference Architecture CO Top-Level Architecture Overview Inside the CO Service Platform: Overview, Basic Functional Area, Features Functional Area, Advanced Functional Area Dynamic Flexibility Service Oriented Architecture CO Platform Highlights Strategic Issues Invitation to Discussion Can do!

3 What are we doing? Design a service platform for M2M applications The concept is called Connected Objects (CO) Service Platform Connected Objects services or devices able to communicate in some way. Devices are e.g. sensors, actuators, display, keyboards, etc The CO Service Platform is highly adaptable and will meet requirements for Small and large scale operations Fast development and deployment Application specific functionality, e.g. security, management of the connected objects,

4 Reference Architecture External service providers Internet/ leased line Customers Internet/ leased line Platform services Platform Transport network Internet/leased line Access network T/G LC S S T/G LC S

5 CO Top-Level Architecture Overview Service Providers Customers API / GUI / Portal OSS/BSS CO Service Platform CO-Interface Networks Sensor/ Device GW Sensor/ Device Sensor/ Device Sensor/ Device Smart device Smart Device CO Operating System COOS

6 Inside the CO Service Platform: Overview COOS Basic COOS Advanced Platform Management Legacy Support Desktop Logic Message Handling Context Object enrichment COOS Features Service Repository Service Enablers Object Management Plugin Framework Security Persistence Control and Optimisation

7 COOS Basic COOS Advanced Platform Management Legacy Support Desktop Inside the CO Service Platform: Basic Functional Area Logic Message Handling Context Object enrichment COOS Features Object Management Persistence Service Repository Service Enablers Plugin Framework Security Control and Optimisation Message Handling Carrier independent and scalable (can be segmented in subnets) Functions for sequencing, security, event subscription, multicast/broadcast, fault tolerant routing Logic Java framework for service execution Supports applications on large servers, PCs, mobiles, sensors Available implementations targeted for OSGi, J2EE, J2ME, J2SE

8 COOS Basic COOS Advanced Platform Management Legacy Support Desktop Inside the CO Service Platform: Features Functional Area Logic Message Handling Context Object enrichment COOS Features Object Management Persistence Service Repository Service Enablers Plugin Framework Security Control and Optimisation Object Management End-user management Functions for access levels (groups, role based, user based, ), SLA, learning, macros, life cycle management Persistence Use an existing database solution Plugin Framework API that enables development of drivers between objects and the platform Support for selected standards for connecting, e.g. http, web service, JMS, ESB, UPnP... Framework independent of technology (Java,.Net, C/C++, scripting language) Control and Optimisation SLA, QoS, load balancing, priority Security End-to-end security Functions for encryption, non-repudiation, privacy, logging,

9 COOS Basic COOS Advanced Platform Management Legacy Support Desktop Inside the CO Service Platform: Advanced Functional Area Logic Message Handling Context Object enrichment COOS Features Object Management Persistence Service Repository Service Enablers Plugin Framework Security Control and Optimisation Platform Management Configuration of devices/provisioning 3rd party provider & application management Package handling (RPM/DEB lookalike) Context presence preferences Object Enrichment Metadata Repository Discovery Legacy Support Support for OSS/BSS systems Service Repository Services can be interfaces towards objects or an actual service Desktop Portal/GUI/HMI Development tools Service Enablers GIS / location Temperature ParlayX Messaging (SMS/MMS) GSM location Call Control User status Charging

10 Dynamic Flexibility

11 Service Oriented Architecture Component structure is service oriented Application Aggregated API As a service enabler API Execution among the platform components COOS A COOS F COOS B Plugin FW Connected Object

12 CO Platform Highlights Powerful functionality Powerful tools for message handling and service execution Optional functionality for object management, persistence, driver development, control and optimisation, security, platform management, context management, object enrichment, legacy support, portal/gui/hmi, location, call control, charging, Technology independence Separation of functionality and physical objects Support of small and large units, smart and simple objects Network technology independence, e.g. change of communication bearer does not affect the platform logic Flexible deployment methods, runtime deployment and configuration SOA / Web2.0 approach

13 Thank you! Questions? Some relevant themes for discussion Open Source vs Standardisation Scalability requirements