The 10 qualities of highly effective hands-free systems

The first time I saw — and heard — a hands-free kit in action was in 1988. (Or was it 1989? Meh, same difference.) At the time, I was pretty impressed with the sound quality. Heck, I was impressed that hands-free conversations were even possible. You have to remember that mobile phones were still an expensive novelty — about $4000 in today’s US dollars. And good grief, they looked like this:



It’s almost a shock to see how far we’ve come since 1988. We’ve become conditioned to devices that cost far less, do far more, and fit into much smaller pockets. (Though, admittedly, the size trend for smartphones has shifted into reverse.) Likewise, we’ve become conditioned to hands-free systems whose sound quality would put that 1998 kit to shame. The sound might have been okay at the time, but because of the contrast effect, it wouldn’t pass muster today. Our ears have become too discerning.

Which brings me to a new white paper from Phil Hetherington and Andrew Mohan of the acoustics team at QNX Software Systems. Evaluating hands-free solutions from various suppliers can be a complex endeavor, for the simple fact that hands-free systems have become so sophisticated and complex. To help simplify the decision process, Phil and Andrew have boiled the problem down to 10 key factors:

• Acoustic echo cancellation
  
• Noise reduction and speech reconstruction
  
• Multi-channel support
  
• Automatic gain control
  
• Equalization
  
• Wind buffet suppression
  
• Intelligibility enhancement
  
• Noise dependent receive gain
  
• Bandwidth extension
  
• Wideband support

Ultimately, you must judge a hands-free solution by the quality of the useful sound it delivers. By focusing on these 10 essentials, you can make a much sounder judgment (pun fully intended).

Recently, Electronic Design published a version of this paper on their website. For a longer version, which includes a decision checklist, visit the QNX download center.

Am I crazy for talking to my car?

Earlier this afternoon, I participated in a connected car panel at SpeechTEK 2012, hosted by our friend Mazin Gilbert from AT&T. The other panelists included Greg Bielby of VoltDelta, Thomas Schalk of Agero, and Hakan Kostepen of Panasonic.

Even though Mazin did a fantastic job, not every panelist had a chance to answer every question. I was itching to answer some, so here are my responses to the questions that I didn't get to answer, or where I feel I could have provided a more complete response.

Have speech technologies matured to the point where they can be used robustly in the car? The general answer to this question from the panel was yes, but I think the real answer is a qualified yes. The technologies exist, but often aren't applied or may need auto-specific adaptations to handle in-cabin noise or other issues. Natural language recognition was an oft-stated driving technology, but a missing piece to the puzzle is hybrid recognition. I don't mean pushing recognition wholesale to the cloud, like Siri does. I mean a true split of the recognition effort, where each part does what it’s best at. Put the front half of acoustic processing in the vehicle to clean up the audio and convert the waveform to frequency-domain data, then send the data to the cloud-based server. The cloud server can then parse and interpret the data, and send back the result.

