Joint ITU-GISFI Workshop on Bridging the Standardization Gap

Joint ITU-GISFI Workshop on “Bridging the Standardization Gap: Workshop on Sustainable Rural Communications” (Bangalore, India, 17 -18 December 2012) Sustainable Rural Broadband Communications Seth Newberry General Manager Open Mobile Alliance Ltd. snewberry@omaorg. org Bangalore, India , 17 -18 December 2012 1

Problem Statement Exponential growth in consumer-facing application. M 2 M applications poised to explode Will 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 M 2 M devices as well as rural areas that need both high speed data and M 2 M 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 2002 Telecommunications 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 Technologies A Vibrant Work Program 52 Enablers published during January through September 2012 Game Service Application Programming Interface V 1. 0 AER Simplified Converged Address Book V 1. 0 CER Converged Address Book V 1. 1 CER SIP/SIMPLE Based IM Service Definition V 1. 0 AER SIP/SIMPLE Based IM Service Definition V 2. 0 CER Enhanced Visual Voice Mail Service V 1. 0 CER Policy Evaluation, Enforcement and Management V 1. 0 AER RESTful bindings for Parlay X Web Services V 2. 0 AER Presence SIMPLE V 2. 0 AER Key Performance Indicators for OMA Enablers V 1. 0 AER XML Document Management V 2. 2 CER Application Layer Security Common Functions V 1. 1 AER Mobile Search Framework V 1. 0 AER Converged IP Messaging V 1. 0 AER Mobile Spam Reporting V 1. 0 AER Converged Address Book API V 1. 0 CER Telecom Application Store V 1. 0 CER Open Connection Manager API V 1. 0 CER LPP* Extensions V 1. 1 CER Next Generation Services Interface V 1. 0 AER Next Generation Service Interfaces-SOAP V 1. 0 AER Service User Profile Management V 1. 0 AER Mobile Location Service V 1. 3 CER Secure User Plane Location V 2. 1 CER Secure User Plane Location V 2. 0 AER Lock and Wipe Management Object V 1. 0 AER Bangalore, India , 17 -18 December 2012 Gateway Management Object V 1. 0 CER OMA Web Runtime API V 1. 0 CER Games Services API V 1. 0 CRR RESTful Network API Chat V 1. 0 CER Rich Communication APIs V 1. 0 CER RESTful Network API File Transfer V 1. 0 CER Mobile Advertising V 1. 0 AER Customized Multimedia Ringing V 1. 0 AER Secure Content Identification Mechanism V 1. 0 AER Rights Issuer Common Domain V 1. 0 AER Device Management V 1. 3 CER Gateway Management Object V 1. 0 CER Condition Based URIs Selection V 1_0 AER RESTful Network API Presence V 1. 0 CER Guidelines for RESTful Network APIs V 1_0 CRR RESTful Network for API Address Book V 1_0 CER RESTful Network API for Payment V 1_0 CER RESTful Network API for Messaging V 1_0 CER RESTful Network for API Address Book V 1_0 CER Guidelines for RESTful Network APIs V 1_0 CRR RESTful Network API for Notification Channel V 1_0 CER RESTful Network API for Device Capabilities V 1_0 CER RESTful Network API for Short Messaging V 1_0 CER Location in SIP/IP Core V 1_0 AER General Service Subscription Management V 1_0 CRR Diagnostic Monitoring V 1_1 AER 5

