C3 recap: The future of the connected car

UPDATE: CE Week has uploaded audio and video of the C3 panels that Derek covers in this post. To hear what experts from companies like AT&T, BMW, Delphi, GM, and QNX see on the horizon for the connected car, visit the Connected Car Conference website — Ed.

“Automotive has always been a wellspring of technology and innovation.” Those ten words, spoken by Doug Newcomb, car technology consultant and conference chair — and occasional QNX blog contributor — brought the Connected Car Conference (C3) to a successful close. The conference, co-located with CEA’s CE Week in New York City, featured panels on issues and trends for the connected car: big data, the future of radio, driver distraction, and more.

I was honored to sit on a panel that included executives from General Motors, AT&T Emerging Devices, and Audiovox, and that tackled the question on the minds of everyone in the industry: how can cars keep pace with consumer electronics? Traditionally, the speed of car development has trailed consumer devices, but with consumers looking at their cars as another connected gadget, the industry is working to bring technology into the car faster, while still providing a safe, reliable experience. As GM’s Tim Nixon put it, “we want to make the car better from the day you drive it off the lot.”

Striking a balance
Tim’s comment touches on something we frequently discuss — the significance of over-the-air (OTA) updates in ensuring that a car always has the latest technology. In fact, my colleague, Tina Jeffrey, just wrote a blog post on the topic; it's worth a read. Another point that came up is the need to balance security with consumers’ desire for cutting-edge technology. As I pointed out, not all infotainment systems are created equal — security shouldn’t be an afterthought in the pursuit of the latest and greatest tech. Rather, it should be deeply engrained in each step of the software development process. At the same time, consumer choice also has to be balanced with what OEMs are comfortable with.

Driving big data

John Quain of the New York Times hosted a panel on big data, which was full of insights on how data is being used to connect drivers and their cars. In response to the question, “how can big data in automotive save lives?” Delphi’s Doug Welk commented that, while data on crashes was abundant and readily available, data on near misses — which is even more important to understanding how to prevent accidents — is scant. Telenav’s Niall Berkey pointed out something that my colleague Andrew Poliak often discusses: the importance of the car as a sensor. For instance, by using information on how a driver is behaving, a car could activate assisted-driving technologies to reduce the likelihood of an accident.

Dealing with distraction
During the “Dealing with Driver Distraction” panel, representatives from the Auto Alliance of Automobile Manufacturers, Nuance, NVIDIA, and Pioneer spoke on how the industry is working to curb distraction. Gloria Bergquist of the Auto Alliance stated that the concern is nothing new; when car radios were first introduced in the middle of the last century, industry watchers claimed that drivers’ attention would be diverted by the novelty.

Gloria also drew from her organization’s recent report, which showed that most drivers overestimate how well they can handle distractions and think that it’s other drivers who can’t cope. Erik Clauson of Nuance discussed how voice recognition technologies — like the QNX intent framework — can play a large role in decreasing the cognitive load of drivers. Dave Anderson of NVIDIA defended skeumorphism — a design aesthetic that has received much criticism as of late — as a way to increase the intuitiveness of user interfaces and therefore decrease distraction. For example, digital instrument clusters that look like conventional (and familiar) analog instruments can enhance the driving experience.

Continuing the conversation
The day ended with a networking reception — a unique opportunity to pick the brains of the some of the industry’s thought leaders and observers. While I got to spend only a short time in New York for the event, I am look forward to next year when we can continue this conversation on the industry’s challenges and innovations.

UN agencies take major step towards international standards for driver distraction

June 27 marked a historic event in Geneva, Switzerland — an event that could ultimately lead to internationally harmonized vehicle regulations and Information and Communications Technology (ICT) standards to address driver distraction.

The event was a workshop titled "Intelligent transport systems in emerging markets — drivers for safe and sustainable growth". The title may sound innocuous, but don’t let that fool you. It only touches the surface of what was really going on.

So what, exactly, made this event so important? It was the first joint meeting of the United Nations (UN) agencies that deal with automotive regulations and ICT standards/radio spectrum allocation: the UNECE World Forum for Harmonization of Vehicle Regulations (UNECE WP.29) and the International Telecommunications Union (ITU), respectively. During the opening of the workshop, Eva Molnar (director, UNECE Transport Division) and Malcolm Johnson (director, ITU Telecommunication Standardization Bureau) spoke about the historic significance of this event and how they hoped it would be the beginning of a close collaboration.

This is big news. The possibility of vehicle regulations by the UNECE WP.29 may force automakers to work with the ITU, which has been working to develop comprehensive, internationally agreed standards to address driver distraction caused by mobile devices and other ICTs. Previous attempts such as the ITU-T Focus Group on Driver Distraction (FG Distraction) have had only limited success at engaging the automotive industry. See the FG Distraction reports for more information on the current state of such comprehensive standards.

Not if, but when
Regulation of ICTs could also occur. Strictly speaking, ITU-T Recommendations are non-binding, but they can become mandatory if referenced in a regulation by a national authority such as the FCC in the US. Increasing pressure to regulate use of ICTs in vehicles and the likely harmonization of ITU-T Recommendations with UNECE WP.29 vehicle regulations make regulations based on ITU-T Recommendations a real possibility.

Regulation of automotive and ICT equipment used by drivers isn’t a question of "if", but of "when". That said, many paths could lead to such regulation, some better than others. For example, authorities could jump the gun and issue regulations before good solutions are in place — and actually make the situation worse. With that in mind, let's hope that the step taken on June 27 is the first of many down a path that leads us to internationally harmonized standards and regulations that truly address unsafe driver interaction with ICTs.

Reducing driver distraction With ICTs