Hybrid speech rec solves three problems at once: better audio signals (the car can improve audio specific to the in-cabin environment), better cost (frequency data is far more compressed than raw audio, so you pay less for data transfer), and better responsiveness (hybrid rec gives the server time to start working on the response while it's coming in instead of waiting for the whole utterance to finish before starting).

Is driver distraction a major business driver, or is it the "Siri effect"? Currently, the car industry seems to use driver distraction as a reason to push a lot of features into speech. Many of those uses are gimmicky. Personally, I don't care if I can set my climate control system with voice — why would I when I can simply turn a dial? I once had someone ask me about the feasibility of adding voice recognition commands for rolling down the windows. I asked him, "Yes, but wouldn't people just push the window button?"

We shouldn’t implement speech commands just because we can. They may have contributed to excitement in the early adopter crowd, but we're beyond that now. Mind you, there are some seriously useful ways to use voice. For instance, any time you need to pick from a huge number of choices, voice recognition is the natural way to go. Calling contacts ("Call Sarah Potter"), entering destinations ("Go to 3121 South Park Street"), or picking music ("Play Audioslave") are all much easier than using an HMI to enter the same information, and safer to boot. It just has to work consistently and accurately.

Will car makers see more speech moving to the cloud, or will it be a hybrid of cloud and embedded? I disagree with the majority of the panel on this one, and, I think, the majority of people in the industry. Most auto people believe a hybrid between embedded and cloud allows the best of both worlds — good recognition and updatability when connected, and consistent reliability when not. My colleague Andrew Poliak also champions this view with a memorable catch phrase: Zombie Apocalypse. That is, you still want the system to work, albeit partially, when the infrastructure isn't available.

But if you ask me, everyone is missing the point — theirs is a technology-centric point of view. Everyday customer acceptance of a particular technology is notoriously harsh: if it doesn't work well, it gets rejected out of hand. Good cloud solutions beat an embedded solution hands-down; they just need some improvements (see my hybrid bullet above). Once a customer experiences a good solution, they will become frustrated with one that performs poorly. In my opinion, it's better not to offer the service at all, than to try a graceful degradation of capability, because most customers won't understand or care. Spend the effort instead on making sure you always have an acceptable cloud connection — either through multiple redundant mechanisms or a car-based powerful antenna — and you'll be better off. Even when the car knows some data that the cloud doesn't (like a mobile's contact list or music selection), there's no need to handle that on the embedded side. The cloud recognition server is powerful enough to not require the data set a priori. And I think we can predict an eventual migration of phone data to cloud-based data (or cloud-synchronized data) that makes the car's knowledge either easily transferrable or less relevant.

Who makes money, and how, from voice-enabled agents or voice services? This was one of the best questions of the panel, because nobody really knows the exact model, but everybody agreed that customer tolerance is very low. The most likely candidate is ad-based revenue. This doesn't mean reading ads aloud to the driver, but rather, positively influencing search results for either active or temporary situation-based points of interest (POIs). Depending on how valuable the service is to the driver, there will still be an option for service-based payments and high-value apps.

Standards and building mobile apps — will it come? You need standards if you want to build an app platform that will promote application creation and adoption. That's what we're doing with the QNX CAR 2 application platform — creating a way for someone other than the car companies to join the ecosystem and to deploy their apps to the car in a controlled way. But don't forget, you need a standard way to deploy apps for the cloud half of the recognition, too.

To close, let me share two photos. One was taken outside the Marriott Marquis, the hotel hosting the conference just off of Times Square in NYC. The other is from our PR agency, Breakaway Communications. What do they have in common? Wooden water towers. Sorry, I couldn't help myself; I just love those things. They just look so quaint in a city full of glass and brick.

WIRED Autopia slips into driver's seat of QNX reference vehicle

Chances are, you've seen pictures of the new QNX reference vehicle. You may have even seen the "making of" video that QNX released a few days ago. But have you seen any video of the vehicle in action?

If not, check out this vid by Doug Newcomb of WIRED Autopia. Last week, at Telematics Detroit, Doug met up with Andrew Poliak of QNX for a tour of the vehicle and its various features, including a re-skinnable UI and voice-controlled Facebook integration. The camera was rolling, and here's what it caught:

Phonedog connects with QNX concept car at BlackBerry World 2012

If you aren't at BlackBerry World this week, you're missing out. For starters, you won't get to see what, in my biased opinion, is the world's coolest car: the QNX-powered and very connected Porsche 911.

But not all is lost. You can still watch this video from Sydney Myers of PhoneDog.com, who caught with up with Mike Shane of QNX for a tour of the car's features — from instant smartphone pairing and off-board navigation to handsfree calling with HD stereo. Check it out:



My favorite part? When the text overlay on the video shouts out "The audio quality was REALLY good." Got that right.

And did I mention? Mike is one of the super-talented people who built the concept car. He's a keeper.
 

Find me a Starbucks! QNX concept car showcases power of WATSON speech engine

Yes, you can talk to the QNX concept car and tell it what to do.

