Tackling fragmentation with a standard vehicle information API

Tina Jeffrey

Has it been a year already? In February 2013 QNX Software Systems became a contributing member of the W3C’s Automotive Web Platform Business Group, which is dedicated to accelerating the adoption of Web technologies in the auto industry. Though it took a while to rev up, the group is now in full gear and we’re making excellent progress towards our first goal of defining a vehicle information API for passenger vehicles.

The plan is to establish a standard API for accessing speed, RPM, tire pressure, and other vehicle data. The API will enable consistent app development across automakers and thereby reduce the fragmentation that affects in-vehicle infotainment systems. Developers will be able to use the API for apps running directly on the head unit as well as for apps running on mobile devices connected to the head unit.

Parallel processing
Let me walk you through our work to date. To get started, we examined API specifications from four member organizations: QNX, Webinos, Intel, and GENIVI. Next, we collected a superset of the attributes from each spec and categorized each attribute into one of several functional groups: vehicle information, running status, maintenance, personalization, driving safety, climate/environment, vision systems, parking, and electric vehicles. Then, we divvied up these functional groups among teams who worked in parallel: each team drafted an initial API for their allotted functional group before sharing it with the members at large.

Throughout this effort, we documented a set of API creation guidelines to capture the intent and reasoning behind our decisions. These guidelines cover details such as data representation, attribute value ranges and increments, attribute naming, and use of callback functions. The guidelines also capture the rules that govern how to grow or extend the APIs, if and when necessary.

Driving towards closure
In December the business group editors began to pull the initial contributions into a single draft proposal. This work is progressing and will culminate in a member’s face-to-face meeting mid-March in Santa Clara, California, where we will review the draft proposal in its entirety and drive this first initiative towards closure.

I’m sure there will be lots more to talk about, including next potential areas of focus for the group. If you're interested in following our progress, here’s a link to the draft API.

Enjoy!

Self-driving cars? We had ‘em back in ‘56

Quick: What involves four-part harmony singing, control towers in the middle of the desert, and a dude smoking a fat stogie? Give up? It's the world of self-driving cars, as envisioned in 1956.

No question, Google’s self-driving car has captured the public imagination. But really, the fascination is nothing new. For instance, at the 1939 World’s Fair, people thronged to see GM’s Futurama exhibit, which depicted a world of cars controlled by radio signals. GM continued to promote its autonomous vision in the 1950s with the Firebird II, a turbine-powered car that could drive itself by following an "electronic control strip" embedded in the road. Here, for example, is a GM-produced video from 1956 in which a musically adept family goes for an autonomous drive:



Fast-forward to today, when it seems that everyone is writing about self-driving cars. Most articles don’t add anything new to the discussion, but their ubiquity suggests that, as a society, we are preparing ourselves for a future in which we give up some degree of control to our vehicles. I find it fascinating that an automaker was at the avant-garde of this process as far back as the 1930s. Talk about looking (way) ahead.

And you know what’s cool? Comparing the vision of the good life captured in the above video with the vision captured in the “Imagined” video that QNX produced 56 years later. In both cases, autonomous drive forms part of the story. And in both cases, an autonomous car helps to bring family together, though in completely different ways. It seems that, no matter how much technology (and our vision of technology) changes, the things closest to our hearts never do:



One more thing. Did you notice how much the sets in the GM video look like something straight out of the Jetson’s, right down to the bubble-domed car? They did to me. Mind you, the video predates the Jetson’s by several years, so if anything, the influence was the other way around.

QNX drives home (quietly) with embedded award

Every year, the organizers of the Embedded World conference hold the embedded AWARDs to recognize the most innovative software, hardware, and tools for embedded developers. And this year, they selected QNX Acoustics for Active Noise Control, the new QNX solution for eliminating engine "boom" noise in cars, as the winner in the software category.

This marks the third time that QNX Software Systems has taken home an embedded AWARD. The company also won in 2004 for power management technology and in 2006 for its multicore tools and OS — and in 2010, it nabbed a finalist spot for its persistent publish/subscribe messaging. That's a lot of plaques.

QNX Acoustics for ANC eliminates the need
for costly dedicated ANC hardware.

So why did QNX Acoustics for ANC get the blue ribbon treatment? I can't speak on behalf of the Embedded World judges, but check out this overview I wrote a few months ago. Or better yet, read this deeper dive from my colleague Tina Jeffrey.

Or skip the middle man entirely and check out the product page, which does a nice job of summarizing what QNX Acoustics for ANC is all about.

When is a road trip not a road trip?

The über-cool modified Mercedes-Benz CLA45 AMG that QNX unveiled at CES is on its inaugural road trip. Well, sort of. It's actually winging its way to Barcelona for Mobile World Congress 2014.

