OMA 2014 Newsletter Volume 2

by OMA | Friday, August 1, 2014

OMA Quarterly

2014 Volume 2

Table of Contents

Address from the Technical Plenary Chair

The Convergence of the Telecom and Automotive Industry to Drive the Connected Car

Mark Younge Recognized for Contributions to OMA

Next OMA Meeting – Montreal

Technical Achievements

New Work Items

Elections 2Q2014

Events Calendar

New Members

 

OMA Technical Plenary Chair Address – Francesco Vadalà

Francesco Vadala

Welcome to the second quarterly newsletter of 2014. This quarter has seen the approval of new Work Items in two areas where OMA is confirming its relevancy and role.

The first area is M2M and Internet of Things. OMA has released at the end of 2013 the OMA Lightweight M2M (LWM2M) Enabler, a simple, low-cost remote management and service enablement mechanism, based on modern architectural principles and working over wireless connections. OMA has approved three new Work Items which define three new Management Object for LWM2M: one for Connectivity Management (e.g. to provision and modify connectivity parameters), one for Software Management (e.g. to configure installation options for software components and uninstall a software component when it is not needed any longer), and one for Lock and Wipe (e.g. to remotely erase the memory of a stolen device ensuring that sensitive data does not get into the wrong hands).

The second area is Network APIs and Service Exposure Framework. OMA has released over the years specifications for several “Network APIs” i.e. a programmable interface to expose capabilities of a resource residing in a network operator, enabling smart use of network resources. In addition to a long list of existing Network APIs, OMA has approved three new Work Items. First is the “OMA Template for Network API” that will specify a template for the RESTful Network API and it will be made available externally to OMA (e.g. for other Standards Organizations) for defining their own RESTful APIs. Second, the “OMA Guidelines for RESTful Network API” will specify guidelines and best practices that will be made available externally to OMA, for the development of RESTful Network API specifications.

Finally, the “OMA Service Exposure Framework” will represent a tool to ease the integration between different service environments and the access to network capabilities by external and internal service centers. Finally, I would like to highlight how OMA is continuing to explore new opportunities for future work through the “Forward Looking session”. At the June meeting, some interesting discussions have been held on topics including: “Mobile Payment, Operators and Developers”, with a presentation from Gerri Kodres, Fortumo and ADA (Application Developers Alliance) representative, about what ADA is doing about Mobile Payments and Carrier Billing; a presentation from Rajiv Dholakia, Nok Nok Labs and FIDO (Fast IDentity Online) Alliance representative, about FIDO and the future of authentication; some presentations about “Wearables” and the potential of wearable technology, in particular from Bob Bergman (Southwest Management Technology), Bryan Sullivan (AT&T) and Alan Hameed (Fujitsu).

As always, I invite you to read through this entire newsletter to keep up to date on the many activities at OMA.

Return to Table of Contents

 

The Convergence of the Telecom and Automotive Industry to Drive the Connected Car

Roger Ordman

by Roger M.H. Ordman, Dir. Product Marketing at Red Bend Software

In this tech savvy and connected world, the connected car is already the third fastest growing technological device after phones and tablets. By 2020, £380 billion – or 20% of the value of new connected vehicles – will be able to be attributed to “connected life”, according to Machina Research. It is predicted that by 2020 the scale of connected cars is to reach into the millions of units globally, with car manufacturers now agreeing that building a connected car is no longer an option. Such a car is needed not only because the consumer now expects continuous connectivity for convenience and better infotainment, but also because governments will soon require this for better safety.

Software in Cars
As the connected car becomes a reality the amount of software and Electronic Control Units (ECUs) increases within the car. According to Frost & Sullivan1 a modern premium car has more than 100 million lines of software code used in many aspects of the car from the sensors such as radar and infra-red through the core of the car’s powertrain, chassis and infotainment system. The embedded software package size is now tens of megabytes for engine and transmission controllers, while audio/infotainment systems are usually the largest and most complicated softer units, often exceeding 100MB. By 2020 the report estimated that almost 40-50 percent of the car value will be software related.

The software within the car is one of the biggest challenges car manufacturers face, they have systems that currently manage updates for the more mechanical parts in the car, but are having a hard time in understanding how they efficiently manage computer software updates in the most cost-effective and flexible way. A lot of money is spent on recalling the cars for either updates for safety reasons, regular maintenance or production line updates.