Recently, our friends at AT&T invited us to bring the concept car to their "Living the Networked Life" event in New York. We said yes, of course! After all, what could be cooler than riding the streets of Gotham City in a digitally pimped-out Porsche 911?

Kidding aside, the event provided an excellent opportunity to demonstrate how the car takes advantage of WATSON, AT&T's natural-language speech engine. To get an idea of what WATSON can do, check out this video from Terrence O'Brien of Engadget:



For the full Engadget article, click here. And stay tuned for more updates from the Living the Networked Life event.
 

A quick tour of the QNX CAR 2 application platform

If you're looking for a quick, two-minute intro to the QNX CAR 2 application platform, you've come to the right place.

In this video, Kerry Johnson, automotive product manager at QNX, takes us on a tour of the platform, including its home screen, media player, application area, HTML5 support, phone app, and acoustic processing.

Ready? Then hit the Play button and let's get started:



In case you didn't know, the QNX CAR 2 platform forms the basis of the QNX concept car, a specially modified Porsche 911 that demonstrates what to expect in next-generation car infotainment systems. Earlier this year, the platform drove home with a 2012 Best of CES award, in the Car Tech category.
 

ITU-T: Developing standards to fight driver distraction

The telecommunication standardization sector of the International Telecommunications Union is poised to play a crucial role in tomorrow’s connected cars. And yet, many people in the auto industry have never heard of the ITU, or of its standardization sector, the ITU-T. So let’s start with a quick introduction.

The ITU is the United Nations agency that deals with telecommunications. More specifically, it is where governments come together to agree on international standards for Information and Communications Technologies (ICTs).

Currently, the ITU-T is developing recommendations for ICTs that interact with drivers — examples include networked-based navigation systems, web browsers, and mobile phones. These recommendations will apply to networks; to applications accessed by drivers; and to connected, nomadic, and factory-installed devices. Strictly speaking, these recommendations are voluntary, which is precisely why they are referred to as “recommendations.” However, they can become binding if mandated by regional government agencies or customers.

ITU-T recommendations for the car are needed for several reasons:

• ICTs are moving into the automotive cockpit — Increasingly, ICT systems under the scope of the ITU-T are finding their way into the cockpit and interacting with drivers. Technology-related driver distraction has been recognized as a global problem that needs to be addressed. Internationally agreed guidance on the design and performance of these systems can help increase safety.
   
• Easy-to-find guidance for ICT community — ICT designers, developers, and application authors need easy access to guidance on design and performance requirements for ICT systems that interact with drivers. The ICT community consults ITU-T recommendations for guidance and requirements on ICT systems. Therefore, there is real value in having ITU-T recommendations that can serve as a reference to existing driver distraction-related standards and to fill any standardization gaps.
   
• Internationally agreed standards — The ITU-T is where governments come together to agree on international telecommunications standards. This is what makes these standards unique. It also gives them more weight with regional Standards Development Organizations (SDOs) and regulatory authorities. There is even value in an ITU-T recommendation that simply references existing standards since it will have gone through the ITU-T approval process.

Focus group on driver distraction
Last year, I became the founding chair for the ITU’s Focus Group on Driver Distraction (FG Distraction), which was created to pull expertise from the automotive industry and human factors experts into the ITU-T standardization process. The group currently has 3 planned ITU-T recommendations related to driver distraction:

G.SAM — recommendation on mechanisms for managing the situational awareness of drivers:

 

G.V2A — recommendation on an automotive interface (for instance, APIs) for applications external to the vehicle gateway:



P.UIA — recommendation on automotive user interface requirements:



FG Distraction will finalize pulling together input from industry and human factors experts by December 2012. Approved ITU-T recommendations are not expected until late 2013.

Want to contribute?
If you’d like to participate in FG Distraction, the group is open to any individual from a country that is a member of ITU and who is willing to contribute to the work (which is just about everyone). This includes anyone who is also a member or representative of an interested SDO. There is no cost to participate.

For more information about FG Distraction and upcoming meetings, click here. The next meeting will take place on April 4-5 at the SAE Headquarters in Troy, Michigan, USA.
 

