Skip to end of metadata
Go to start of metadata
GENIVI-OIC call 19 Feb 2016 - 7am CET

Roundtable
Sanjeev (Samsung Open Source Group - OSG), Philippe Coval (Samsung OSG)
GENIVI: Magnus (RVI Expert Group Lead), Philippe (Program Manager)

Support materials: new Samsung presentation attached - message sequence diagrams to be reviewed

slide #6 - RVI OIC gateway & rule engine
Magnus: presents the gateway functionalities (see also message sequence diagrams)
Sanjeev: do we consider persistence is in scope ?
Magnus: we may have just simple configuration files in the gateway
Sanjeev: what is the smart home box in the vehicle side ?
Magnus: this is a Qt/Qml ui running on the GDP

slide #9 - Sequence Diagram: Vehicle -> OIC
Magnus: <register static RVI message service> supports the registration of a callback in RVI
Sanjeev: agrees on the sequence diagram
Magnus: <send msg> will send only preconfigured text as the baseline functionality, if we have time, we may go to dynamic text

slide #10 - Sequence Diagram: OIC -> Vehicle
Magnus: same as above, just the other way around
Sanjeev: in the RVI-OIC gateway we need to host and map the services provided by the head unit so that they are visible by the OIC side, we need a description of the service parameters and resources (as a json representation of the resources and how they are controlled)
Philippe Coval: can we create OIC resources on the fly when RVI registers with the gateway ?
Sanjeev: OIC client on the diagram is basically a Gear S2 (smart watch) which is supposed to discover a HVAC resource on the vehicle side
Philippe Coval: what is the use case then ?
Sanjeev: we need to clarify how the hosting of the OIC resource is done within the RVI-OIC gateway
Sanjeev: how is the HVAC represented in the gateway ? 

*TODO* Sanjeev - figure out how to host the OIC server in the gateway ?

Sanjeev: rule engine role is to aggregate devices together and provide a more abstract vision of devices, the gateway is actually performing the mapping of services

slide #12 - #1: RVI API: Location Update (Vehicle -> OIC) 
straightforward

slide #13 - #1: RVI API: Location Update (Vehicle -> OIC) (device side)
Magnus: agrees with the way Sanjeev presents the update sequence

slide #15 - #2:  Location Update  (OIC -> Vehicle)
taken offline by Samsung

slide #17 - #3 : RVI API: HVAC
HVAC registers a service name
the call to the service is triggered by the rule engine

slide #21 - #4 : RVI API: Message
this is the shopping list use case

Deployment & test
Magnus: JLR can offer a test server as soon as Friday 19 Feb, Samsung needs just to send a public key to get a SSH access

Resources
Magnus: resources are not confirmed on JLR side due to the many priorities for preparing demos at the Spring AMM

Jira tracking
discussion on how to organize and track activities in Jira
preference for a basic setting (no Kanban or Sprint at this step)

Next steps
Sanjeev will update the slide deck using the meeting notes taken by Philippe
Philippe will create the Jira project and create issues corresponding to AI table on slide #40
Magnus will provide access to the test server
next call is on Thursday 25 February - 7am CET, a calendar invite will be sent

note: notes will be uploaded on the public wiki at: https://at.projects.genivi.org/wiki/display/WIK4/GENIVI-OIC+Demonstrator

Adjourned: 8am CET








  • No labels