Lessons learnt from the mobile industry
The automotive industry is not the first industry to have faced this software challenge, the mobile industry also experienced the same transition when it moved from a feature phone to a smartphone and now have a proven technology for remotely updating software on mobile devices. The technology is called Firmware over-the-air (FOTA) updating. All major mobile phone and tablet manufacturers and Tier 1 operators have adopted FOTA successfully, performing hundreds of millions of updates a year with the benefits of providing new features and performance improvements, reducing customer care costs, avoiding product recalls and increasing consumer satisfaction.

How can the automotive industry adopt FOTA?
For the automotive industry to adopt FOTA successfully they need to look at the standards that already exist within the mobile industry and lessons learnt and adopt these for implementing software updates within the car. The Open Mobile Alliance Device Management Software Component Management Object (OMA-DM SCOMO) helps manage multiple software elements on a single device, which in this case would be the car. It can collect information from the car on the software that currently exists and the versions within the car, balance dependencies between software platforms and create a single download package for different software types.

The standard is de-coupled from the actual updating of the software in the car, leaving room for parts manufacturers to develop their own update technology or implement someone else’s, making this interoperable across all device-side software platforms. An example of device-side update technology that sits on the ECUs to deliver the updates is Red Bend Software’s firmware updating of small electronics (FUSE) technology, which is capable of updating over-the-air the firmware of small electronics, even the most resource-constrained ECUs, such as those found in the automotive industry.

The development of the SCOMO standard is being backed by mobile network operators such as AT&T, Docomo, Verizon, China Mobile & Sprint who have existing infrastructure in OMA DM servers from managing mobile phones to managing other devices.

There are several benefits of firmware over-the-air updates using the OMA-DM SCOMO standard. The manufacturer increases production efficiencies with reduced recalls, the dealership saves time and money as the car is already updated, the mobile operator can offer new services using existing infrastructure, and the consumer has a continuously better driving experience as the car is always updated over its 15-20 year life cycle.

The future
The automotive industry is going through the same trend that the mobile industry experienced eight years ago, where the growing amount of software and increased connectivity is forcing the industry to change the way it manages software to meet time-to-market demands, extend the vehicle’s lifecycle, enhance the driving experience and satisfy consumers. The current way of updating the software is costly, not customer friendly and not flexible enough to cope with the rapid changes that are happening within the industry.

FOTA technology is a proven, safe and cost-effective method for car manufacturers to manage the automotive software evolution, which is turning the car from piston driven to code driven. FOTA can help car manufacturers comply with regulation, save time and costs, mitigate risk and retain customers.

1Over the Air Updates – Crucial to Impacting a Key Decrease in an Expensive $1Million/Day Recall Bill for OEMs; Published: 21 Aug 2013; By Krishna Jayaraman, Industry Analyst, Frost & Sullivan-  http://www.frost.com/sublib/display-market-insight.do?id=283395035

Return to Table of Contents

Mark Younge Recognized for Contributions to OMA

youngeJune 6 at the OMA Technical Plenary in Kona, HI, Mr. Mark Younge of T-Mobile USA was awarded the Contributor and Achievement Award. Mark was recognized for his outstanding leadership in the Location Working Group. He has been leading the Location Working Group since 26th of January 2010, being a technical guide for the group and contributing many accomplishments and OMA specifications, such as Secure User Plane Location (SUPL), SUPL Configuration Services, LTE Positioning Protocol extensions (LPPe), Mobility Location Protocol (MLP), Dynamic Navigation (DynNav).

The OMA Location Working Group (OMA LOC WG) develops specifications to ensure the interoperability of Location Services and provides technical expertise and consultancy on Location Services for other working groups across OMA. The LOC WG specifications address end-to-end architectural applications and content interfaces, including privacy, security, charging, billing, and roaming for location services. OMA LOC WG coordinates with other industry organizations, including 3GPP, 3GPP2, IETF NFC and GSMA to ensure architectural conformance, security, and interoperability of specifications and to address new opportunities for collaboration across the mobile industry.

The Technical Plenary of the Open Mobile Alliance operates an Award Scheme to recognize the exceptional efforts of individuals in support of the Technical Plenary’s activities. These Awards are bestowed by the Technical Plenary Officers following a nomination by members to thank them for their outstanding work, in recognition of their commitment to OMA’s values and Mission Statement.

Return to Table of Contents

Next OMA Meeting – Montreal