Inappropriate use of information and communication technologies (ICTs), especially mobile phones, is a chief culprit behind driver distraction and road accidents, and with automobile manufacturers scrambling to develop a “connected” driving experience, the ICT and automotive industries are becoming ever more closely entwined.

However, this integration of cars and ICTs need not come at the expense of driver safety, and there are strong grounds on which to argue that ICTs have great potential to enhance rather than diminish vehicle safety systems.

Under the banner of intelligent transport systems (ITS) the automotive and ICT communities are working towards a convergence of automobiles and ICTs that prioritizes drivers’ safety and broad consensus has it that international standards are the tools through which this will be achieved.

Over the past two years, as chairman of the ,I have had the pleasure of leading a group tasked with laying the foundations for driver-distraction standardization work in ITU’s Telecommunication Standardization Sector (ITU-T).

Established in February 2011, the Focus Group reached the end of its study period in March 2013 and has been instrumental in raising awareness around ITU-T activity on driver distraction and the scale of this workload, as well as in providing clear direction to ITU-T’s driver-distraction work plan. The group has also been successful in opening lines of communication with key organizations and drawing new expertise into the ITU-T standardization process.

The Focus Group’s final deliverables take the form of five technical reports that describe:

• use cases and user interface requirements for automotive applications 
• system capabilities for improving the safety of driver interaction with applications and services (situational awareness management) 
• approaches that enable external applications to communicate with a vehicle

The reports are freely available .

The conclusions put forward by the reports are being taken up by the two groups leading ITU-T’s standardization work on driver distraction,  (Performance, QoS and QoE) and  (Multimedia). New related work items calling for external coordination and collaboration may also be addressed by the , a forum working to create an internationally harmonized set of ITS communication standards to enable the deployment of fully interoperable ITS products and services in the global marketplace.

Safe interaction with applications and services
The Focus Group’s work is just the beginning of an international standards effort to help drivers interact safely with applications and services — and not just apps on phones, but apps running in the cloud, in roadside infrastructure systems, and in the car itself, to name just a few locations.

The Focus Group’s  details the use cases and user scenarios being targeted by this standards effort, but for now let’s look at Use Case 2, Scenario A (arbitration of external message), which illustrates how ITU-T is working towards a comprehensive framework for managing distraction and workload.

Keeping priorities straight
In this user scenario, a navigation maneuver is given priority over a social media ‘status update’ message. The blue call-out boxes indicate where the ITU-T Recommendations under development can enable safe interaction between the driver and applications. For instance, ITU-T Recommendation G.SAM will define mechanisms for prioritizing navigation, G.V2A will define the communications interface between the app and the driver-vehicle interface (DVI), and P.UIA will recommend characteristics of the auditory social media message.

Remember that the focus here is not on how to implement social media in the car, but rather on how best to manage workload and distraction.



Giving a navigation maneuver priority over a social media status update message

In for the long haul
Speaking from our perspective at QNX Software Systems, a subsidiary of BlackBerry, the work of the Focus Group marks the beginning of a long road ahead. Within ITU-T, QNX will continue to:

1. Work with the relevant parties to identify solutions to the problem of technology-related driver distraction and workload. These parties include automotive, telecommunications, and consumer electronics organizations; standards development groups; academia; and government agencies.
2. Determine which aspects of the solution should be standardized, and help drive this standardization.
3. Align QNX product roadmaps as solutions develop.

Certainly this is a long-term strategy that will take years to realize, factoring in the rigour of ITU-T’s standards process as well as the significant amount of time needed to deploy technologies in vehicles on a meaningful scale.

Join the discussion
A workshop hosted by ITU and  at ITU headquarters in Geneva, 27 June 2013, will address  with a view to analyzing recent advances in ITS with emphasis on improving road safety in developing countries.

This workshop includes a session dedicated to driver distraction in which I will present the outcomes outlined by the Focus Group’s technical reports to spur discussion on the likely course of corresponding ITU-T standardization work.

The workshop is free of charge and open to all interested parties, including non-members of ITU, and online ‘remote participation’ will be available to all those unable to travel to Geneva. Please join us for what will certainly be a richly informative and interactive event!

OTA software: not just building castles in the air

After attending Telematics Detroit earlier this month, I realized more than ever that M2M will become the key competitive differentiator for automakers. With M2M, automakers can stay connected with their vehicles and perhaps more importantly, vehicle owners, long after the cars have been driven off dealer lots. Over-the-air (OTA) technology provides true connectivity between automakers and their vehicles, making it possible to upgrade multiple systems, including electronic control unit (ECU) software, infotainment systems that provide navigation and smartphone connectivity, and an ever-increasing number of apps and services.

Taken together, the various systems in a vehicle contain up to 100 million lines of code — which makes the 6.5 million lines of code in the Boeing 787 Dreamliner seem like a drop in the proverbial bucket. Software in cars will only continue to grow in both amount and complexity, and the model automakers currently use to maintain and upgrade vehicle software isn’t scalable.

Vehicle owners want to keep current with apps, services, and vehicle system upgrades, without always having to visit the dealer. Already, vehicle owners update many infotainment applications by accepting software pushed over the air, just like they update applications on their smartphones. But this isn’t currently the case for ECUs, which require either a complete module replacement or module re-flashing at a dealership.

Pushing for updates
Automakers know that updates must be delivered to vehicle owners in a secure, seamless, and transparent fashion, similar to how OTA updates are delivered to mobile phones. Vehicle software updates must be even more reliable given they are much more critical.


BlackBerry’s OTA solution: Software Update Management for Automotive service

