In Carmesh, we are considering urban wireless mesh networks (WMNs) as one option for vehicular connectivity. This kind of network has emerged as a highly flexible, reliable and cost efficient solution for wirelessly covering large areas. It provides low-cost Internet access through multihop communications.
While working on the first version of carmesh Android application I had some issues with co-ordination between the app and an embedded Webview browser. The issues manifested in an authentication process which had to run in an embedded browser before handing control back to the application.
Yesterday I had an opportunity to present Carmesh implementation work and project vision on Connected Car to valuable technical audience at Google Developers Group in Dublin. I also had a chance to listen to two presentations and engage further discussions.
Google Developers Groups are worldwide communities which are interested in technologies provided by Google and ways to leverage them, but in most cases are not Google workers (Googlers). It was my first presentation to such large audience from industry and I find it very valuable.
(This is the first in our series of posts on issues we found in our implementation work).
Short blog post on an issue we found with a library we’re using…
In carmesh, we’re working on accessing some social services on the user’s behalf. One technology we’re using to access Oauth’d services is sanction – it’s a handy python library which takes care of authentication and provides a nice authenticated way to interact with services.
The CarMesh project is funded under the European Union Marie Curie Industry-Academia Partnership Pathways (IAPP) umbrella which encourages people from industry and academia to work together and to engage by means of joint research – an essential aspect of this scheme is that partners from different countries exchange staff via secondment. This short blog post is about my experience of my secondment to an SME in Poznan, Poland as an academic researcher who just finished his PhD in Ireland and who is originally from in Germany.
While searching for information on possible services/apps future drivers would really enjoy getting while in their car, I came across this interesting market research report from Arbitron. The findings are based on a broad-based survey with a total of 1,858 peoples interviewed in the US. The sample is large enough to reveal some general trends, despite the fact that it not clear whether the sample is representative of drivers distribution across US – some findings do suggest that the sample is heavily concentrated in sub-urban areas where driving is King!
In Carmesh, we are looking at different networking solutions for delivering services to cars, mainly in an urban enviroment. One connectivity solution is wireless mesh networks. One critical aspect of Wireless Mesh Networks (as well as other networks) is routing. That is the focus of this post.
The digital services that can be provisioned to the car are many and diverse. Let’s imagine a driver (and passengers) of a car connected to the Internet. Every move of the car is fed back to Internet services such as Yelp, Opentable, GMaps, GoCallendar, etc making received services ever more relevant and frictionless. Clearly, the use-case possibilities are endless and the most important are captured in a previous post. In Carmesh, we believe that VoIP services will have a reasonable future in the car. Besides the traditional VoIP chat services (e.g., Skype, Hangout, etc), there are a plethora of services that could be built around tourisms. An example here is a city guided tours service, where a user receives a voice description of landmarks and point of interests depending on its location and driving direction. It is easy to imagine other rich content that can come with the voice such as detailed maps, videos for in-depth coverage of landmarks, reviews, etc.