What’s next for the connected car?

It’s been almost three years since QNX Software Systems launched its connected car concept, and I thought it would be an interesting exercise to look at what has been accomplished in the automotive industry around the connected car and how some of the concepts are evolving. When the QNX CAR Application Platform was introduced, we provided a simple way to look at a connected car, using four “dimensions” of connectivity:

• Connected to portable consumer devices for brought-in media and handsfree communications
• Connected to the cloud for obvious reasons
• Connected within the car for sharing information and media between front and rear seats, between the center stack and the cluster, and for other similar functions
• Connected around the car for providing feedback to the driver about the environment surrounding the car, be it pedestrians, other cars, or vehicle to infrastructure communications

We’ve seen significant advances and evolutionary thinking on all fronts. Although QNX is not (and cannot be) at the forefront of all of these, our primary emphasis has been on cloud and consumer device connectivity. Nonetheless, it is interesting to look at each area.

Connected to consumer devices, connected to the cloud
Why lump these two together? There is not exactly a clear line between the two since consumer devices are often just extensions of the cloud. If my car connects to a smartphone which, in turn, draws information from the cloud, is there much point in creating a distinction between consumer device and cloud connections? Although it made sense to differentiate between cloud and consumer device connections when phones provided only handsfree calling and simple music playback, today the situation is quite different.

Device integration into the car has been a beehive of activity over the last few years. Smartphones, superphones, and tablets are providing entertainment, social networking, news, and access to a myriad of other content and applications to consumers anywhere, anytime. Automakers want to take advantage of many of these capabilities in a responsible, non-distracting way.

The primary issue here is how to marry the fast-paced consumer electronics world to the lifecycle of the car. At present, there are solutions at the opposite end of the spectrum: standardized Bluetooth interfaces that allow the car to control the smartphone; and screen replication technologies (iPod Out, VNC/Terminal Mode/Mirror Link) where the smartphone takes control and uses the car as a dumb display.

Neither of these scenarios takes full advantage of the combined processing power and resources of the car and the brought-in device. This, to me, is the next phase of car and cloud connectivity. How can the power of the cloud, brought-in devices, and the in-car systems be combined into a cooperative, distributed system that provides a better driver and passenger experience? (If the notion of a distributed system seems a bit of a stretch, consider the comments made by Audi Chairman Rupert Stadler at CES 2011.)

When looking for technologies that can bring the cloud, devices, and car together, you do not need to look any further than the web itself. The software technologies (HTML5, Javascript, AJAX, peer-to-peer protocols, tooling, etc.) that drive the web provide a common ground for building the future in car experience. These technologies are open, low cost, widely known and widely accessible. What are we waiting for?

Connected within the car
The integrated cockpit has emerged as a prevalent automotive design concept. It is now commonplace in higher-end vehicles to see seamless integration between center stack functions and the instrument cluster and driver information displays. For example, turn-by-turn directions, radio tuning, and song now playing are all available to the driver on the cluster, reducing the need to constantly glance over to the main display. One such example is the Audi cluster:

Connected around the car

Three years ago, systems in this category were already emerging, so there really wasn’t much of a crystal ball required here. Adaptive cruise control has become one of the most common features that illustrate how a car can connect to its surroundings. Adaptive cruise control detects the car’s surroundings (cars in front of you) and adjusts your speed accordingly. Other examples include pedestrian detection (offered in Volvo S60 and other models)automatic parking, lane departure warning, and blind spot detection/warning systems.

These Advanced Driver Assist Systems (ADAS) will become more common as cost reductions take place and the technology is provided in lower-end vehicles.

In contrast, vehicle-to-infrastructure communication that requires industry-wide collaboration is proceeding at a pace that you’d expect from an internationally standardized solution.

Read More

Ready to Rock and Roll !

Paul Leroux

What single word best describes a perfectly executed piece of art? More often than not, I would choose the word seamless. Because when a painting, song, or story is done right, nothing feels out of place. Everything fits together so well that, almost magically, the whole becomes greater than the sum of the parts.

The same principle applies when you design a vehicle. Whether it's a dune buggy or an ultra-luxury sedan, your end product should evoke a consistent vision and emotional appeal. People don't want dune buggies with walnut dashboards, nor do they want Bentleys with rollbars. They want a vehicle, and a vehicle brand, that clearly embodies what they value most, be it styling, safety, reliability, or performance.

Well, that's the theory. But putting it into practice isn't easy. For instance, people now expect their cars to integrate with smartphones, tablets, and other mobile devices. By satisfying this demand, automakers have a real opportunity to win over consumers. But how does the automaker provide this integration without losing control over the user experience, and without sacrificing their brand identify to that of a third-party device? And lest I forget, without sacrificing safety?

Consumers, conditioned by smartphones and tablets, also expect in-dash user interfaces to be slick and intuitive. To create these interfaces, automotive developers are tapping into HTML5, Adobe AIR, OpenGL ES, and specialized toolkits. Problem is, none of these is a magic bullet. None addresses every problem. But what if you could take the best of each and seamlessly blend the results on an in-dash display, without breaking a sweat?

These are the kinds of problems that QNX is tackling. To create compelling products, our automotive customers must integrate numerous mobile and UI technologies, so we've created a platform to help make that integration as clean and simple as possible. I keep thinking of the 1950s, when some innovative musicians fused multiple styles — blues, boogie-woogie, country, gospel — into a thrilling new musical form. You've probably heard of it; it's called rock and roll. That's the kind of exciting synthesis we want to enable.

Simply put, we want to make our customers rock stars. Because when you create an automotive platform, you are judged by only one criterion: your customers' success. Little else matters. And speaking of stars, we've enlisted some remarkably knowledgeable and insightful people to contribute to this new blog. I can say that with confidence, because I have the privilege of working with many of them every day.

So buckle in, because it's going to be a great ride. Our goal is to keep you up to speed on what matters in automotive infotainment. Sure, we'll talk QNX now and then, but we're going to take the high road and cover everything from data plans to driver distraction. So make sure you don't miss a single post: subscribe to our RSS feed and follow us on Twitter at @QNX_Auto

 

Read More