Meeting minutes
Conexxus use cases and plugfest participation
Lagally: possibility of Conexxus' participation in Plugfests in the future?
David: would think about that
Lagally: maybe we could work on some topic on simulations
David: Jack, do you have somebody could help in your mind?
Jack: yeah
Lagally: simulated behavior like state change
… on and off
… something like a pump
… handling fluid level
David: maybe a group meeting would be helpful
Lagally: next Plugfest would be in March next year
David: right time frame for us too
Lagally: we should talk about the next steps
Minutes
Lagally: (goes through the minutes)
<mlagally> typo with "moratorium"
fixed
(some discussion on time synchronization)
(also about consolidating multiple clock ticks using events, etc.)
Lagally: any problems?
(none)
approved
Lagally: had nice discussion on time series data as well
David: first thing wanted to show is the chart
… I showed last time
… [Device comparison]
… first column is IoT Primary devices
… it is important to clarify what the devices, e.g., a camera, do
… and then today's slides
… [WoT and "Pseudo-devices"]
… fed data from video/audio input streams
… a camera provide video streams
… and smart speakers provide audio streams
… "pseudo-devices" then substitute computation resources for discrete devices
… client devices understand IoT languages
… security implication of storing the video data on the cloud side
Lagally: camera taking infra-red data possibly
… every certain time period
… that is my image
David: we call it (infra-red) heat map
… see the store's layout in different color depending on the temperature
… [Simple Schematic]
… video -stream- processor - WoT Facade- clients
… the ability to reuse the capability
… [TD: Cooler Door]
… [Pseudo-devices in action]
… transport mechanism may be Web Socket or anything
… (connection between Camera and Edge AI Processor)
… the first consume opens the door
… event invoked
… the edge AI get the event
… the POS System only gets the notification
… a lot of legacy devices need upgrade paths
… skimming devices to get credit data, etc.
… flexible AI-based system
Jack: they can leave the existing devices
… based on regulatory, safety, etc.
… might have some push back
David: there is a study done on transition to EMV
Lagally: question about the maintenance event
… this is a boolean event
… [TD: Cooler Door]
… any insight about the possible data structure?
David: not thinking about the detail, but something like facing one direction or another
Lagally: another question on the sequence diagram
… [Pseudo-devices in action]
… encrypted data connection with the AI processor?
David: problem with the API ecosystem
… not all the edge devices don't have HTTPS capability
… the connection here is protected by OAuth2
… also TLS
… this side (AI Processor on the right side) is protected
Lagally: do you have bandwidth to put this idea into a use case?
David: need somebody
Jack: next week?
… will catch up with David
Lagally: aob?
(none)
[adjourned]