In September, Carmesh had the opportunity to present at the SmartDevCon2 conference. This is a developer focused conference which is looking to a future comprised of very many smart devices: the conference focuses on innovative tools and technologies appropriate for this new context. With Carmesh focused on the Connected Car – which will clearly have more intelligence – this conference is very much relevant to the project.
The conference itself was a modest international conference – some of the speakers had travelled quite a distance to get there – with about 100 attendees. Most of the attendees came from the mobile development arena and had varying levels of experience.
We presented our view of the evolution of the Connected Car. In essence, we see a HTML5 based OBU talking to a phone where most of the intelligence lies and this connects to a cloud backend (more on our vision here). We also talked about some particular technologies we think are exciting and hold particular promise in this area.
As the audience was mostly comprised of mobile developers, the auto space was something which was new to them; while there was some interest in our talk, I think it’s fair to say that novel mobile platforms were in more demand. It did, however, give us a good platform to get out in front of developers to promote the Carmesh vision.
We had the opportunity to attend the Automotive Linux Summit in Edinburgh in October 2013. It’s an industry focused event which is tied in to Linuxcon Europe.
The event had about 100 attendees, from a mix of component suppliers, OEMs, Tier 1s and smaller guys working on some specific automotive software aspects.
It was our first time attending this conference, so we had no idea what to expect. Generally, we got the impression that the sector is in the midst of quite a big transition, moving from very bespoke, specialized software and hardware solutions to a much more standardized approach based on Open Source and open standards. While this in itself is very significant, it’s the greater implications of this – an increased rate of innovation – which is both the threat and opportunity that is simultaneously causing discomfort and excitement right now.
The range of topics covered at the Summit is impressive – ranging from software licensing in Open Source to mapping to mobile integration to new virtualization platforms. Any one of these alone could have its own dedicated event.
The highlight of the event yesterday was definitely the very engaging Matt Jones from Jaguar-Land Rover who argued cogently that the sector has the opportunity to greatly increase its rate of innovation. Noting that timelines for introduction of software into cars can be about 39 months and small companies can bring production software out in 18 months or less, highlights the challenges for small companies with new ideas to engage in the automotive space. Also the idea of having rapid software update and distribution cycles should increase innovation and offer a much better experience to the car user overall.
We learnt lots from day 1 and met loads of very interesting people. Let’s hope day 2 will be equally as interesting…
In a previous post, we described how we see the used car market changing as the Connected Car evolves. Here, we focus on the Car Rental sector with particular emphasis on how data collection can impact the sector. (Note that while we focus on the power of the data here, we do view the Connected Car as offering more – see our vision post for details).
The car rental sector is very interesting from a Connected Car point of view from two particular perspectives. Firstly, the Connected Car sector is comprised of quite a few big organizations who can roll out Connected Car technology across their entire fleet quite easily. Secondly, the car rental sector is seeing some disruption with peer-to-peer solutions offering lower cost services – the Connected Car fits neatly into this paradigm shift. Both of these perspectives are examined a little further below.
The NS-3 simulator tries to mimic as close as possible the journey of a packet through the IP-stack’s layers. Passing the packet from one layer to the next one is done through Callbacks or functions which access the packet. In this way, NS-3’s callbacks are taking successively control over the packet, which remains static.