Report from CTIA Wireless: Apps in the Car

You wouldn’t think that CTIA Wireless, a mobile show, would be a good venue for a car guy. But automotive journalist Doug Newcomb put together a set of panels that managed to attract everyone from the automotive industry who attended the show.

I met a good number of friends from a variety of automakers, tier one suppliers, and hardware and software vendors. I also had the distinct pleasure of participating in one of Doug's panels, which was moderated by Damon Lavrinc of WIRED.

The topic was the future of apps in the car, and it generated a spirited discussion. Panel participants included Geoff Snyder from Pandora, Michelle Avary from Toyota, Henry Bzeih from Kia, and Scott Burnell from Ford — all experts on the topic.

Andy speaking on the

apps panel. Videos of all

the panels are now online.

In general, we agreed: apps are coming to the car. They have already arrived in several cases, and it’s only a matter of time before they come to mass-market vehicles. And apps are not for North American alone: it's a worldwide phenomenon.

Mind you, we engaged in lively debate on a number of questions: What role does the mobile app developer play? How to deal with the fragmentation caused by different OEM app platforms? How to deal with driver distraction? And when will the "one man app" ever make it into the car? We all had good and varied opinions on these topics, and the session was very well received by the audience.

Derek Kuhn, QNX vice president of sales and marketing, also participated in a panel session, titled "Can we all just get along… for the consumer's sake?". That panel focused on how the industry as a whole can create a more seamless experience for the consumer. Derek's co-panelists included Mark Harland from GM, Leo McCloskey from Airbiquity, Brian Radloff from Nuance, and Niall Berkery from Telenav.

Did I mention? Videos of all the panels are now on Doug Newcomb's website — check them out!
 

OnStar RemoteLink app comes to BlackBerry smartphones

This just in: The RemoteLink App from OnStar, which allows smartphone owners to remotely start their vehicles, check fuel levels, and lock or unlock their doors, is now available for the BlackBerry Bold 9900 and 9930 phones.

RemoteLink has been available for iPhone and Android phones, but many OnStar subscribers have asked for a BlackBerry version of the app. In response, Onstar wrote a new version for the BlackBerry platform, in HTML5.

“Writing the app using HTML5... positioned us to be more flexible supporting new phone operating systems,” said Steve Schwinke, director of advanced systems development for OnStar.

Opening screen
for RemoteLink
© GM Company 

In 2011, OnStar added navigation to RemoteLink, allowing users to search for a destination on their smartphone and send it directly to their vehicle. Users can then access the route through the QNX-powered OnStar system.

By leveraging OnStar’s connection to the vehicle, the app can report on oil levels, tire pressures, fuel level, and lifetime miles per gallon. It also offers remote commands, such as remote start, door lock/unlock, and horn/light activation.

According to OnStar, a total of 821,000 smartphone owners actively use the RemoteLink app.

To read OnStar's press release, click here. To download the RemoteLink app from BlackBerry App World, click here.

On a related note, here's a conversation between QNX's Andy Gryc and OnStar's Steve Schwinke. The topic: how HTML5 can benefit the auto industry.


 

Concept car out. Reference vehicle in.

Our big announcement for Telematics Update is that we are not showing a concept car. Odd news, you say. The truth is, we're not building a concept car because we are building a reference vehicle. Splitting hairs? Not really.

Unlike the Corvette and the Porsche, our demo for this show will be based on the exact same technology that our customers are using today to design their next-generation systems.

So why vehicle instead of car? Is it a truck? Nope. A van? Negative. What about a motorcycle? Double negative.

I was hoping to give you a sneak peek at what we are working on but I'm not allowed to give away the details. However, I did manage to get these shots – let me know if you can see the vehicle. :-)


 

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.
 

QNX joins Car Connectivity Consortium

This just in: QNX Software Systems has announced its membership in the Car Connectivity Consortium (CCC), the organization dedicated to developing the MirrorLink standard for car-smartphone connectivity.

MirrorLink offers a way to help car occupants access their smartphone applications. For instance, it could allow occupants to access their phone apps through the infotainment touchscreen, steering-wheel buttons, or other in-car controls.

Source: CCC

