Discussion:
Architecture Proposal for Vehicle Network APIs of MeeGo IVI
Grigory Abuladze
2011-07-20 14:49:09 UTC
Permalink
Hi



With regards to this

http://lists.meego.com/pipermail/meego-ivi/2011-July/000652.html

http://wiki.meego.com/In-vehicle/Roadmap/Vehicle_Network_API



A few comments:

1. Possible Use Cases:

.. Pay-As-You-Drive : Insurance companies can provide App, which reports
the driver's driving habits with his consent. The data can be used to
discount insurance fee...

Should be read as "The data WILL BE used to INCREASE insurance fee."

Don't even mention all connected to privacy and so on :)



2. CAN stack.

Do you hear something about

SocketCAN http://en.wikipedia.org/wiki/SocketCAN ?

Which is:

- mature, comes from real automotive

- integrated into kernel

- ndev based, not chardev

- has build in virtual CAN adapter

- has HW specific drivers support from almost all CAN HW modules
manufacturers



Shouldn't we just reuse already available and easily integrable
technology instead of reinvent CAN-stack wheel again?



Grigory Abuladze



Application Solutions (Electronics and Vision) Limited.
Tel: +44 (0) 1273 409147



Please consider the environment before printing this document.



This message and any attachments may be confidential and contain
privileged information.



Legal Disclaimer: Any views expressed by the sender of this message are
not necessarily those of Application Solutions (Electronics and Vision)
Limited. and whilst every precaution has been taken to ensure it is
virus free, we accept no responsibility for any damage which may occur
from its use.
Information in this e-mail may be confidential and is for the use of the
intended recipient only, no mistake in transmission is intended to waive
or compromise such privilege. Please advise the sender if you receive
this e-mail by mistake.



This communication was sent from Application Solutions (Electronics and
Vision) Limited. Registered office: The Riverside Centre, Railway Lane,
Lewes, East Sussex, England, BN7 2AQ. Company Reg. No. 6437845
Kevron Rees
2011-07-20 17:00:23 UTC
Permalink
Post by Grigory Abuladze
Hi
With regards to this
http://lists.meego.com/pipermail/meego-ivi/2011-July/000652.html
http://wiki.meego.com/In-vehicle/Roadmap/Vehicle_Network_API
.. Pay-As-You-Drive : Insurance companies can provide App, which
reports the driver’s driving habits with his consent. The data can be
used to discount insurance fee…
Should be read as “The data WILL BE used to INCREASE insurance fee.”
Don’t even mention all connected to privacy and so on :)
2. CAN stack.
Do you hear something about
SocketCAN http://en.wikipedia.org/wiki/SocketCAN ?
- mature, comes from real automotive
- integrated into kernel
- ndev based, not chardev
- has build in virtual CAN adapter
- has HW specific drivers support from almost all CAN HW modules
manufacturers
Shouldn’t we just reuse already available and easily integrable
technology instead of reinvent CAN-stack wheel again?
I believe the goal is to build an API on top of CAN to abstract OEM
specific implementation/protocol details away from applications.
SocketCAN can very well be used in conjunction with this API to do the
low level reading and writing to the bus. Otherwise, SocketCAN is not
terribly useful as SocketCAN doesn't understand what information is
available in any given vehicle.
=?ks_c_5601-1987?B?udrBvryxKEp1c3RpbiBQYXJrKQ==?=
2011-07-25 06:24:21 UTC
Permalink
Hello,

I'm sorry for the late feedback.

1. Possible Use Cases:

As you said, there can be several issues about this use cases.
Nevertheless, its realization looks very high in the near future.
What is not in doubt is that it'll be able to be performed with only
driver's consent.
It's similar way to that of some applications which seek the approval of
using position data in smart phones.
Thus, we need to provide this mechanism as a platform's infrastructure.

2. SocketCAN

Kevron gave us the correct answer. I appreciate it.
I agreed that we don't need to make the same thing again. But, SocketCAN
seems not profit to my proposal.
Anyway thank you for your information.
I look forward to your continuous interest and advice.

Best regards,
Justin

-----Original Message-----
From: meego-ivi-***@lists.meego.com [mailto:meego-ivi-
***@lists.meego.com] On Behalf Of Kevron Rees
Sent: Thursday, July 21, 2011 2:00 AM
To: meego-***@lists.meego.com
Subject: Re: [MeeGo-ivi] Architecture Proposal for Vehicle Network APIs of
MeeGo IVI
Post by Grigory Abuladze
Hi
With regards to this
http://lists.meego.com/pipermail/meego-ivi/2011-July/000652.html
http://wiki.meego.com/In-vehicle/Roadmap/Vehicle_Network_API
.. Pay-As-You-Drive : Insurance companies can provide App, which
reports the driver��s driving habits with his consent. The data can be
used to discount insurance fee��
Should be read as ��The data WILL BE used to INCREASE insurance fee.��
Don��t even mention all connected to privacy and so on :)
2. CAN stack.
Do you hear something about
SocketCAN http://en.wikipedia.org/wiki/SocketCAN ?
- mature, comes from real automotive
- integrated into kernel
- ndev based, not chardev
- has build in virtual CAN adapter
- has HW specific drivers support from almost all CAN HW modules
manufacturers
Shouldn��t we just reuse already available and easily integrable
technology instead of reinvent CAN-stack wheel again?
I believe the goal is to build an API on top of CAN to abstract OEM
specific implementation/protocol details away from applications.
SocketCAN can very well be used in conjunction with this API to do the
low level reading and writing to the bus. Otherwise, SocketCAN is not
terribly useful as SocketCAN doesn't understand what information is
available in any given vehicle.

_______________________________________________
MeeGo-ivi mailing list
MeeGo-***@lists.meego.com
http://lists.meego.com/listinfo/meego-ivi

Loading...