Gearing up for CES

I arrived in Las Vegas last night, gearing up for the CES show. I know I must be in Vegas: When I woke up at 4:30 am (my body is stuck in eastern time), there was still a buzz around the hotel — people just do not stop here.

I’m looking forward the show. Our automotive development team has been hard at work on some exciting new technology, and I can hardly wait to show it off.

First, we are demonstrating our new concept car, based on a Porsche Carrera. This thing is loaded with goodies to demonstrate how you can use your smartphone and tablet to improve the driving experience. For instance, the car supports Near Field Communications (NFC) pairing: You simply touch your phone to the car and the two become instantly paired — no more fumbling with unintuitive menus and security codes.


The new concept car features one-touch smartphone pairing, tablet-based rear-seat
entertainment, ultra HD voice technology, and a reconfigurable instrument cluster.

We’re also showing a level of integration beyond a simple voice-dialing list. For instance, you can use your phone’s contact list to direct your navigation system or to automatically contact meeting invitees when your car knows you’ll be late for an appointment. We will also demonstrate our ultra HD voice technology, which provides full stereo sound for handsfree calls — you’d have to hear this to get the real impact. It’s like you're sitting right next to the person on the other end of the call. (I hope this works well in the noisy show floor environment!)

We're also launching the QNX CAR 2 application platform, which will allow automakers to leverage the power of the mobile development community and to keep in-car infotainment software fresh for consumers. We are doing some pretty unique things with HTML5, including the ability to write and package applications for deployment to the car. Another cool feature is the ability to dynamically detect and play media that is added to the system – try doing that with a standard browser!

Just writing this has me looking forward to getting started. See you at 2012 CES!
 

Video: The secret to making hands-free noise-free

 

Explaining a highly technical product to a broad audience is tough. To succeed, you must reach out to people on their own terms, without being condescending. Most people love a good explanation, but everyone hates being talked down to.

Case in point: The QNX Acoustic Processing Suite. This software runs in millions of cars and offers a benefit that everyone can relate to: clear, rich, easy-to-understand hands-free calls. But once you start explaining how the suite does this, it's easy to get mired in technical jargon and to forget the bigger picture — something that even a technical audience wants to see.

So we dropped the jargon and opted for a creative approach. It involves a marching band, a rock guitarist, and, for good measure, an electric fan with a really long extension cord. Seriously.

Intrigued yet? Well, then, grab some popcorn and dim the lights:




Interested in learning more about this technology? Check out the acoustic processing page on the QNX website.

BTW, companies that use the QNX Acoustic Processing Suite in their products include OnStar, whose FMV aftermarket mirror recently won a CES Innovations Design and Engineering Award.

Posted by Paul Leroux
 

QNX-powered OnStar FMV drives home with CES Innovation award

Paul Leroux

This just in: The OnStar FMV aftermarket mirror, which brings the safety and security features of OnStar to non-GM vehicles, has won a coveted CES Innovations Design and Engineering Award.

To clinch this award, a product must impress an independent panel of industrial designers, engineers, and trade journalists. Speaking of impressions, it seems that OnStar FMV also made a hit with the folks at CNET, because they've chosen it as one of their Top Holiday Shopping Picks for 2011.

As you may have guessed, OnStar FMV uses QNX Neutrino as its OS platform. It also uses the QNX acoustic processing suite, which filters out noise and echo to make hands-free conversations clear and easy to follow. The suite includes cool features like bandwidth extension, which extends the narrow-band hands-free signal frequency range to deliver speech that is warm and natural, as well as intelligible.

Have time for a video? If so, here's a fun look at FMV's features, including stolen vehicle recovery, automatic crash response, turn-by-turn navigation, hands-free calling, and one-touch emergency calling:


 

Pimp your ride with augmented reality — Part I

The use of electronics is exploding in automotive. Just last week, Intel proclaimed that the connected car “is the third-fastest growing technological device, following smartphones and tablets.”