As a core member of the CCC, QNX Software Systems will have access to MirrorLink specifications under development and to various MirrorLink work groups. It will also be able to support future MirrorLink options in QNX-based systems, and help drive development of the standard.

“QNX Software Systems is a key player in the evolution of car infotainment technology and we are pleased to welcome them into the organization,” commented Mika Rytkonen, the CCC's chairman and president.

The announcement fits into QNX's strategy of enabling automotive developers to leverage widely supported industry standards.

“We believe in giving automotive customers choice and the flexibility to use the technologies best-suited to their requirements — contributing to the CCC helps us deliver on that commitment,” added Andy Gryc, automotive product marketing manager for QNX. (This is, of course, the same Andy Gryc who contributes to this blog.)

To read the press release, click here.

 

What the connected car is really all about (and what we need to do about it)

Recently, I was invited to participate in a webinar that highlighted hits and misses at Mobile World Congress. It occurred to me that some of you might be interested in what I had to say — at the very least, I’d earn points with Paul Leroux, our editor, for spontaneously offering up a blog post. :)  So here's what I said... almost verbatim.

"First, a quick intro on QNX: Many will know us as the wholly owned subsidiary of RIM whose software platform powers the BlackBerry PlayBook. But we also provide the de facto standard platform for all types of in-vehicle infotainment and navigation systems. And it’s from this perspective that I offer these comments. My primary observation is regarding the evolving dialogue surrounding the connected car and what I think it represents. Three years ago we were here with Alcatel-Lucent, showcasing the first LTE connected concept car, based on a Toyota Prius. This car proved so popular that we had to hire a security guard to help manage the traffic. Now, three years later, there are a number of connected production vehicles to be seen, including a QNX-based BMW 7 series in the GSMA’s connected home exhibit. And the announcements this year focused not so much on broadband connectivity per se (it's here, people expect it), but on the integration of the smart phone with the vehicle. At QNX, we talk about the personalization of the in-vehicle experience, as people want to bring in their own devices, their own music, their own contacts and other content — and experience these in the vehicle setting. For instance, Ford not only announced the B-Max vehicle, but used MWC as a platform to launch Ford Sync for Europe. Toyota and Samsung, meanwhile, announced support for Samsung Mobile Car Application for integration of phones to the car's head unit. So if step one was getting a broadband connection to enable a consumer experience in the car, and step two is about personalizing that experience, what’s next? I think that, ultimately, the connected car is all about the consumer, and this is how revenue will be generated in a way that connected telematics on its own could never do. You could be an automaker interested in improving how to service a car and its owner after the car has driven off the dealer's lot. Or you could be a carrier interested in extending your offer beyond connectivity to deliver value-added services. Or perhaps you’re a small business trying to get more people in the door. In each case, the car represents a new frontier. And it offers the added value of context – not only do you know if someone is available and where they are, but you also know that they are driving a vehicle. The next few years are going to be very exciting as the automotive and mobile industries converge to address this opportunity. Think about the brands involved: Companies like Audi, BMW, and GM on one hand and the likes of AT&T, Verizon, and Vodafone on the other. They’re mutually dependent — neither group will be successful without the other. Automotive needs to leverage the investments being made for smart phones, be it device technology, network infrastructure, or developer communities. Meanwhile, the mobile industry has to consider the nature of automotive in terms of safety, security, and liability, not to mention product life cycles. It's safe to say that automotive is just the first example of this type of industry convergence and transformation. All of the carriers are looking at M2M as a huge untapped market opportunity. And within the classic embedded market, there are an almost infinite number of market segments, truly an example of the Long Tail. It will be exciting to watch how mobile transforms those markets and vice versa — what will mobile look like in 5 years from now? I don’t think we can easily predict it; after all, it's not going to be like anything we’ve seen before. But I can’t wait to find out.

So there you have it. If you'd like to hear the entire webinar, you can register here to access the archived version.
 

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.
 

HTML5: Bustin' the myths

Did you know you can build HTML5 apps that don't use an Internet connection? Did you know you can run HTML5 apps without a web browser? And did you know HTML5 apps can show snappy performance even on automotive silicon? (As you can well imagine, in-car infotainment systems don't ship with quad-core server-class CPUs.)