For those that didn't have a chance to see it at CES, the car incorporates state-of-the-art voice recognition; navigation from Elektrobit, Here, and Kotei; smartphone connectivity based on Miracast and on MirrorLink from RealVNC; advanced multi-media streaming, including iHeartRadio; and a reconfigurable digital instrument cluster, all delivered in a user-centric, multi-modal experience.

For those that have seen it, it is still worthwhile taking the time to check it out because this time around it's powered by Qualcomm’s Snapdragon S602A Automotive Solution. We announced the relationship with Qualcomm at CES and just over a month later we're showcasing the relationship in the Mercedes. Imagine what we'll do by Telematics Detroit.

You can check it out in the Qualcomm booth, Hall 3, Mobile World Congress 2014

Now powered by Qualcomm’s Snapdragon S602A Automotive Solution: the latest QNX technology
concept car, based on a Mercedes CLA45 AMG.

Frankenstein and the future networked car

So what do Frankenstein and the future networked car have in common, you ask? Simple: both are compelling stories brought to life in Geneva, Switzerland.

In Mary Shelley’s Frankenstein the creature is seen climbing Mont-Salève after having fled Geneva during a lightning storm:

“I thought of pursuing the devil; but it would have been in vain, for another flash discovered him to me hanging among the rocks of the nearly perpendicular ascent of Mont-Salève.”

Mont-Salève, overlooking Geneva
Photo: Benoit Kornmann

Of course, the future networked car is a very different type of story, but compelling nonetheless. The laboratory in this story is the ITU Symposium on The Future Networked Car being held within the Geneva Auto Show on March 5 to 6, where many new ideas will be brought to life by convening leaders and technical experts from the automotive and ICT communities.

The event, organized by the International Telecommunications Union (ITU), will consist of high-level dialogues and several technical sessions; these include a session on integrating nomadic devices in cars, where I will discuss how technology standards can help minimize driver distraction. The dialogues will cover road safety and innovation for the future car, and will feature key leaders such as the presidents of Fédération Internationale de l’Automobile (Jean Todt) and Infiniti (Johan de Nysschen). The technical sessions will explore automated driving, connected car use cases, emergency services, and, of course, nomadic device integration. Speakers for these sessions come from a mix of automakers, tier one suppliers, ICT companies, standards development organizations (SDOs), industry groups, and government agencies.

The symposium also includes a session jointly organized by the ITU and UNECE Inland Transport Committee that deals with the human factors and regulatory issues introduced by automated driving. This session is an encouraging sign that the ITU and UNECE will continue the collaboration they started last June (see my previous post, “UN agencies take major step towards international standards for driver distraction”).

Hope to see you in Geneva!

Why I should have gone to CES this year

No problem, I said, I'll be happy to stay back at the office. After all, somebody has to hold down the fort while everyone is at CES, and it may as well be me.

Of course, I didn't know what Audi was bringing to the show. Because if I did, I wouldn't have been so willing to take one for the team. If you're wondering what I am talking about, it's the new user-programmable instrument cluster for the upcoming 2015 Audi TT. It's based on the QNX CAR Platform for Infotainment, and it's about the coolest thing I've seen in a car, ever — even if I haven't yet had a chance to see it in person.

Roll the tape...

My top 10 QNX Auto posts from 2013

Normally, people write this kind of post at the beginning or end of a calendar year. But as an old friend once said, “Paul defines his own kind of normal.” He may have been right, I don’t know. What I do know is that this is definitely a personal list. It consists of posts that either made me laugh, taught me something I didn’t know, or helped me see things in a new light. I hope they do the same for you.

Disclosure: I wrote a couple of the posts in question. Because, sometimes, the best way to learn about something or see it in a new light is to write about it. :-)

Okay, enough preliminaries, let’s get to it…

• What happens when autonomous becomes ubiquitous? — One question, seventeen answers.
   
• Top 10 lessons learned from more than a decade in automotive — When it comes to software in the car, John Wall is the man.
   
• Protecting software components in an ISO 26262 system — Sometimes, software components can be downright delinquent.
   
• Why doesn’t my navigation system understand me? — Big data might be important, but small data can add a personal touch.
   
• Top 10 challenges facing the ADAS industry — For ADAS systems to be successful, a safety culture must be embedded in every organization in the supply chain. And that’s just the first challenge.
   
• Reducing driver distraction with ICTs — Yes, mobile phones can contribute to driver distraction. But they can also help solve the problem.
   
• A sound approach to creating a quieter ride — Paradoxically, the best way to eliminate engine noise is to generate noise.
   
• What's the word on HTML5? — If you want to know what experts at Audi, OnStar, Gartner, Pandora, TCS, and QNX think about HTML5 in the car, this is the post with the most (videos, that is).
   
• A matter of context — A look at how digital instrument clusters can help provide the right information, at the right time.
   
• My top moments of 2013 — Because this reminds me of the fantastic momentum QNX is building in automotive.
   
• HTML5 blooper reel — Because laughter.
  

Oops, I guess that makes 11.