Ten years ago, you’d be hard-pressed to find a 32-bit processor in your car. Now, some cars have 4 or more 32 bitters: one in the radio, another in the telematics module, yet another in the center display, and still another in the rear-seat system.

Heck, in newer cars, you’ll even find one in the digital instrument cluster — the QNX-powered cluster in the Range Rover, for example. Expect to see a similar demand for more compute power in engine control units, drive-by-wire systems, and heads-up displays.


The Range Rover cluster displays virtual speedometers and gauges, as well as warnings, suspension settings, and other info, all on a dynamically configurable display.

What do most of these systems have in common? The need to process tons of information, from both inside and outside of the vehicle, and to present key elements of that data in a safe, contextually relevant, and easy-to-digest fashion.

The next generation of these systems will be built on the following principles:

• Fully integrated cockpits — Vehicle manufacturers see system consolidation as a way to cut costs and reduce complexity, as well as to share information between vehicle systems. For instance, your heads-up display could discreetly let you know who is calling you, without forcing you to take your eyes off of the road. And it could do this even if the smarts integrating your phone and your car reside in another cockpit component — the telematics module, say.
   
• Augmented reality — With all of the data being generated from phones, cloud content services and, perhaps more importantly, the vehicle itself, presenting the right information at the right time in a safe way will become a major challenge. This is where augmented reality comes in.

Augmented reality is a cool use of cameras, GPS, and data to create smart applications that overlay a virtual world on top of the real world. Here are some of my favorite examples:

AR Starbucks cups — Use your phone to make your coffee cup come alive:



AR Starwars — Blast the rebel alliance squirrels!



AR postage stamp — Add a new dimension (literally) to an everyday object:



And here are a couple more for good measure:

AR ray gun — Blast aliens around the house!

Wikitude AR web browser — Explore the world around you while overlaying social networks, images, video, reviews, statistics, etc.

Stay tuned for my next post, where I will explore how AR could enhance the driving experience for both drivers and passengers — Andrew.
 

Building a hands-free future

The end of my street is governed by a three-way stop. The other morning I was backing out of my driveway when someone rolled past the stop sign and came within inches of hitting me. I stopped, glared at him, and resumed driving. Two stop signs later, the same guy squeezed past my car (in the same lane), completely oblivious to what he was doing.

Why was he driving like this? Probably because he was deeply engrossed in a conversation on his cell phone.

Where I live, using a handset while driving has been illegal for over a year. You cannot talk, you cannot text, you cannot “Facebook”, you cannot Tweet — even if you're stopped at a red light. This makes perfect sense to me. As a driver, your primary responsibility is to control the vehicle. And yet I see people texting on the freeway, talking on their cell phones, and doing who knows what else on an alarmingly regular basis.

The QNX-powered BMW
ConnectedDrive system

Society has become obsessed with mobile devices, and it will take more than legislation to change its behavior. The answer, I think, is to embrace the behavior in a way that makes it possible to interact socially while maintaining control of the car. We’ve seen great progress in hands-free/phone integration, and BMW ConnectedDrive offers an example of how drivers can access email and other smartphone services more safely.

This is the tip of the iceberg. Integrating the handset with the infotainment unit is going to change the way you interact with your car. Intelligently designed apps, combined with multi-modal human machine interfaces, will let you Tweet or update Facebook using speech recognition, keeping your eyes on the road.

Without taking your hands of the wheel, you’ll be able to call a friend and decide that you want to go to dinner, do a local search to find out what’s available, check a restaurant review on Yelp, make a reservation, text your friend back with the time and place, and aim your navigation system at the restaurant. And you’ll be able to do it using natural language. None of this “please say a name” stuff.

Seems futuristic? It’s not. People are working on it today. In fact, QNX-based systems, such as Toyota Entune, already offer a taste of this hands-free and highly personalized future.
 

New release of QNX acoustic processing suite means less noise, less tuning for hands-free systems

Paul Leroux