If you answered no to any of these questions, you need to stop for a minute and check out this interview with QNX Software Systems' Kerry Johnson. Heck, even if you answered yes to all three questions, you'll probably still appreciate what Kerry has to say — and besides, you'll catch a glimpse of a complete in-car UI coded in HTML5. What could be bad?



While I have you, check out Andy Gryc's Q&A series on HTML5, if you haven't already. You'll find the first two installments here and here.
 

Auto + Mobile

I love this play on words. I can’t claim it as my own but I think it’s very cool that the word automobile breaks down into auto and mobile. I’m sure the term originally referred to automatically mobile horseless-carriages or some such thing. According to one online source, the word dates from 1895 and means “self-propelled motor vehicle”.

But today, it represents the convergence of two historically independent industries, auto and mobile. Now, more than ever, consumers are extending their digital lives into their cars. They want a personalized in-vehicle experience, including access to their music, to their friends, to their favourite places, and to their schedules — both personal and professional. And that’s just the beginning.

Following the Consumer Electronics Show (CES) in January, I heard many in the industry refer to CES as one of the most important automotive shows of the year. You heard that right: CES is now considered an automotive show.

The new QNX concept car is
scheduled to appear at MWC.

Now it’s February and QNX Software Systems is headed to Barcelona where we will demonstrate our connected concept car on the BlackBerry stand in Hall 7 at Mobile World Congress. This same car won a Best of CES award in the car tech category.

MWC is the show for mobile phones and everything related. During the show, we will participate on a luncheon panel hosted by Fierce Markets, Paving the Way to Success for the Connected Car. Other panelists include Ford, AT&T, and the GSMA.

MWC isn’t known as an auto-focused event but I expect this to change. Most carriers see the connected car as an emerging growth market, as do silicon vendors. Meanwhile, handset and car companies work towards improving the integration of the mobile experience into the car without impacting driver distraction.

Auto + Mobile. End of story.

For more info on the panel, click here.
 

New CNET video takes you on guided tour of QNX concept car

Paul Leroux

This just in: Antuan Goodwin of CNET has posted a video walkthrough of the new QNX concept car, which showcases the many capabilities of the QNX CAR 2 application platform.

Antuan touches on all of the car's salient features, including one-touch smartphone integration, backseat entertainment, video streaming, rich app support, ultra HD voice technology, and the reconfigurable digital instrument cluster. Check it out:


 

CrackBerry posts first peek at OnStar RemoteLink for BlackBerry PlayBook

Paul Leroux

This morning at CES, CrackBerry.com met up with QNX's Andrew Poliak for a walkthrough of the new OnStar RemoteLink app for the BlackBerry PlayBook.

If you aren't familiar with RemoteLink, it provides a very cool and powerful connection to OnStar-equipped vehicles. From the convenience of your tablet or phone, you can access gas mileage, tire pressure, and other information in real time; you can even remotely start your vehicle and unlock its doors.

Cooler yet, the new version running on the PlayBook boasts a user interface built entirely in HTML5. But enough blather from me. Roll the tape...



Did you know? QNX is the core OS for the PlayBook, but it's also the OS for OnStar and OnStar FMW.
 

HTML5 is a great option for the risk-adverse

The conservative nature of automakers makes them ideal candidates for the brand-spanking new HTML5. Say what?