With OTA technology, automakers will use wireless networks to push software updates to vehicles automatically. The OTA service will need to notify end-users of updates as they become available and allow the users to schedule the upgrade process at a convenient time. Large software updates that may take a while to download and install could be scheduled to run overnight while the car is parked in the garage, making use of the home Wi-Fi connection. Smaller size updates could be delivered over a cellular connection through a tethered smartphone, while on a road trip. In this latter scenario, an update could be interrupted, for instance, if the car travels into a tunnel or beyond the network area.

A win-win-win
Deployment of OTA software updates is a winning proposition for automakers, dealers, and vehicle owners. Automakers could manage the OTA software updates themselves, or extend the capability to their dealer networks. Either way, drivers will benefit from the convenience of up-to-date software loads, content, and apps with less frequent trips to the dealer. Dealership appointments would be limited to mechanical work, and could be scheduled automatically according to the vehicle’s diagnostic state, which could be transmitted over the air, routinely, to the dealer. With this sharing of diagnostic data, vehicle owners would better know how much they need to shell out for repairs in advance of the appointment, with less chance of a shocking repair-cost phone call.

OTA technology also provides vehicle owners and automakers with the ability to personalize the vehicle. Automaker-pushed content can be carefully controlled to target the driver’s needs, reflect the automaker's brand, and avoid distraction — rather than the unrestricted open content found on the internet, which could be unsafe for consumption while driving. Overall, OTA software updates will help automakers maintain the customers they care about, engender brand loyalty, and provide the best possible customer experience.

Poised to lead
Thinking back to Telematics Detroit, if the number of demos my BlackBerry colleagues gave of their Software Update Management for Automotive service is any indication, OTA will transform the auto industry. According to a study from Gartner ( “U.S. Consumer Vehicle ICT Study: Web-Based Features Continue to Rise” by Thilo Koslowski), 40 percent of all U.S. vehicle owners either “definitely want to get” or at least are “likely to get” the ability for wireless software updates in their next new vehicle — making it the third most demanded automotive-centric Web application and function.

BlackBerry is poised to lead in this space, given their expertise in infrastructure, security, software management, and close ties to automotive. They were leaders in building an OTA solution for the smartphone market, and now again are among the first entrants in enabling a solution that is network, hardware, firmware, OS, software, and application agnostic.

Telematics Detroit 2013: The recap

The Telematics Detroit conference always provides a great opportunity to take the pulse of the automotive connectivity market and understand what key players in the industry are doing — and are planning to do in the next couple of years.

Prior to the show, I had the opportunity to participate in an executive roundtable session hosted by Ernst and Young. The focus was the future of mobile integration and how it will change the market as we know it. The roundtable brought together views from the entire ecosystem, including OEMs, tier one suppliers, software and service providers, dealerships, and, ultimately, the end consumer. It was a great session with a lot of interaction.

Telematics Detroit, Day 1

The Bentley attracted lots of traffic

Okay, let’s go through the event checklist:

• QNX technology concept car based on a Bentley Continental and outfitted with our latest instrument cluster and infotainment concepts. Check.
   
• QNX reference vehicle based on a Jeep Wrangler, rocking a new Qt-based HMI on the QNX CAR Platform for Infotainment. Check.
   
• How about a functional over-the-air software update demo from our colleagues at Blackberry to blow people away? OK, got that, too.
   
• And let’s not forget a demo showcasing the latest in fast boot technology and Android app integration for the QNX CAR Platform. Check, and ready to go.

Inside the Jeep: a new Qt-based HMI

Now we’re set for the show. Day 1 opened with a keynote address on “Winning the Telematics Race”, presented by Thilo Koslowski of Gartner; it set the stage what for turned out to be a great show. Our booth was busy pretty much the entire day — but look at the list above… of course, it was busy! :-)

In addition to great booth traffic, I had the opportunity to participate on a panel on autonomous vehicles and the challenges they present — the discussion was very engaging and it did in fact “drive” traffic to our booth for further discussion. Meanwhile, my colleague Andrew Poliak presented a keynote on HMI trends. To my mind, his talk clearly demonstrated that we are thought leaders in this industry.

The evening brought the annual Telematics and Tonics mixer, co-hosted by QNX and several of its partners: AT&T, NVIDIA, Pandora, Tweddle, and Elektrobit. It was a huge success with well over 300 attendees — standing room only, all night. There were great discussions with great people until the wee hours of the night… really wee hours.

Telematics Detroit, Day 2Day 2 was busy, busy, busy. Did I mention it was busy? We provided demos galore to OEMs, tier ones, partners — the works. Andy Gryc sat on a panel discussing the ultimate intuitive user interface and knocked it out of the park, as he always does.

The booth was busy until the show closed. We then we put the cars to bed in their shipping truck and headed off to the airport, tired but extremely happy nonetheless.

Jivin' up the Jeep with a fresh new version of the QNX CAR Platform

by Paul Leroux

Reskinnable, reconfigurable,
and refreshed

If you haven’t already heard, we've announced version 2.1 of the QNX CAR Platform for Infotainment. In fact, we’re demonstrating it this week at the Telematics Detroit conference.

