Hi,
Thank you both, for the encouragement and the offers of support.
> -Original Message-
> From: Jialin Qiao
> Sent: Tuesday, June 18, 2024 9:50 AM
> To: dev@iotdb.apache.org
> Subject: Re: Introducing Apache IoTDB use in COVESA Central Data Service
> Playground
>
> Hi,
>
> Glad to see the integration!
> Welcome and feel free to ask :D
>
> Jialin Qiao
>
> Pengcheng Zheng 于2024年6月15日周六 04:38写道：
> >
> > Hi Stephen,
> >
> > Very exciting project!
> >
> > Thanks for sharing the details of COVESA/CDSP. I remember that you asked
> > some questions in Slack several months ago, and seems that you have made
> > great progress ;-)
Yes, originally I had some questions about running IoTDB on embedded h/w and
the answers helped me commit to using IoTDB in the Playground.
BTW as part of the project I have done some work integrating IoTDB to other
technology:
1) COVESA and the W3C co-developed a REST-like get/set/sub API for accessing
vehicle data in-vehicle called VISS. VISS has a reference implementation
maintained in the VISSR project that supported SQLite and Redis as data
store backends. I upstreamed support for VISSR to also support IoTDB.
2) The Playground includes a bridge for streaming real car data from the
RemotiveLabs virtual signal platform in the cloud into IoTDB. It has a
very simple implementation currently for the IoTDB connection but it has
no requirements on any other part of the Playground and could be a useful
example to anyone wanting to using RemotiveLabs with IoTDB.
> >
> > IoTDB has already proved its excellence in the scenario of connected
> > vehicles before, and the key questions you've listed in the
> > presentation happen to be exactly what IoTDB & TsFile are addressing,
> such
> > as data syncing between all touchpoints/ bidirectional sync/ permissions
> &
> > privacy/ model updating/ subscription, etc.
> >
> > Also your ideas of the deployment in Docker and edge-cloud sync (if my
> > memory serves me right..) shall benefit a lot from IoTDB.
Yes, IoTDB has many features that made it attractive for me to use it in
the Playground. I am sure I will have questions as the project progresses
Especially, I would like to leverage the greater IoTDB experience here to
check we are using it effectively. So please excuse the odd basic question.
Over the last year I have looked through the presentations on the IoTDB website
and occasionally checked back for updates. Including the Chinese language
ones where I have been able to translate. I remember seeing some mentions
of IoTDB implementation in automotive but not many details. If I remember
correctly there was a major instance for a telematics use-case. I also saw
that Table 4 of the IoTDB paper from SIGMOD 2023 listed three automotive
deployments.
If you have details of IoTDB automotive deployments I would be very interested.
> >
> > Hopefully IoTDB could support the CDSP project well and help transform
> the
> > "Playground" to POC - and finally from theory to practice.
I think it will. Put simply the Playground is a toolset of Lego pieces.
These pieces are intended to be connected in a range of ways to create
PoCs or examples of logical concepts large and small and prove them out
in implementation. Hence "Playground". This is not a project to make a
specific middleware 'product' or address a specific singular use-case.
At least in the current project setup.
The open source community aspect of COVESA means for effective collaboration
we need to also support diversity in architecture. In-vehicle architecture is
very complex and OEM A will make different choices to OEM B.
So, production will be a second step for individual companies to take
with their partners suited to their architectural and purchasing decisions.
That said, of course the advantage of using proven technology like IoTDB
is that the path to production is there.
> >
> > Looking forward to your updates!
Thanks.
Best Wishes,
Stephen Lawrence
> >
> >
> > Best Wishes,
> > Pengcheng Zheng
> > Timecho Europe
[snip]