While this seems paradoxical, it is an interesting take-away from the discussion between TCS' director of engineering Michael Camp and our very own Andy Gryc. If you've got three minutes to spare, watch the latest video in our HTML5 series for the whole story. (As usual, don't miss the ending. ;-)

This interview of Michael Camp is the fourth in a series from QNX on HTML5.

HTML5 and the software engineer

HTML5 appears to have a number of benefits for consumers and car manufacturers. But what is often good for the goose is not necessarily good for the developer. Talking to the guys in the trenches is critical to understanding the true viability of HTML5.

Andy Gryc and Sheridan Ethier, manager of the automotive development team at QNX, pair up for a technical discussion on HTML5. They explore whether this new technology can support rich user interfaces, how HTML5 apps can be blended with apps written in OpenGL, and if interprocess communication can be implemented between native and web-based applications.

So without further ado, here’s the latest in the educational series of HTML5 videos from QNX.



This interview of Sheridan Ethier is the third in a series from QNX on HTML5.

Is HTML5 a good gamble?

As the consumer and automotive worlds continue to collide, HTML5 looks like a good bet. And not a long shot either. In fact, the odds are all automakers will eventually use it. But since the standard won’t be mature for some time yet, should you take a chance on it now? 

To answer this, Andy Gryc talks to Matthew Staikos of RIM. Matthew is the manager of the browser and web platform group at RIM, and has over 10 years of software development experience with a strong focus on WebKit for mobile and embedded systems. Matthew co-founded Torch Mobile, which was acquired by RIM for their browser technology.

Andy’s conversation with Matthew is the subject of the following video, the second in an educational series designed to get an industry-wide perspective on HTML5. 

This interview of Matthew Staikos is the second in a series from QNX on HTML5.

What’s HTML5 got to do with automotive?

There’s been a lot of noise lately about HTML5. A September 2011 report by binvisions shows that search engines and social media web sites are leading the way toward adoption: Google, Facebook, YouTube, Wikipedia, Twitter, and plenty more have already transitioned to HTML5. Some are taking it even further: Facebook has an HTML5 Resource Center for developers and the Financial Times has a mobile HTML5 version of their website.

It won’t be long before HTML5 is ubiquitous. We think automakers should (and will) use it. 

To elucidate the technology and its relevance, we’ve created a series of educational videos on the topic. Here is the first in that series. Interviews with partners, customers, and industry gurus will soon follow. 

This simple overview is the first in a series from QNX on HTML5. (Personally I like the ending the best.)

Seamless connectivity is for more than online junkies

As much as I’m not always enamored with sitting behind a computer all day, I find being off the grid annoying. Remember this email joke?

You know you’re an online junkie when you:
• wake up at 3:00 am to go to the bathroom and stop to check your email on the way back to bed
• rarely communicate with your mother because she doesn’t have email
• check your inbox. It says ‘no new messages,’ so you check it again 

Even though this joke circulated several years ago, it still strikes a chord. The big difference now is that there’s no longer a subculture of ‘online junkies.’ From the time we wake up in the morning to the time we go to bed, we all want to be connected — and that includes when we get behind the wheel. So to this joke I would add:

• resent driving because it means going off the grid

At QNX, we’re working toward a seamless experience where people can enjoy the same connectivity whether they’re texting their spouse from the mall or checking traffic reports while driving down the highway. See what I mean:



For more information about the technology described in this video, visit the QNX website.
 

Can HTML5 keep car infotainment on track?

Paul Leroux

True story: When a train on the Trans-Mongolian Railway crosses from Mongolia into China, it must stop and have all of its wheel assemblies replaced. Why? Because the track gauge (distance between the rails) is 1520 mm in Mongolia and 1435 mm in China. Oops!

The rail industry realized long ago that, unless it settled on a standard, costly scenarios like this would repeat themselves ad infinitum. As a result, some 60% of railways worldwide, including those in China, now use standard gauge, ensuring greater interoperability and efficiency.

The in-car infotainment market should take note. It has yet to embrace a standard that would allow in-car systems to interoperate seamlessly with smartphones, tablets, and other mobile devices. Nor has it embraced a standard environment for creating in-car apps and user interfaces.

Of course, there are existing solutions for addressing these issues. But that's the problem: multiple solutions, and no accepted standard. And without one, how will cars and mobile devices ever leverage one another out of the box, without a lot of workarounds? And how will automakers ever tap into a (really) large developer community?

No standard means more market fragmentation — and more fragmentation means less efficiency, less interoperability, and less progress overall. Who wants that?

Is HTML5, which is already transforming app development in the desktop, server, and mobile worlds, the standard the car infotainment industry needs? That is one of the questions my colleague, Andy Gryc, will address in his seminar, HTML5 for automotive infotainment: What, why, and how?. The webinar happens tomorrow, November 15. I invite you to check it out.
 

QNX and Freescale talk future of in-car infotainment

Paul Leroux

QNX and Freescale enjoy one of the longest technology partnerships in the field of automotive infotainment. The roots of their relationship reach back to 1999, when QNX became a founding member of MobileGT, an industry alliance formed by Motorola (Freescale's parent company) to drive the development of infotainment systems.

If you've read any of my blog posts on the QNX concept car (see here, here, and here), you've seen an example of how mixing QNX and Freescale technologies can yield some very cool results.

So it's no surprise that when Jennifer Hesse of Embedded Computing Design wanted to publish an article on the challenges of in-car infotainment, she approached both companies. The resulting interview, which features Andy Gryc of QNX and Paul Sykes of Freescale, runs the gamut — from mobile-device integration and multicore processors to graphical user interfaces and upgradeable architectures. You can read it here.
 

Car Connectivity Consortium (CCC) MirrorLink meeting, Chicago, September 29, 2011

For those who aren't yet reset on "MirrorLink", it's the new term for what previously was called TerminalMode.  The name change is a definite improvement.  I informally polled people to ask them what they though when they first heard "Terminal Mode".  Basically the answers fell into two camps: either a telnet replacement or a disease you really don't want your doctor saying that you have. Neither sound like a real ringing endorsement!  MirrorLink as a term makes sense.  Good job CCC.

Here are some of my observations and notes from the CCC show in Chicago last week.

• MirrorLink will not be going away any time soon--there is enough industry momentum to keep it alive for a while.  Sounds like roughly 60% of the car makers and 60% of the mobile makers are behind it to some extent or another.
• QNX is very bullish on HTML5 as a replacement for MirrorLink-like features, but it doesn’t look like HTML5 is part of the future MirrorLink strategy at all.  Instead, they’re looking at HDMI or MDL—direct video from the mobile with a control channel.  This is a generic replacement for iPod out, and it's an approach that we've considered as well and will likely support, so this is a good alignment at least in direct video technology. Even though they don't see the wisdom of the HTML5 path yet (patience--they'll get there :-).
• OEMs don’t seem to realize how badly this will impact their revenue chain or are taking the "cross your fingers" approach.  Certainly many seemed to be focused solely on the value MirrorLink provides by enabling customers and building new markets.  I think it's somewhat Pollyanna-ish to not admit MirrorLink has the potential to completely decimate in-vehicle navigation uptake.  If I can bring my phone in for navigation for a half-way decent experience with a built-in screen, who's going to spend $3000 on a nav-only solution? 
• MirrorLink isn’t as focused as much on enabling third party apps (although they did talk about it), but more about mirroring custom-built phone apps into the car.  Everything that was demoed in the demo room breakout was a customized app that provided an integrated experience.  This is both bad and good.  Bad because it definitely reduces the short-term promise of opening up a huge third party ecosystem.  Good because I think it's the only reasonable way to go--there's really no other way OEMs can justify the liability of phone apps within the car, unless they can have some measure of control.
•  I still think that there's a significant amount of work they need to address safety concerns around driver distraction. MirrorLink the specification, and the general CCC communications contains "driver-safe" messaging.  However, my take is that the actual participation level people, especially on the mobile side seem to discount their accountability when you bring third party apps into the car, and nothing in the specification really makes it possible for an automotive outsider to make a car-safe app.  I highly doubt this approach will fly. The application level certification that is planned for a future MirrorLink 1.1 release seems almost a mandatory requirement before this issue can be put to bed.

Proposed app certification process

• Interestingly, almost every car company I talked to had a different take on how MirrorLink will impact their strategy—some see it as a low-end only play, but others see it as a high-end play.  There's still a lot of confusion as to where it slots into product lines.  I didn’t talk to anyone there who isn’t going to do it at all (not surprising given that the show was completely MirrorLink-focused), but some didn't seem to put a lot of weight behind it.  The perception I had was that some were doing it to "keep up with the Joneses."
• I give the CCC credit for realizing that MirrorLink has a lot of danger for the fragmentation whirlpool that has plagued Android releases and that makes Bluetooth interop the biggest nightmare for those who implement it and test it.  To that end, they're really trying to take this one head-on. It's still very early days to see if they will be successful, with the first MirrorLink 1.0.1 systems coming out in production.  (Alpine's aftermarket ICS-X8 earns that "first to market" distinction.) I hold out hope that CCC can keep MirrorLink interop from becoming a quagmire, but this is a bugger of a problem to fix in an area that tries to tie "slow-moving" car tech with the mobile space, so keep your eyes peeled...

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.