The automotive API will be an example for a convergence of heterogeneous industries : IT and automotive fields. The knowledge from the two fields should be closely streamlined with each other.
The API should provide a uniform way to handle the car devices such as door, speedometer, car diagnostics module and so on. Since there are various communication channels including GPIO, CAN, MOST, and so on, the API itself should provide an abstract way to be neutral to various configurations. GCF(General Connection Framework) introduced in J2ME can be used as an building block to implement the communication protocols. Furthermore, some kind of layered approach similar to communication protocol stack (logical device layer, physical device layer, and connection layer) might be necessary for this kind of abstraction. As a start point for the discussion to interface with car, the OBD-II specification (http://www.obdii.com) can be used to define the basic interface, because all cars in US have this interface by the regulation. A user could get status information about power train, engine, tiers etc. through embedded devices using API that based on the OBD-II standard.
No comments:
Post a Comment