Device Management (DM) Use Case Device Management performs the following operations on Devices that have already been deployed in the market: Call Centre! How can I help you? • 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 Let me investigate Please stand by … Ope Dev n a rem ice & id ote con enti fy th nection e pr oble to the U m ser I cannot send MMS from my phone. What can I do? Identifies that MMS configuration was lost or corrupted Server sends a new MMS configuration file 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 3 GPP, ETSI, Wi. Max Forum among them 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. Bangalore, India , 17 -18 December 2012 7

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 M 2 M related OMA activities In addition to OMA DM (v 1. 3), several OMA Enablers, already developed or under specification, may fit in M 2 M scenarios in different ways. OMA DM 1. 3 Profiling (specifically for M 2 M context) OMA DM 2. 0 (next generation RESTful based DM Protocol) Lightweight M 2 M (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 M 2 M applications Press release, May 21 st 2012 – Sprint, Metrum, Tollgrade Make Smart Grid Smarter Enabling smart meters with wireless connectivity Both Metrum and Tollgrade have completed OMA Device Management certification “Over the Air” Management and configuration of devices and efficient use of network resources. Suitable for large-scale deployments Bangalore, India , 17 -18 December 2012 10

OMA and one. M 2 M OMA collaborated with ETSI TC M 2 M during the specification of ETSI M 2 M 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 one. M 2 M Global Initiative. OMA is a one. M 2 M Partner Type 2 and actively participating in one. M 2 M activities Bangalore, India , 17 -18 December 2012 11

M 2 M and Rural Broadband Rural broadband: Bridges the digital divide Benefits various M 2 M applications, such as: Agriculture: what crops to plant and where to sell Weather forecasts/trends Right price for the goods: some Kenyan farmers sell directly to American market through Earth. Marketplace bypassing the distributor Remote healthcare and monitoring Helps sustainable rural social, economic, cultural, and educational developments, and hence Helps rural communities achieve economic selfsufficiency. 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 CSP can reach a subset Apps App can reach a subset of Subs Does not scale Bangalore, India , 17 -18 December 2012 14

APIs Proliferate Bangalore, India , 17 -18 December 2012 15

The Value of Standardized APIs Available to any developer community independent of the development platform Expose network assets independent of the signaling protocols, network platforms, or access technology Operators benefit Developers benefit Users benefit Everybody benefits Reduces development cost and time-to-market for new applications and services Bangalore, India , 17 -18 December 2012 Simplifies and fuels wider deployment of existing applications and services 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 Networks Neustar Oracle Orange SA Red Bend Software Smith Micro Software Songdo Telecom, Inc. Telecom Itália Telenor ASA Telia. Sonera U. S. Cellular ZTE Corporation These endorsing member companies represent a wide spectrum of 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 key No single organization meets everyone’s needs. OMA collaborates with other bodies—including GSMA & ETSI OMA maintains formal cooperation agreements or frameworks with nearly 50 industry bodies A Board level program with appointed ambassadors to champion other bodies inside OMA IPR 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 possible OMA 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

Joint ITU-GISFI Workshop on “Bridging the Standardization Gap: Workshop on Sustainable Rural Communications” (Bangalore, India, 17 -18 December 2012) OMA Device Management Architecture Eshwar Pittampalli, Phd. Director, Market Development Open Mobile Alliance Ltd. epittampalli@omaorg. org Bangalore, India , 17 -18 December 2012 20

DM-Introduction Technology that enables device customization and services configuration in a remote fashion The Enabler defines the syntax and semantics of the twoway 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. Application MO DM Protocol DM Commands: Add, Get, Replace, Delete, Exec, Alert, etc. DM Representation Bindings to Transports Bangalore, India , 17 -18 December 2012 21 OBEX TCP / IP DM Protocol HTTP Ir. DA WSP WAP

DM-Architecture DM-1: DM Protocol DM Payload DM-2: DM Notification DM-3: Smartcard Bootstrap DM-4: DM Bootstrap & CP HTTP OBEX WSP TCP / IP Ir. DA WAP DM-1 DM-3 DM-4 Bangalore, India , 17 -18 December 2012 22 DM-2

OMA DM already in M 2 M specifications 4. 1. 2 OMA-DM/BBF-TR 069 Integration* * Bangalore, India , 17 -18 December 2012 23

M 2 M Use cases and terminology M 2 M Use Case Terminology: M 2 M Network Provider M 2 M Service Provider M 2 M User Use Cases (Some Examples): Streetlight control Air conditioning Movable Asset Management Bangalore, India , 17 -18 December 2012 24 24

Light. Weight M 2 M (LWM 2 M) Architecture SIM Smartcard LWM 2 M enabler focuses not only on management but also on service enablement of LWM 2 M devices The LWM 2 M devices are in particular Resource Constrained (consumes low power and is limited in its CPU, memory, I/O for processing requests) LWM 2 M protocol provides a light and compact protocol and a flat data structure Bangalore, India , 17 -18 December 2012 25 25

LWM 2 M Entity Relationship Overview (1/3) Single M 2 M Server Bangalore, India , 17 -18 December 2012 26 26

LWM 2 M Entity Relationship Overview (2/3) M 2 M Service Provider 1 Multiple M 2 M Servers M 2 M Service Provider 2 An M 2 M User may subscribe to multiple M 2 M Service Providers that run multiple and get multiple services Bangalore, India , 17 -18 December 2012 27 27

LWM 2 M Entity Relationship Overview (3/3) M 2 M Service Provider 1 Multiple M 2 M Servers M 2 M Service Provider 2 Although a device is connected to multiple M 2 M Servers, it can switch from one to another to perform some specific tasks Bangalore, India , 17 -18 December 2012 28 28

Joint ITU-GISFI Workshop on “Bridging the Standardization Gap: Workshop on Sustainable Rural Communications” (Bangalore, India, 17 -18 December 2012) Sustainable Rural Broadband Communications Bangalore, India , 17 -18 December 2012 29