Post on 07-Feb-2016
description
Bangalore, India ,17-18 December 2012
Sustainable Rural Broadband Communications
Seth NewberryGeneral Manager
Open Mobile Alliance Ltd.snewberry@omaorg.org
Joint ITU-GISFI Workshop on “Bridging the Standardization Gap: Workshop on
Sustainable Rural Communications”(Bangalore, India, 17-18 December 2012)
1
Problem StatementExponential growth in consumer-facing application. M2M applications poised to explodeWill drive order-of-magnitude increases in bandwidth consumption and provisioning and control actions.Many applications are poorly adapted for the constraints posed by wireless networks. But wireless is essential in bridging the digital divide especially in rural areas.Protocols that manage the services and devices efficiently are essential if the promise of untethered applications is to be fulfilled.How do mobile operators deploy networks that efficiently serve populated areas with their onslaught of M2M devices as well as rural areas that need both high speed data and M2M services?
Bangalore, India ,17-18 December 2012 2
Standardization
Standards Development Organizations play an important role in development of efficient protocols. They are the one place where the technical merits of a particular approach can be debated and decided by the relevant body of operators and suppliers – where all come together with an equal voice.
Bangalore, India ,17-18 December 2012 3
OMA – Mission and Background
The mission of the Open Mobile Alliance is to facilitate global user adoption of mobile data services by specifying market driven mobile service enablers that ensure service interoperability across devices, geographies, service providers, operators, and networks while allowing businesses to compete through innovation and differentiation.Founded in June 2002Telecommunications Operators, Telecommunications
Equipment, Terminal and Software vendors, Content providers and ICT companies with members evenly represented from Europe, Asia, and the Americas
Bangalore, India ,17-18 December 2012 4
A Broad Set of TechnologiesA Vibrant Work Program
Game Service Application Programming Interface V1.0 AERSimplified Converged Address Book V1.0 CERConverged Address Book V1.1 CERSIP/SIMPLE Based IM Service Definition V1.0 AERSIP/SIMPLE Based IM Service Definition V2.0 CEREnhanced Visual Voice Mail Service V1.0 CERPolicy Evaluation, Enforcement and Management V1.0 AERRESTful bindings for Parlay X Web Services V2.0 AER Presence SIMPLE V2.0 AERKey Performance Indicators for OMA Enablers V1.0 AERXML Document Management V2.2 CER Application Layer Security Common Functions V1.1 AERMobile Search Framework V1.0 AERConverged IP Messaging V1.0 AERMobile Spam Reporting V1.0 AERConverged Address Book API V1.0 CERTelecom Application Store V1.0 CEROpen Connection Manager API V1.0 CERLPP* Extensions V1.1 CERNext Generation Services Interface V 1.0 AERNext Generation Service Interfaces-SOAP V1.0 AERService User Profile Management V1.0 AERMobile Location Service V1.3 CERSecure User Plane Location V2.1 CERSecure User Plane Location V2.0 AERLock and Wipe Management Object V1.0 AER
Bangalore, India ,17-18 December 2012 5
Gateway Management Object V1.0 CER OMA Web Runtime API V1.0 CERGames Services API V1.0 CRRRESTful Network API Chat V1.0 CERRich Communication APIs V1.0 CERRESTful Network API File Transfer V1.0 CERMobile Advertising V1.0 AERCustomized Multimedia Ringing V1.0 AERSecure Content Identification Mechanism V1.0 AERRights Issuer Common Domain V1.0 AERDevice Management V1.3 CERGateway Management Object V1.0 CERCondition Based URIs Selection V1_0 AER RESTful Network API Presence V1.0 CERGuidelines for RESTful Network APIs V1_0 CRRRESTful Network for API Address Book V1_0 CERRESTful Network API for Payment V1_0 CERRESTful Network API for Messaging V1_0 CERRESTful Network for API Address Book V1_0 CERGuidelines for RESTful Network APIs V1_0 CRRRESTful Network API for Notification Channel V1_0 CERRESTful Network API for Device Capabilities V1_0 CERRESTful Network API for Short Messaging V1_0 CERLocation in SIP/IP Core V1_0 AERGeneral Service Subscription Management V1_0 CRRDiagnostic Monitoring V1_1 AER
52 Enablers published during January through September 2012
UserDevice
Server
Call Centre! How can I help you?
I cannot send MMS from my phone. What can I do?
Let me investigatePlease stand by …
Open a remote connection to the User
Device & identify the problem
Identifies that MMS configuration was lost or corrupted
Server sends a new MMS configuration file
Device Management performs the following operations on Devices that have already been deployed in the market:•Provisioning of configurations for services supported by the device, •Remove, install and activate Software Components,•Update Firmware on faulty devices,•Perform Diagnostics and Monitoring operations on the devices
Device Management (DM) Use Case
Bangalore, India ,17-18 December 2012
6
DM Adoption on a global scale
More than 60 Management Objects have been registered by OMA Working Groups More than 30 Management Objects from other SDOs
3GPP, ETSI, WiMax Forum among them
Bangalore, India ,17-18 December 2012 7
A Management Object is a data model that is used in conjunction with OMA DM to allow both server and client to perform certain functions while being agnostic to vendor implementations.
Commercial DM Deployment on a Global Scale
OMA has achieved commercial deployment of 1.4 Billion devices implementing the Firmware Update Management Object enabler
Bangalore, India ,17-18 December 2012 8
DM in M2M related OMA activities
In addition to OMA DM (v 1.3), several OMA Enablers, already developed or under specification, may fit in M2M scenarios in different ways.
OMA DM 1.3 Profiling (specifically for M2M context)OMA DM 2.0 (next generation RESTful based DM Protocol)Lightweight M2M (protocol for service delivery and management of constrained device)OMA DM Gateway (for managing device through a Gateway)OMA CPNS, OMA SUPL, the Device API Program, …
Bangalore, India ,17-18 December 2012 9
OMA DM used in M2M applicationsPress release, May 21st 2012 – Sprint, Metrum, Tollgrade
Make Smart Grid Smarter Enabling smart meters with wireless connectivity
Both Metrum and Tollgrade have completed OMA Device Management certification
Bangalore, India ,17-18 December 2012 10
“Over the Air”Management
and configurationof devices
and efficient use of networkresources.
Suitable for large-scale deployments
OMA and oneM2M
OMA collaborated with ETSI TC M2M during the specification of ETSI M2M Release 1:OMA DM is natively included in the Functional Architecture and several Management Objects have been specified.OMA, in the very best interest of collaboration, harmonization and coordination, welcomes oneM2M Global Initiative.
OMA is a oneM2M Partner Type 2 and actively participating in oneM2M activities
Bangalore, India ,17-18 December 2012 11
M2M and Rural Broadband Rural broadband:Bridges the digital divideBenefits various M2M applications, such as:
Agriculture: what crops to plant and where to sellWeather forecasts/trendsRight price for the goods: some Kenyan farmers sell directly to American market through EarthMarketplace bypassing the distributorRemote healthcare and monitoring
Helps sustainable rural social, economic, cultural, and educational developments, and henceHelps rural communities achieve economic self-
sufficiency.
Bangalore, India ,17-18 December 2012 12
Making the Enablers Available
Ultimately, the key to success of any enabling technology is its adoption.OMA has a program of Application Programming Interface (API) development for many of the specifications it produces. This program helps make implementation of the OMA service enablers easier for application developers.
Bangalore, India ,17-18 December 2012 13
OMA APIs Standardize Access to Unique Resources within Operator Networks
Bangalore, India ,17-18 December 2012 14
CSP can reach a subset Apps
Does not scale
App can reach a subset of Subs
APIs Proliferate
Bangalore, India ,17-18 December 2012 15
The Value of Standardized APIs
Available toany developer community
independent of thedevelopment platform
Expose network assetsindependent of thesignaling protocols,network platforms,
or access technology
Reduces development costand time-to-marketfor new applications
and services
Simplifies and fuelswider deployment ofexisting applications
and services
Operators benefitDevelopers benefit
Users benefit Everybody benefits
Bangalore, India ,17-18 December 2012
16
31 Members Endorsing the API Program
Aepona Alcatel-Lucent AT&T Bell Mobility Birdstep Technology Cambridge Silicon Radio China Mobile China Unicom China Telecom Comverse
Deutsche Telekom AG Ericsson ETRI GSM Association (GSMA) Hansol Inticube HTC Huawei Technologies Interop Technologies NEC Corporation Nokia Siemens NetworksNeustar
Oracle Orange SA Red Bend Software Smith Micro Software Songdo Telecom, Inc. Telecom Itália Telenor ASA TeliaSonera U.S. Cellular ZTE Corporation
These endorsing member companies represent a wide spectrumof industry players, including operators, equipment manufacturers,and software vendors from all geographies across the globe,signifying very strong signal of industry support!
Bangalore, India ,17-18 December 2012 17
Cooperation is the keyNo single organization meets everyone’s needs.OMA collaborates with other bodies—including GSMA & ETSIOMA maintains formal cooperation agreements or frameworks with nearly 50 industry bodiesA Board level program with appointed ambassadors to champion other bodies inside OMAIPR policies harmonized with many of the major SDOs including ETSI and ITU-T to make information exchange and cross-referencing as easy and effective as possibleOMA welcomes collaboration and input from other bodies in an effort to reduce duplication and fragmentation
Bangalore, India ,17-18 December 2012 18
Bridging the Standardization Gap
Companies that participate in Standardization work make a long term investment in their own success. The opportunity to work with a world-wide community of technologists who can help define the efficient protocols that can cope with the traffic and application demand of the future.
Helping ensure long-term interoperability of applications and ensure that services have the opportunity to work seamlessly between networks, between countries, between devices.
Bangalore, India ,17-18 December 2012 19
Bangalore, India ,17-18 December 2012
OMA Device Management Architecture
Eshwar Pittampalli, Phd.Director, Market Development
Open Mobile Alliance Ltd.epittampalli@omaorg.org
Joint ITU-GISFI Workshop on “Bridging the Standardization Gap: Workshop on
Sustainable Rural Communications”(Bangalore, India, 17-18 December 2012)
20
DM-Introduction
DM Protocol
DM Commands:Add, Get, Replace, Delete, Exec, Alert, etc.
DM Client DM ServerTransports
DM Protocol
DM Representation
Bindings to Transports
Application MO
Technology that enables device customization and services configuration in a remote fashionThe Enabler defines the syntax and semantics of the two-way message exchange protocol (DM Protocol)Configuration and management is exposed in a logical interface, which is represented under the structure of a MO (Management Object) within the management tree.
OBEX HTTP
TCP / IP
WSP
WAPIrDA
21Bangalore, India ,17-18 December 2012
DM-Architecture
OBEX HTTP
TCP / IP
WSP
WAP
DM Payload
IrDA
DM Client
DM Server
Bootstrap Server
Push Proxy Gateway
DM-1 DM-2
DM-4
DM-3
DM-1: DM Protocol
DM-2: DM Notification
DM-3: Smartcard Bootstrap
DM-4: DM Bootstrap & CP
22Bangalore, India ,17-18 December 2012
OMA DM already in M2M specifications
4.1.2 OMA-DM/BBF-TR069 Integration*
*23Bangalore, India ,17-18 December 2012
M2M Use cases and terminology
Device embedded in the car
Peter’ s car PeterPeter’ s smart phone
M2M Server
Network Connection
Network Provider M2M Service Provider
Use Cases (Some Examples):Streetlight controlAir conditioningMovable Asset Management
2424Bangalore, India ,17-18 December 2012
M2M Use Case Terminology:M2M Network ProviderM2M Service ProviderM2M User
LightWeight M2M (LWM2M) Architecture
LWM2M Enabler
LWM2M Server
LWM2M Client
LWM2M-1:Device
Discovery and Registration
LWM2M-3:Device
Management and Service Enablement
LegendComponents specified by this Enabler
XYZ-n
Indicates Use of an interface exposed by an Enabler/Component. The Enabler/ Component offering or exposing interface is indicated by the arrowhead.
Name of the interface offered or exposed by Enabler/Component XYZ(following the interface naming convention)
LWM2M-4:Information Reporting
LWM2M-2:Bootstrap
LWM2M enabler focuses not only on management but also on service enablement of LWM2M devicesThe LWM2M devices are in particular Resource Constrained (consumes low power and is limited in its CPU, memory, I/O for processing requests)LWM2M protocol provides a light and compact protocol and a flat data structure
SIM Smartcard
2525Bangalore, India ,17-18 December 2012
LWM2M Entity Relationship Overview (1/3)
LWM2M Client
LWM2M Client
LWM2M Client
LWM2M Server M2M ApplicationNetwork Service Provider's Network
M2M Service Provider
M2M User M2M User
LWM2M Client
LWM2M Client
LWM2M Client
M2M Application
M2M Service Provider
M2M User M2M User
LWM2M ServerNetwork Service Provider's Network
Single M2M Server
2626Bangalore, India ,17-18 December 2012
LWM2M Entity Relationship Overview (2/3)
LWM2M ServerM2M Application
#2
M2M Application #1
Network Service Provider's Network
LWM2M ServerM2M Application
#4
M2M Application #3
LWM2M Client
Multiple M2M Servers
M2M Service Provider 1
M2M Service Provider 2
An M2M User may subscribe to multiple M2M Service Providers that run multiple and get multiple services
2727Bangalore, India ,17-18 December 2012
LWM2M Entity Relationship Overview (3/3)
LWM2M ServerM2M Application
#2
M2M Application #1
Network Service Provider's Network
LWM2M ServerM2M Application
#4
M2M Application #3
LWM2M Client
Multiple M2M Servers
M2M Service Provider 1
M2M Service Provider 2
Although a device is connected to multiple M2M Servers, it can switch from one to another to perform some specific tasks
LighweightM2M enabler
M2M Server (of Service Provider)
M2M Device
M2M User
M2M Server (of Device Manufacturer)
1
2
1 A command comes from user or SP to make the device switch to another server for specific task
2 M2M device logouts from the original M2M server
3
3 M2M device register and login on another M2M server.
4
4 M2M device perform a specific task, updating firmware for example
5
5 M2M device logouts from the second M2M server
6
6 M2M device login on the original M2M server
2828Bangalore, India ,17-18 December 2012
Sustainable Rural Broadband Communications
Joint ITU-GISFI Workshop on “Bridging the Standardization Gap: Workshop on
Sustainable Rural Communications”(Bangalore, India, 17-18 December 2012)
29Bangalore, India ,17-18 December 2012