Sustainable Rural Broadband Communications

1. 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

2. Problem Statement Exponential growth in consumer-facing application. M2M 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 M2M devices as well as rural areas that need both high speed data and M2M services?

3. 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.

4. 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

5. A Broad Set of TechnologiesA Vibrant Work Program 52 Enablers published during January through September 2012 • Gateway Management Object V1.0 CER • OMA Web Runtime API V1.0 CER • Games Services API V1.0 CRR • RESTful Network API Chat V1.0 CER • Rich Communication APIs V1.0 CERRESTful Network API File Transfer V1.0 CER • Mobile Advertising V1.0 AERCustomized Multimedia Ringing V1.0 AERSecure Content Identification Mechanism V1.0 AERRights Issuer Common Domain V1.0 AER • Device Management V1.3 CERGateway Management Object V1.0 CERCondition Based URIs Selection V1_0 AER RESTful Network API Presence V1.0 CER • Guidelines for RESTful Network APIs V1_0 CRR • RESTful Network for API Address Book V1_0 CER • RESTful 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 CER • RESTful Network API for Device Capabilities V1_0 CER • RESTful Network API for Short Messaging V1_0 CER • Location in SIP/IP Core V1_0 AER • General Service Subscription Management V1_0 CRR • Diagnostic Monitoring V1_1 AER Game Service Application Programming Interface V1.0 AER Simplified 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 AER Converged IP Messaging V1.0 AERMobile Spam Reporting V1.0 AER Converged Address Book API V1.0 CER Telecom Application Store V1.0 CER Open Connection Manager API V1.0 CER LPP* Extensions V1.1 CER Next 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 CER Secure User Plane Location V2.0 AER Lock and Wipe Management Object V1.0 AER

6. Device Management (DM) Use Case • 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 Call Centre! How can I help you? Let me investigate Please stand by … Open a remote connection to the User Device & identify the problem 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

7. DM Adoption on a global scale 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. • 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

8. Commercial DM Deployment on a Global Scale OMA has achieved commercial deployment of 1.4 Billion devices implementing the Firmware Update Management Object enabler

9. 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, …

10. OMA DM used in M2M applications “Over the Air” Management and configuration of devices and efficient use of network resources. Suitable for large-scale deployments Press 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

11. 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

12. M2M and Rural Broadband Rural broadband: • Bridges the digital divide • Benefits various M2M 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 EarthMarketplace bypassing the distributor • Remote healthcare and monitoring • Helps sustainable rural social, economic, cultural, and educational developments, and hence • Helps rural communities achieve economic self-sufficiency.

13. 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.

14. 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

15. APIs Proliferate

16. The Value of Standardized APIs Expose network assets independent of the signaling protocols, network platforms, or access technology Available to any developer community independent of the development platform Operators benefit Developers benefit Users benefit Everybody benefits Reduces development cost and time-to-market for new applications and services Simplifies and fuels wider deployment of existing applications and services

17. 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 • TeliaSonera • 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!

18. 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

19. 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.

20. 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

21. DM Commands: Add, Get, Replace, Delete, Exec, Alert, etc. DM Protocol DM-Introduction • Technology that enables device customization and services configuration in a remote fashion • The 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. HTTP WSP OBEX IrDA Application MO WAP TCP / IP DM Protocol DM Representation Bindings to Transports Transports

22. DM-Architecture DM-1: DM Protocol DM-2: DM Notification DM-3: Smartcard Bootstrap DM-4: DM Bootstrap & CP DM Profile or CP Profile DM or CP Profile PAP TCP/IP OMA DMBOOT for DM OMA ProvSC for CP ETSI TS 102.221 ISO 7816 Smartcard SMS DM Message DM Payload HTTP WSP OBEX DM-1 DM-2 DM-3 WAP IrDA TCP / IP DM-4

23. OMA DM already in M2M specifications 4.1.2 OMA-DM/BBF-TR069 Integration* *

24. M2M Use cases and terminology M2M Use Case Terminology: • M2M Network Provider • M2M Service Provider • M2M User Use Cases (Some Examples): • Streetlight control • Air conditioning • Movable Asset Management 24

25. LightWeight M2M (LWM2M) Architecture SIM  Smartcard LWM2M enabler focuses not only on management but also on service enablement of LWM2M devices The 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 25

26. LWM2M Entity Relationship Overview (1/3) Single M2M Server 26

27. LWM2M Entity Relationship Overview (2/3) M2M Service Provider 1 M2M Service Provider 2 Multiple M2M Servers An M2M User may subscribe to multiple M2M Service Providers that run multiple and get multiple services 27

28. LWM2M Entity Relationship Overview (3/3) M2M Service Provider 1 Multiple M2M Servers 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 28

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