The next OMA face-to-face meeting will take place August 25 to 28, 2014 in Montreal, Canada. Members will gather at the Hilton Montreal Bonaventure for four days of Working Group meetings plus Technical Plenary sessions. OMA working groups who will meet in Montreal include: Architecture (ARC), Content Delivery (CD), Communications (COM), Device Management (DM), Location (LOC), Release Planning and Management (REL), and Requirements (REQ). The COM working group will focus efforts on active work items Push-to-Communication for Public Safety (COM PCPS); Enhanced Visual Call (COM EVC); and Converged IP Messaging (COM CPM). Not only will members be meeting face-to-face during the week in these groups, but OMA will be testing a new “hybrid” style meeting set-up for select working groups that will allow members to dial-in and participate remotely. The goal of a “hybrid” set-up is to allow members who are not able to meet in person to still present documents, comment on work items and maintain active participation within the group.
OMA is also excited to announce that the meeting in August will be co-located with the Continua Health Alliance. OMA has identified mobile healthcare as an important topic in the standards industry and we look forward to welcoming Continua to Montreal to learn more about their mission for interoperable connected health solutions. OMA will be hosting a private social event on Wednesday evening, August 27, to foster the relationship between our organizations and memberships.

OMA members can access full meeting details regarding registration, hotel block, and more on the Next Event Registration page (click here).

Return to Table of Contents

Technical Achievements

During the second quarter of 2014, OMA Board of Directors has approved the documents listed below.

April 2014
Enabler and Reference Releases
Candidate Approval
Device Apps Network Efficiency V1.0 Enabler Release Package (containing Requirements Document and Architecture Document)
Management Policy MO V1.0 Enabler Release Package

Final Approval
SUPL Configuration Services V1.0 Reference Release Package
Virtualisation Management Object V1.0 Enabler Release Package

May 2014
Enabler and Reference Releases
Notification
SOAP_NetAPI_Roaming V1.0 Enabler Release Package

Enabler Test Specification, Test File Package and Enabler Validation Plan
Notification
Browsing Maintenance V2.1 XHTML Mobile Profile 1.1 Test File Package
Browsing Maintenance V2.2 XHTML Mobile Profile 1.1 Test File Package
Browsing Maintenance 2.3 XHTML Mobile Profile 1.2 Test File Package
Browsing Maintenance V2.4 XHTML Mobile Profile 1.3 Test File Package

June 2014
Enabler and Reference Releases
Candidate
REST NetAPI Roaming V1.0 Enabler Release Package (re-approval)
Authorization Framework for Network APIs V1.0 Enabler Test Specification
Authorization Framework for Network APIs V1.0 Enabler Validation Plan

Historic Status
Converged IP Messaging V1.0 Enabler Release Package

Return to Table of Contents

 

New Work Items

The following have been approved as new OMA Work Items (WID) in Q2 2014.

  • WID 0298 – Lightweight M2M Object Connectivity Management V1.0
  • WID 0299 – Lightweight M2M Object Software Management 1.0
  • WID 0300 – Lightweight M2M Object Lock and Wipe 1.0
  • WID 0302 – Template for Network API -V1.0
  • WID 0303 – OMA Guidelines for RESTful Network API-V2.0
  • WID 0304 – OMA Service Exposure Framework-V1.0

Return to Table of Contents

Elections 2Q2014

Congratulations to the follow people elected in Q2 of 2014:

  • Pierre-Henri Gross of Alcatel-Lucent on his successful election as Vicechair of the Architecture Working Group (ARC)
  • Markus Hanhisalo of Microsoft on his successful affirmation as Chair of the Interoperability Working Group (IOP)

Return to Table of Contents

Events Calendar

Upcoming Industry Events

M2M Evolution Conference & Expo
11-14 August 2014 / Las Vegas, Nevada, USA

4G World 2014
9-11 September 2014 / Las Vegas, Nevada, USA

4G-world-logo

SDN & NFV World Summit
15-17 September 2014 / Nice, France

Service Delivery Innovation Summit 2014
16-17 September 2014 / London, UK

LTE World Series: Asia
22-24 September 2014 / Singapore

PT/EXPO
23-27 September 2014 / Beijing, China

Money 2020
2-6 November 2014 2014 / Las Vegas, Nevada, USA

Apps World – Discover the Future of Multi-Platform Apps
12-13 November 2014 / London, UK

Return to Table of Contents

 

New Members

OMA would like to welcome the following companies who have joined during Q2 2014!

CompanyCompany LevelCompany URL
ARM Ltd.Fullwww.arm.com
CellebriteExplorerwww.cellebrite.com
TelularExplorerwww.telular.com
Stream Explorerwww.stream-communications.com
Mobile Tornado Group PLCExplorerwww.mobiletornado.com
County of Somerset New JerseyGovernment Agencywww.co.somerset.nj.us
Sonim TechnologiesExplorerwww.sonimtech.com

For more information on OMA membership and a complete list of OMA members, please visit http://openmobilealliance.org/membership/.

Return to Table of Contents