And finally here is the last part of the article about capsFramework.
The app CarProﬁleBook is an application that grants access to the available sensor data. It lists all the sensors of the vehicle and displays the sensor data for the
selected sensors. Figure 6 shows a screenshot of the app. On the left hand side of ﬁgure 5.1 one can recognize a list of sensors which are
available in the car. Another list, containing the sensor data, is shown on the right hand side if a sensor is selected.
Now comes part 3 of my excerpt from capsFramework.
The necessity of capsFramework constitutes with the request to have a framework that allows the user as well as the developer to create or use apps for vehicles with comparably small eﬀort. Though, the developers shall be able to access sensor data straightforward with the use of APIs. The user shall have a simple to use platform in order to manage and access the diﬀerent apps. The framework shall also follow
the idea of the web of things. The vehicle, and so all its data, shall be available for the vehicles owner and also for everyone or everything that are allowed to access it. capsFramework shall oﬀer all the previously mentioned goals by utilizing proven and standardised protocols, applications and programming languages.
The following technologies are used: JBoss Application Server, Apache HTTP Server, DatabaseManagement System PostgresSQL,GWT,HTML, SOAP, REST and Java.
Figure 1 visualizes the interaction of the components in the capsFramework.
As you can see in ﬁgure 1 there are three main blocks: Server block including the two servers JBoss AS and Apache HTTP Server as well as the Sensoric Reader, Postgres database, caps and apps. The Simulation block includes CarSim which can produce sensor data and broadcast it. Finally the Sensor API block has got the elements capsWS and capsREST which can initiate a communication to the database. The Sensoric Reader consumes sensor data, for example from CarSim and sends this data to the database which stores it. caps has got an amount of apps and it can access the database. Every app can use the elements inside the Sensor API block in order to retrieve (sensor) data from the database. The previously named elements of capsFramework are described in the next sections.
Audi A8 – Google Earth Support
Audi announced the cooperation with Google on the 16th December 2009. The model Audi A8 will soon include well-known Google services. A connection to the services can be established via the Bluetooth car-telephone which has got a GPRS/EDGE data transfer module integrated. The driver will have got access to Google Maps and will be able to search for diﬀerent addresses displayed on a map. A UMTS module, which will be able to transfer bigger data packages, shall be added to the Audi A8 in the year 2010. So that Audi can provide Google Earth, that presents three-dimensional satellite and aerophoto of places, for the driver [Auda] [Audb].
BMWConnectedDrive is a system consisting of ﬁve components actively supporting the driver. ConnectedDrive is divided into the following ﬁve components: BMW Assist, BMW Online, BMW Tracking, BMW TeleServices and Internet in the vehicle [Cond].
Today I present the first excerpt of my latest thesis called (capsFramework) Car ApPlication System – Framework: A Framework For Visualizing Sensordata With Apps. Contact me, if you are interested in the complete text and I will send it to you.
Before you start reading this article let me show you a demo video of the system which is described below.
How is it possible to create a system using the information that is generated by a vehicle in order to support the driver actively?
This thesis addresses this topic and presents an approach to realize such a system. A platform will be described that can access the sensor data of a vehicle and makes them accessible. Applications are deployed being able to work with the sensor data. Therefore, a framework will be presented that uses diﬀerent technologies like application servers, databases, web services, Google Web Toolkit – and Java applications. These technologies will be presented and described. It will be explained how the framework is arranged and how the several components work together. Additionally, examples of applications will be shown that are running on the platform and use the framework.
Again, the following paragraphs are parts from one of my theses. If you are interested in the complete article, in which it is described in detail how the implementation was done, you can write me an e-mail.
The aspect-oriented programming (abbreviated AOP) is an expedient to solve the problems when trying to modularize software. It focuses the problem of cross-cutting-concerns (abbreviated CCC).
There are already several programming languages which permit the developer to program in an aspect-oriented (abbreviated AO) way. Though, AOP is not every time immediately supplied by the developers of the language. It is often implemented after the ﬁrst versions of the language are released. This implementation can be done in diﬀerent ways whereupon every implementation has it’s advantages and disadvantages.
This work implements aspect-oriented constructs in three ways for the programming language Ruby.