ENIVI-OIC call 12 Feb 2016

Roundtable
Sanjeev (Samsung Open Source Center)
GENIVI: Magnus (RVI Expert Group Lead), Gunnar (System Architecture Team Lead), Philippe (Program Manager)

Support materials: new Samsung presentation attached - high-level system architecture for the demo, demo scenarii proposal, work breakdown proposal

OIC & RVI resource model mapping
Magnus: had a quick look at it, should not be too hard, identified 2 approaches for implementing the mapping
approach #1: have a OIC plugin inside RVI
approach #2: have a gateway (with a dedicated address) doing the routing OIC domain and genivi RVI domain
Magnus needs to put this on paper
Sanjeev: in approach #1 which is a direct mapping, are the ports dynamically used ? answer: yes

Samsung presentation
Sanjeev: shows the architecture of the BMW/Samsung demo at CES 2016, the demo used the BMW cloud service infrastructure. The smartphone had to be in the car since it was the actual gateway between the car and the home. 
Sanjeev: shows the proposed architecture for the genivi-oic demo, it is proposed to have a router connected to the local network of the home (bottom right on slide #6)
discussion on how to route communications between the GENIVI in-vehicle head unit and the OIC enabled home
Magnus: how to route back messages from the home to the in-vehicle head unit ?
Gunnar: what the data router shown in the head-unit side comes from ? answer: it is part of RVIcore

*TODO* Magnus - update the slide deck with a system architecture diagram (identifying the software components used) and message sequence diagrams

for Magnus :-) comparison of MSC with UML: https://en.wikipedia.org/wiki/Message_sequence_chart#Comparison_to_UML

Sanjeev: shows the proposed demo scenario
discussion on feasability of the scenario
Magnus: we will need to have a simulator of vehicle position
Philippe: genivi has one if it helps - look at http://git.projects.genivi.org/?p=lbs/positioning.git;a=tree;f=log-replayer;hb=HEAD

Demo deployment
Magnus: how would Samsung like the demo to be deployed ?
Sanjeev: we would expect a car, Samsung would bring a 3D model of a house
Philippe: genivi can host only two cars at the Spring AMM (for security reasons), we expect one car from PSA (still to be confirmed) and one car from JLR, in case PSA cannot show their car, there might be a second car from JLR.
Magnus: JLR has already planned to show 2 demos on the JLR car; it would be difficult to show a 3rd demo on the same car, needs to check with Matt
Sanjeev: a fallback solution is to do a demo on a table with a head unit and the model of the house

*TODO* Philippe contact Mike Nunnery (marketing) to secure a (large) table for the genivi-oic demo in the showcase

Sanjeev: we would like to have a self-contained infrastructure for the demo, i.e. have a local unique access point (we do not want to rely on cloud services)
Magnus: agreed, this is the way we intend to the JLR demo

Sanjeev: shows the proposed work breakdown and assignment of activities to OIC and GENIVI
Magnus: will check for the availability of a resource for the RVI-OIC gateway work
Sanjeev: Samsung has involved Philippe Coval in the demo work, Philippe Coval has already completed a preliminary proof-of-concept (https://vimeo.com/154879264#iotivity-genivi-demo-platform-20160210rzr)
Sanjeev: please invite Philippe Coval to the next sync call.
Magnus: leaves the call
Sanjeev: asks about the status of RVI integration into GDP
Gunnar: there might be prototype work done at JLR on this, this is to be checked with Magnus

Next steps
Sanjeev will update the slide deck and also create a doc from the slide deck and the meeting notes taken by Philippe
Magnus will update the slide deck with system architecture and sequence diagrams
next call is on Friday 19 February - 7am CET, a calendar invite will be sent