This just in: QNX has released version 2.0 of its acoustic processing suite, a modular software library designed to maximize the quality and clarity of automotive hands-free systems.

The suite, used by 18 automakers on over 100 vehicle platforms, provides modules for both the receive side and the send side of hands-free calls. The modules include acoustic echo cancellation, noise reduction, wind blocking, dynamic parametric equalization, bandwidth extension, high frequency encoding, and many others. Together, they enable high-quality voice communication, even in a noisy automotive interior.

Highlights of version 2.0 include:

Enhanced noise reduction — Minimizes audio distortions and significantly improves call clarity. Can also reconstruct speech masked by low-frequency road and engine noise.

Automatic delay calculation and compensation — Eliminates almost all product tuning, enabling automakers to save significant deployment time and expense.

Off-Axis noise rejection — Rejects sound not directly in front of a microphone or speaker, allowing dual-microphone solutions to hone in on the person speaking for greater intelligibility.

To read the press release, click here. To learn more about the acoustic processing suite, visit the QNX website.


The QNX Aviage Acoustic Processing Suite can run on the general purpose processor,
saving the cost of a DSP.

 

Wanted: Haunted Vehicles

Halloween is just around the corner, and that reminds me of the haunted room at Lucent Bell Labs. Mind you, it wasn’t really haunted. But for a moment, I was convinced.

Let me explain. As I entered the room, I could hear two of my colleagues talking to each other, and by the sound of their voices, they were both sitting right in front of me. But when I looked, I could see only one person. Creepy, to say the least.

It took a few seconds, but I finally realized what was happening: The other colleague was in a different room, talking over a perfectly tuned prototype of a conference phone. The sense of presence was so real that I couldn’t help but feel we were all in the same room — even after I became aware of the “trick” being played!

It was then that I realized it: We don’t know what we’re missing until we experience it.

Making it real
Current telephone calls don’t sound like face-to-face conversations because the telephone network and terminals band-limit speech from about 50-10000 Hz down to 300-3400 Hz. To make matters worse, the phone’s single channel of audio eliminates spatial information about the sound source. As a result, we perceive most sounds as coming from the same point in space.

But here's the thing: The historical reasons for transmitting these single-channel narrowband speech signals no longer apply. Current technologies — such as wideband speech coders, spatial audio, and VoIP — are enabling speech communications with wider bandwidth speech and greater spatial information.

Many in the industry refer to these next-generation telecommunications systems as telepresence systems. “Telepresence” refers to the degree of realism created by a telecommunications system. Traditional systems have low telepresence while newer systems that use wider bandwidth speech and spatial audio have high telepresence.

Some people believe that a visual display is a must-have for a telepresence system. In reality, a display can decrease telepresence if its quality is poor. Experience shows that an audio-only system can have such high telepresence that people can't distinguish it from face-to-face communications — witness my haunting experience at Lucent Bell Labs.

Until recently, widespread deployment of telepresence systems has hit a roadblock: lack of standardization. Fortunately, the IETF CLUE Working Group and ITU-T Study Groups 16 and 12 are actively developing standards to remedy this situation.

Pimp my ride with telepresence
Telepresence systems have a lot to offer in an automotive environment. For instance, they could:

• reduce driver distraction
• make it easier to understand speech in the presence of vehicle noise
• reduce the fatigue that comes from trying to understand a degraded voice signal

Moreover, a telepresence system makes the talker on the far end of the phone connection sound more like they are in the vehicle; it also makes the talker easier to identify.

Successful deployment of telepresence in an automotive environment depends on several factors:

• attention to the design of vehicle platforms
• use of high-performance acoustic processing algorithms (AEC, NR, etc.), such as those provided by the QNX acoustic processing suite
• the ability to transport telepresence signals between telephony terminals — this is being enabled by increased VoIP availability (via LTE, for instance)

I don't know about you, but I'm looking forward to the day when my vehicle is haunted like that lab in New Jersey!

For additional reading on this topic, download the whitepaper, "Wideband Speech Communications for Automotive: the Good, the Bad, and the Ugly".