So what’s new in 2.1? Well, let’s start with what hasn’t changed. The platform is still based on the same, reliable QNX architecture proven in tens of millions of vehicles. (Fact: In 2012, QNX technology shipped in 11 million cars. If you put those cars end to end, they’d circle the earth — and you’d still have about 6000 miles of cars left over. That's a lot of cars.) The platform also retains its inherent flexibility, allowing infotainment system designers to use multiple app environments, connect to multiple mobile platforms, and create a wide range of systems.

Um... let me correct that statement. The new version is, in fact, more flexible. From the beginning, the QNX CAR Platform has supported both HTML5 and OpenGL ES, the two most popular open standards for mobile development. And now, with version 2.1, it also supports Android apps, as well as apps and human machine interfaces (HMIs) built with the popular Qt 5 application framework.

The QNX reference vehicle — a modded Jeep Wrangler — is the perfect, well, vehicle for showcasing these new capabilities. Take, for example, the new digital instrument cluster, which is implemented in OpenGL ES:



I enjoyed the look of the reference vehicle’s original cluster, and still do. But you know what I like about the new version? It shows how a digital cluster can deliver state-of-the-art features, yet still honor the look-and-feel of an established brand like Jeep. These features include dynamic reconfigurability and the power to display turn-by-turn directions, weather updates, and other information provided by the head unit.

Speaking of which, here is the head unit’s main screen, which serves as a one-stop information center for turn-by-turn directions, weather, music, and recent messages:



Now let’s slide over to the passenger seat for a different perspective. If you look below, you’ll see the head unit’s app tray, which shows how the QNX CAR Platform can blend a variety of apps and HMI technologies on the same display — in this case, native and Android apps running on an HMI built with the Qt 5 application framework. In case you’re wondering, the Android app icons in this image are AutoTrader and TapTu. (That's right, they can be accessed just like other apps.)



If you’ve seen images of the QNX technology concept car (you know, the Bentley!), you’re already familiar with the gorgeous 3D navigation system created by our partner Elektrobit. Well, the reference vehicle also comes with a version of Elektrobit’s nav system, seen here:



And last, here’s an image of my personal favorite, the virtual mechanic. In this case, it's displaying trip information, including duration, mileage, and average speed:



There's a lot to see in version 2.1 of the QNX CAR Platform for Infotainment, but there's also a lot you can't see — such as improved power management, optimizations for faster boot time, and support for more hardware platforms, including Freescale i.MX 6Dual and i.MX 6Quad, NVIDIA Tegra 3, Texas Instruments OMAP 5, and Texas Instruments Jacinto 5 Eco.

What's more, I haven't shown you any of the new, pre-integrated partner apps that have been added to the platform, including HearPlanet, Parkopedia, Soundtracker, and wcities eventseekr. But no worries, I plan to reveal more in coming posts.

In the meantime, I invite you to check out the press release we issued this morning.

BlackBerry demonstrates new mobile computing service for automakers

This just in: BlackBerry has announced a new service for  automakers that will let them manage and deliver “over-the-air” (OTA) software updates to vehicles. Leveraging BlackBerry’s global and secure infrastructure, which already  delivers software updates to millions of BlackBerry devices around the world, the Software Update Management for Automotive service facilitates machine-to-machine (M2M) communication between the automaker and the vehicle, allowing the automaker to easily provide software updates to vehicles in the field.

BlackBerry is previewing the new service this week at the Telematics Detroit conference, where QNX Software Systems is also demonstrating the latest version of its QNX CAR Platform for Infotainment (more on that in my next post).

“BlackBerry is helping facilitate a rapid convergence between mobile computing and the auto industry as automakers seek to connect with customers wherever they may be,” said David J. Smith, Executive Vice President, Enterprise Mobile Computing at BlackBerry. “At Telematics Detroit we are previewing how BlackBerry can help automakers connect with customers... BlackBerry’s Software Update Management for Automotive service can transform the vehicle experience by enabling automakers to deliver new, compelling capabilities to their customers, long after the initial sale.”

More details about the BlackBerry's OTA solutions will made available in the coming months. In the meantime, check out the press release and visit www.blackberry.com/m2m.

Behind the scenes at the QNX concept garage

It seems like every technology concept car QNX produces is bigger and better than the last one, which is just how we like it. That also means each year countless hours are spent dreaming up and implementing ideas. Luckily for us, we’ve got an absolutely amazing concept design team who go above and beyond to create these demos. Luckily for them, the team’s got a cool garage to work in.

Here’s a behind-the-scenes look at where the magic happens.


The garage can be a serene place after a milestone is reached. In this photo, the Jeep and Bentley await transport to the Telematics Detroit conference.


Mike Shane only looks like he’s trying to break into the car. In reality, he’s shining some light on the latest challenge to roll into the garage.


Tyler Elliott works on the remote monitoring demo portion of the Bentley, making sure the windows and locks behave as planned not only in the garage but also on the show floor.


Like most of his colleagues, Alexandre James splits his time in the garage between the computer and the vehicles. Here he helps test the Bentley’s stereo audio capabilities.


The open concept of the garage makes it easy to share challenges and draw upon everyone's expertise. Here Justin Moon, a former member of the concept team, talks with colleagues about the DLP.

True Nguyen, a UX designer “borrowed” from the engineering team to work on the Jeep and Bentley UIs, fits right in with the garage regulars.


James Henderson from Design First moves in and out of the garage as needed. Here he is deep in thought as he works on the new dash that will eventually house the large display.


The garage has a small alcove with couches and whiteboards away from the vehicles; the guys from Crank Software make good use of the space to check in their code.


Mark Rigley, the team’s fearless and passionate leader, toasts everyone’s hard work before each technology concept car makes its maiden voyage out of the garage.


Who says real men don’t drink rosé? After countless hours in the garage, a celebration is always a welcome break.


Another end-of-project tradition – team photo with the concept car.

Chevy MyLink drives home with CTIA Emerging Technology Award

by Paul Leroux

There's nothing better than going home with first prize. Except, perhaps, doing it twice. Back in January, the QNX-based Chevy MyLink system earned a Best of CES 2013 Award, in the car tech category, for its intuitive user experience, smartphone connectivity, and instrument-cluster integration. And just recently, MyLink pulled another coup: it took first place in the "Automotive, LBS, Navigation & Safe Driving" category of the 2013 CTIA Emerging Technology (E-Tech) Awards.

If you're new to the E-Tech Awards, they honor innovation in wireless products and services. A panel of industry experts, reporters, and analysts conduct the online judging, which selects winners based on functionality, technological importance, and overall “wow” factor.

Congratulations to our friends at Chevrolet! And kudos for bringing such a successful system to market.

For more information on the awards, read the blog post from CTIA. For more information on Chevy MyLink, visit the Chevrolet channel on YouTube.

Image source: Chevrolet

HTML5 blooper reel

I find bloopers infinitely amusing — mind you I’m talking about those that come on a reel, not those that happen for real. Missed deadlines, cost over-runs, IP disputes — these are the bloopers we all could do without.

Helping customers avoid bloopers is what we do — so to speak. Except it seems, when we put them in front of the camera. <grin>

Seriously though, no customers were hurt in the making of this video.



This compilation of bloopers from the HTML5 series highlights the professionalism of QNX customers, partners, and employees as well as their good nature.

 

#QNXLive Twitter Sessions Return!

Ask us your questions about self-driving cars and the secrets of the QNX Garage

Paul Leroux

We’re back for more of your questions. Back in December, we held our first #QNXLive Twitter sessions leading up to CES 2013; next week, we’re revving up for Telematics Detroit (June 5-6) with not one, but two #QNXLive sessions with experts from the QNX auto team.

Autonomous cars continue to captivate the popular imagination and are quickly becoming a reality. On Tuesday, May 28 at 4pm ET, Justin Moon, global technical evangelist,will give a preview of his Telematics Detroit panel, “The Autonomous Car: The Road to Driverless Driving” in his first #QNXLive session. Justin will share his thoughts on the latest developments in autonomous and assisted driving, how the industry defines “autonomous”, how your car is already autonomous in certain respects, and how self-driving cars will change your driving experience.

On Thursday, May 30 at 1pm ET, Alex James, concept development team software engineer, will take you Behind the scenes at the QNX Garage in his #QNXLive session. Have you ever wondered what a day looks like in the QNX garage for the concept design team? What does the team enjoy most about working in the garage? Alex will give you a behind-the-scenes look at the birthplace of the QNX technology concept car based on a Bentley Continental GT and the reference vehicle based on a Jeep Wrangler Sahara — both will be at Telematics Detroit.

You can submit your questions now or on the day of the Twitter sessions by tweeting @QNX_Auto with the hashtag #QNXLive. As usual, we’ll be sure to call you out if you asked a question that we selected.

Be sure to follow @QNX_Auto for next week’s live Twitter sessions – and the latest from Telematics Detroit. I’m looking forward to being your host for #QNXLive.

In the meantime, check out our recent posts on autonomous cars and the following videos:

Meet Justin Moon, product manager turned concept designer (Justin is nothing if not versatile: he's since taken on the role of global technical evangelist.)

Meet the QNX concept team: Alex James, software engineer

QNX technology concept car - Bentley Continental

Cisco study: people want a safer, more personalized driving experience

And they're willing to give up some of their privacy to get it.

Paul Leroux

Call me old-fashioned, but my hackles go up every time a web site or business asks me for personal information. My reaction is at once emotional and rational. Emotional because I'm a private person by nature; sharing details about myself simply goes against the grain. Rational because I know that people want this information more for their own benefit than for mine.

Does that mean I never share personal information? Of course not. Even if someone wants it primarily for their benefit, I may still enjoy some benefit in return. That said, I weigh the pro's and con's carefully. And I ask questions. For instance, who will have access to the information? And what will they do with it?

In effect, personal information becomes a form of tender — something I barter in exchange for a perceived benefit. And it seems I'm not alone.

Recently, Cisco published the results of a study on what car drivers would be willing to give up in exchange for a variety of benefits. For instance, 60% would provide DNA samples or other biometric information in return for personalized security or car security. And a whopping 74% would let their driving habits be monitored in return for lower insurance or service maintenance costs. Cisco sums it up in this infographic:


In autonomous we trust
The study also found that people are willing to embrace autonomous cars — but the enthusiasm varies significantly by geography. For instance, Canada trails the U.S. by 8 percentage points, but both countries are miles behind India or Brazil.


The study surveyed more than 1,500 consumers across 10 countries. That's only about 150 people per country, so I wouldn't put too much credence into this geographic breakdown. That said, the differences are dramatic enough to suggest that self-driving cars will see faster adoption in some countries than others.

For more on these and other findings, visit the Cisco website.

The great autonomous car debate

Paul Leroux

When it comes to cars that drive themselves, are you for or against? Either way, you're bound to find fodder for your arguments in Six reasons to love, or loathe, autonomous cars, a recent CNET article co-authored by Wayne Cunningham and Antuan Goodwin.

Wayne is for, Antuan is against, and they both score good points. For instance, Wayne argues that autonomous cars will reduce accidents and help the elderly remain mobile. Antuan, meanwhile, warns of the potential for reduced privacy and the likelihood that driving will become less random — that last point may not sound like a drawback, but I found myself nodding in agreement.

Actually, I found myself agreeing with both writers on several points. Does that make me a fence-sitter or just someone with a balanced perspective? Read the article and tell me what you think.

Specs for Cars?

Tina Jeffrey

As Google Glass, the latest in experimental computer wearables, starts to make its way into the hands of select users, a multitude of use cases is popping up. For instance, a WIRED article recently explored the notion of your car being a ‘killer app’ for Google Glass. Now, you may not want to think of your car as a killer app, but let’s contemplate this use case for a moment.

Drivers wearing Glass could pair their new specs to their phone and instantly have a personal heads-up display (HUD) that overlays virtual road signs and GPS information over the scene in front of them. For instance:


Source: Google

Glass also understands voice commands and could dictate an email, display turn by turn directions, or set up and display point-of-interest destination data based on a simple voice command such as “Find the nearest Starbucks”.

This is all very cool — but does it bring anything new to the driving experience that isn’t already available? Not really. Car makers have already deployed voice-enabled systems to interface with navigation and location-based services; these services either run locally or are accessed through a brought-in mobile device and displayed on the head unit in a safe manner. ADAS algorithms, meanwhile, perform real-time traffic sign detection and recognition to display speed limits on the vehicle’s HUD. All this technology exists today and works quite well.

Catch me if you can
Another aspect to consider is the regulatory uncertainty created by drivers wearing these types of devices. Police can spot a driver with their head down texting on a cellphone or watching a movie on a DVD player. But detecting a driver performing these same activities while wearing a head-mounted display — not so easy. There’s no way of knowing whether the activities a driver is engaged in are driving related or an outright distraction. Unlike an HUD specified by the automaker, which is designed to coordinate and synchronize displayed data based on vehicle conditions and an assessment of cognitive load, a head-mounted display like Glass could give a driver free reign to engage in any activity at any time. This flies in the face of driver distraction guidelines being promulgated by government agencies.

Don’t get me wrong. Glass is cool technology, and I see viable applications for it. For instance, as an alternative to helmet cams when filming a first-person perspective of a ski run down a mountain, or in taking augmented reality gaming to the next level. (You can see many other applications on the Glass site.) But Glass is a personal display that operates as an extension of your cellphone, not as a replacement for a car’s HUD. Cars need well-integrated, useable systems that can safely enhance the driving experience. Because of this, I don’t believe that devices like Glass, as they are currently conceived, will garner a spot in our cars.

QNX, Renesas to integrate R-Car SoCs and QNX CAR platform

Paul Leroux

This just in: QNX and Renesas today announced that they are integrating support for Renesas R-Car SoCs into the QNX CAR application platform. The companies also announced that QNX is joining the Renesas R-Car consortium, a partner program designed to help drive rapid development of next-generation in-car systems.

Renesas designed its R-Car SoCs to power a variety of high-end navigation and infotainment systems. The SoCs integrate a 3D graphics processor, an audio processing DSP, and image recognition processing IPs, as well as support for CAN, MOST, USB, Ethernet, SD Card, and other interfaces.

As part of their collaboration, QNX and Renesas intend to include support for the recently announced R-Car H2 Soc. According to Renesas, the H2 is now the world's highest-performance SoC for car information systems, with a Dhrystone benchmark of over 25000 DMIPS.

For more information, read the press release.

UPDATE: My colleague Kosuke, who writes for the QNX Japan blog, has just sent some photos from the Embedded Systems Expo in Tokyo, where Renesas unveiled the first demonstration of the QNX CAR platform on an R-Car M1A processor.

Here is a shot of the demo:



And here's a closeup of the BOCK-W board that hosts the M1A processor:

Experience the MLOVE!

Justin Moon

The Monterey Peninsula is arguably one of the most inspiring backdrops for a conference on the planet. I couldn’t think of a better place to hold this year’s MLOVE Confestival USA. MLOVE brings together thought leaders, business innovators, and forward thinking engineers in the mobile space for three days of inspirational talks and thought-provoking workshops. The goal of the conference is quite simply to inspire attendees and spark innovation. This year the QNX team pulled out all the stops — not only did we have a speaking slot but the QNX technology concept car (a specially modified Bentley) was front and center throughout the entire conference.

Day 1
MLOVE was the first outdoor public demonstration of the Bentley, so Mark Rigley and I started the day by putting the car through its paces. Connectivity? Check. Screens visible in the sunlight? Got it. Input, voice, touch, media? All good! In the afternoon we demonstrated the Bentley to delegates from a wide range of mobile companies. Kudos to our talented concept development team for flawless execution.

The evening’s festivities were in the key of inspiration. A very engaging talk by Maurice Conti of Autodesk on future trends was the opening salvo. Steve Brown, producer and director at Spark Pictures, introduced a feature film that showcases passion and empowerment during the Burning Man Festival.

Inside the Bentley

Day 2
The second day was jam-packed with presentations, an open space interactive ideation session, and even a startup competition. The focus of the day’s presentations included the internet of things, wearable computing, artificial intelligence, and transformational media. Highlights included discussions not just on the digitization and connectivity of things, but on the over-arching experience contained within the idea. We also learned what space startup Nanosatisfi is doing with lightweight, inexpensive satellites (CubeSats) that users can rent for experiments. Talk about the Internet of Things! Each break in the action saw the Bentley come back into focus with engaging conversations as well as demonstrations.

Day 3
Connected Vehicle day! Day 3 saw a very passionate set of presentations focusing on connected vehicles and how we will interact with them. Topics included direct interaction (the fusion of mobile and automotive technology), inter-vehicle communication, and interaction with city infrastructure. I had the opportunity (and the pleasure) to deliver a talk around reshaping the mobile and automotive user experience. The exclamation point to my presentation was the seamless interaction between my mobile device and the Bentley, which was just outside the conference area. Not only did I speak about the possibilities, I demonstrated them.

Moving the needle
MLOVE is about innovative people coming together to discuss future trends in mobility, to figure out what needs to be done to move the needle, and generally to be inspired by the experience. Ideation was abundant and minds were blown. Thank you MLOVE — now I have so much more to think about! In all seriousness, great conference, great ideas, great people, a great experience.

Report from Barcelona: first meeting of the W3C automotive business group

Last week, I had the privilege of attending the first face-to-face meeting of the W3C automotive business group and the honor of being nominated group co-chair. (The other co-chair is Adam Abramski, an open source project manager for Intel.) With more than 70 members, the group has already become the eight-largest group in the W3C, even though it is barely two months old. Clearly, it’s generating a lot of interest.

The meeting included three presentations and two contributions. I presented on the lessons we’ve learned with the QNX CAR platform, how we think the market is changing, and how these changes should drive HTML5 standardization efforts.

I presented my three “musts” for standardizing HTML5 in the car:

1. Must create something designed to run apps, not HMIs (unless HMIs come along for free)
2. Must focus on mobile developers as the target development audience
3. Must support integration of HTML5 environments with native environments like EB Guide and Qt

I described some of the changes that have resulted from the alignment of the QNX CAR platform with the Apache Cordova framework, and why they are crucial to our HTML5 work. Unfortunately, we didn't have our W3C contribution ready due to these changes, but members generally agreed that having a standard consistent with mobile development was an appropriate course change.

Tizen and GenIVI gave presentations about their vehicle APIs. Tizen has contributed its APIs, but GenIVI hasn't yet — still waiting on final approvals. Webinos contributed its APIs before the meeting, but didn’t deliver a presentation on its contribution; members had reviewed the Webinos work before the meeting.

The meeting was a great chance to sit down with people I don’t normally meet. Overall, the group is moving in the right direction, creating a standard that can help automakers bring the goodness of HTML5 into the car.

Autonomous, not driverless

Paul Leroux

I don't know about you, but I'm looking forward to the era of self-driving cars. After all, why spend countless hours negotiating rush-hour traffic when the car could do all the work? Just think of all the things you could do instead: read a novel, Facebook with friends, or even watch Babylon 5 re-runs.

Unlike Babylon 5, this scenario is no longer a page out of science fiction. It’s coming soon, faster than many imagine. That said, the story of the self-driving car still has a few unfinished chapters — chapters in which the human driver still has an important role to play. Yes, that means you.

As I’ve discussed in previous posts, the fully autonomous car is a work in progress. In fact, some of the technologies that will enable cars to drive themselves (adaptive cruise control, forward collision avoidance, etc.) are already in place. Moreover, research suggests that these technologies can, among other things, improve traffic flow and reduce accidents. But does that mean you will soon be able to sit back, close your eyes, and let the car do everything? Not quite.

Evolution, not revolution
If you ask me, Thilo Koslowski of Gartner hit the bull's eye when he said that self-driving cars will go through three evolutionary phases: from automated to autonomous to unmanned. Until we reach the endpoint, we should pay heed to the words of Toyota's Jim Pisz: autonomous does not mean driverless.

If planes can do it…

Some folks hear this and are disappointed. They point to auto-pilot technology in planes and ask why we can’t have driverless cars sooner than later. The argument goes something like this: "It's much harder to fly a plane, yet we have no problem with a computer handling such a complex task. So why not let a computer drive your car?”

If only life were so simple. For one thing, automakers will have to make autonomous cars affordable — doable but not easy. They’ll also have to negotiate a variety of legal hurdles. And in any case, driving and flying have less in common than you might think.

When you drive, you must remain alert on a continuous basis. Lose your attention for a second, and you stand a good chance of hitting something or somebody. The same doesn't always hold true in flight. When a plane is cruising at 30,000 feet along a proscribed flight path, the pilot can avert his or her attention for 5 seconds and incur little chance of hitting anything. In comparison, a driver who becomes distracted for 5 seconds is hell on wheels.

And, of course, auto-pilot doesn’t mean pilot-less. As Ricky Hudi of Audi points out, pilots may rely on autopilot, but they still retain full responsibility for flying the plane. So just because your car is on auto-pilot doesn’t mean you can watch YouTube on your tablet. Bummer, I know.

An alarming solution

Source: Modern Mechanix blog (and yes, that should 
read Frankfurt)

All of which to say, the driver of an autonomous car will have to remain alert most or all of the time — until, of course, autonomous vehicles become better than humans at handling every potential scenario. Now that could happen, but it will take a while.

It seems that someone anticipated this problem in the early 50s when they invented “alarming glasses” — take a gander at the accompanying photo from the August 1951 issue of Modern Mechanix.

Scoff if you will, but a kinder and gentler form of this technology is exactly what autonomous cars need. No, I'm not suggesting that scientists find a better way to glue wires to eyelids. But I am saying that, until cars become fully and safely autonomous, drivers will need to pay attention — after all, it’s tempting to drift off when the car is doing all the work. And, indeed, technologies to keep drivers alert are already being developed.

Pre-warned means prepared
Mind you, it isn’t enough to keep the driver alert; the car may also need to issue “pre-warnings” for when the driver needs to take over. For instance, let’s say driving conditions become too challenging for the car’s autonomous mode to handle — these could heavy rain, a street filled with pedestrians, or an area where lane markers are obscured by snow. In that case, the car can’t wait until it can no longer drive itself before alerting the driver, for the simple reason that the driver may simply take too long to assess the situation. The car will need to provide ample warning ahead of time.

The more, the better
That cars will become autonomous is inevitable. In fact, the more autonomous, the better, as far I'm concerned. Research already suggests that technologies for enabling autonomous driving can, in many cases, do a better job of avoiding accidents and improving traffic flow than human drivers. They also seem to do better at things like parallel parking — a task that has caused more than one student driver to fail a driving test.

But does this all mean that, as a driver, I can stop paying attention? Not in the near future. But someday.

Goodbye passwords, hello biometrics

Let's face it — passwords suck.

Every day we have to recall all manner of alphanumeric combinations for bank PINs, network log-ons, corporate email, social networking, and e-commerce. According to Microsoft Research, the average user types eight passwords per day.

During a talk at last year's SAE Convergence, Joseph Carra from the US Department of Transportation said, “Passwords have to go” ... a breath of fresh air for those of us who rely heavily on the "forgot password" option. The stage is set, according to Carra, for biometrics to replace passwords in the vehicle.

Using biometrics for driver preferences is nothing new — my favorite example is a car seat that can identify you by the shape of your butt — but using them to replace passwords makes perfect sense.

Ultrasound fingerprinting, iris scans, facial recognition, signature dynamics, voice recognition, keystroke dynamics, hand geometry, skin patterns, and foot dynamics are already being used in enterprise security, law enforcement, border control, ATM transactions, and so on. And second-gen biometrics promise to pump up the Sci-Fi factor with neural wave analysis, electro-physiological biometrics, skin luminescence, body odor, and so on.

Many technologies eventually find their way into the car after becoming popular elsewhere — mobile telephony, media players, GPS navigation, etc. I can’t think of too many world-changing technologies that got their start inside the car. But given the innovative trajectory of today’s auto industry, that may be about to change.

A matter of context: How digital instrument clusters can enhance the driving experience

I always drive a manual, so checking the tachometer in my car’s instrument cluster has become second nature to me. But while I have a personal interest in what my cluster displays, why would a software company like QNX be interested in instrument clusters? After all, most clusters use physical gauges and relatively little software.

The answer, of course, is that automakers are starting to migrate to digital instrument clusters, which replace mechanical gauges with virtual instruments rendered on an LCD display. In fact, Jaguar and Land Rover, who are pioneers in this market, have been shipping QNX-based digital clusters since about 2010. Here, for instance, is a photo of the digital cluster and dash in the latest Range Rover:



So why use a large LCD display instead of mechanical gauges? For one thing, you can attract early adopters who always want the latest tech and who see large 3D displays as cool. But more importantly, a digital cluster can provide an experience that is both personal and adaptive — personal because consumers today want to control the UX (just as they customize their smartphones) and adaptive to help the driver in a variety of traffic situations.

Context matters
In the latest QNX technology concept car, for instance, the digital cluster can re-configure itself to display a 3D rear view camera to help with parking. Saab pursued similar ideas a few years ago with a context-based cluster that avoids loading the driver with too much information during night-time driving.

It will be interesting to see who takes this to the next level with an adaptive HMI that takes speed, location, and driving conditions into account. For instance, driving at high speed on a German Autobahn differs immensely from driving at low speed on a busy downtown street with lots of pedestrians and intersections. These two scenarios place different demands on the driver, and a digital cluster could adapt accordingly.

On the autobahn, the cluster could increase the size of the speedometer and tachometer to make them easier to see, while hiding other information that isn’t currently needed. (The cluster would, of course, still display any necessary warnings, such as high oil temperature.) In the city, meanwhile, the cluster could replace the tachometer with pedestrian warnings to improve the driver's situational awareness.

Also, think of a car that supports both automatic and manual gear-shifting. A driver who prefers automatic might not be interested in a tachometer, whereas a driver who shifts manually will want to see a RPM readout to optimize gear shifting. A digital cluster could accommodate both preferences.

For safety’s sake
What does it mean from a safety perspective to include a large display and its attendant electronics in the car? A malfunctioning digital cluster can’t directly kill or injure, but it could give false indications that may lead to an accident. That is why automakers will likely have to address ISO 26262 requirements for their digital clusters.

So what is ISO 26262? It’s a standard that focuses on functional safety in cars and other types of passenger vehicles, with the goal of avoiding or controlling system failures. It is similar in content and purpose to the IEC 61508 functional safety standard, to which two QNX OS products have already been certified. Read our previous posts (here and here) for more information on ISO 26262.

Massive arrays
When it comes to digital clusters, I’ve only scratched the surface. For instance, cars are becoming massive sensor arrays that generate tons of data. By leveraging this data, reconfigurable clusters could display contextually relevant information, such as highlighting a person in your path, an accident up ahead, or the current speed limit.

And from the automaker’s perspective, a digital cluster could help reduce costs by allowing the same hardware to be used across multiple vehicle lines; in many cases, only the graphics would need to be “reskinned.”

---

Emil Dautovic is an automotive business development manager at QNX Software Systems, where he is responsible for the European automotive market.

Finally, I can throw away my 8 tracks

Okay, maybe I'm not old enough to have owned 8-track tapes. But I do remember that my uncle had an 8-track player in the dash of his station wagon when I was a kid, and I am old enough to have owned a car with a cassette player.

Music has been fundamental to the driving experience for about as long as cars have been on the road. Terrestrial radio dominated forever, supplemented by tape and then CD. XM radio came along in 2001 and connecting your iPod started to show up in the late 2000s. That's 5 formats since the Model T was introduced in 1908 (okay, so it didn't  have a radio) and 3 formats in the first 90 years.

Now, with connected cars becoming a reality, the rate of change is shifting into overdrive. Want Pandora – check. Want to listen to the top alternative radio station in Dublin while driving in California – check. Want to keep listening to your Songza programming as you move from the house to the car – check.

Today's announcement from QNX and 7Digital adds a whole new dimension. Having 7Digital in the car will unify the music ownership experience across the big three: car, pocket, and home. Want to listen to your own music programming in the car – check. Want to buy a song you just heard on that Dublin radio station – check.

Read the press release for details. And when you're done, check out the 7digital blog.