Your browser is not supported. Please update it.

25 June 2015

Amid sale talks, Nokia Here pushes standard for handling in-car sensor data

Nokia is searching for a new owner for its Here mapping division, and continues to add to the attractions for a potential buyer. This week, it published a set of specifications for integrating data from a wide range of in-car sensors via the cloud, aiming to set a standard way to address this challenge.

Here – richly functional and independent of any one mobile platform – has a real chance to challenge Google and become a de facto standard to power location-aware services. This is particularly true in the automotive sector, where Android and iOS are less established than they are in smartphones, and where the carmakers are keen to build in-car service platforms which they – not the mobile giants – control. Indeed, a consortium of automotive vendors remains the most likely buyer for the Nokia unit, a move which would build on Here’s existing deals in the sector.

Just developing feature-rich applications and back end engines is not enough to make a real impact on the internet of things (IoT), or on important segments of that, such as the connected car. Vendors need to create de facto standards with open developer links, thus embedding their platforms, and associated revenue-generating services, into a broad base, and forcing their rivals to play along.

There are plenty of areas where companies can attempt this feat – IoT connectivity, device management, APIs, messaging protocols and many more. An important one is a way to make sense of all the data from thousands of multifarious sensors in cars, homes or cities, to ensure that any application is able to tap into that in a uniform manner. Nokia Here aims to build that kind of framework for in-car data, and is starting with an interface specification geared primarily to road safety (though many other applications, such as traffic management and proactive driver directions, could benefit too).

The first generation spec handles data from sensors from multiple vendors, which would not otherwise be interoperable. This helps to update maps in near-real time to support live views of road and traffic conditions, based on the information from huge numbers of cars. That information, in turn can be used by a variety of traffic applications. In the future, evolved versions of such interfaces will be important to make the driverless car workable and safe.

Dietmar Rabel, Here’s product management director for automated driving, wrote in a company blog post that real time mapping will depend on a critical mass of sensors being connected, and that will only happen if there is a common way to handle the data they produce.

“If an OEM is only in a couple of thousand cars across Europe then a vehicle might only pass a certain location every two weeks and you can’t do any real time or near-real time processing or change detection with such limited data.”

Of course, there are always privacy issues attached to data being transmitted to the cloud for use by applications. Nokia insisted that its interface is currently focused on getting information from vehicles when a significant event is occuring, rather than permanently monitoring vehicles – but the potential for broader usage is clear, especially if it is in the hands of auto makers, which are seeking new ways to generate revenue from in-car platforms.

“We are defining that vehicles don’t send individual vehicle IDs so they aren’t traceable,” Rabel wrote. “This means that if the vehicle is sending some data today and then the next day, we will not know that it is the same vehicle. We would be aggregating across many submissions but not across a single individual.”

Nokia said that it is currently holding talks with a group of leading carmakers about the spec and will then invite other industry players to comment on it and possibly contribute to its development.

It seems likely that, among the automotive companies inputting to the interface specs, will be those which may also end up owning Here. Reports about who might buy the subsidiary, which Nokia indicated it would offload when it announced its bid for Alcatel-Lucent, have swirled ever since. Some candidates may be those looking to enhance a mobile platform. Microsoft might seek to acquire an asset which would actually be of greater value to it than the Nokia devices unit (some executives are said to have been angry that previous CEO Steve Ballmer failed to include Here in that deal). Other Here maps licensees such as Amazon would also be logical buyers.

But the smart money is on a consortium of German car manufacturers – Audi, BMW and Daimler, backed by some private equity money – although Nokia is said to be asking for a higher price than they had envisaged, at a reported $4.5bn. An interesting twist, according to Bloomberg sources, is that Chinese search giant Baidu could join this group and so secure a higher degree of influence than it would gain from a straightforward licensing deal, as it builds up its own broad mobile and IoT platform. Baidu had previously teamed up with a different group, including taxi app provider Uber and private equity firm Apax Partners, said the reports, but these have since pulled out, as have some other private equity players.

Nokia certainly won’t sell its jewel unless it can secure a high price, and the delays in announcing any deal may reflect a behind-the-scenes bidding war. CEO Rajeev Suri reiterated last week that sale was only one option being considered as part of the ongoing strategic review of Here.