Re: Streaming sensor support?

It may well not be a good match for our needs. Your proposal, reviewing
groups and individuals to try to meet at TPAC and recollection that
Continental's previous interest in WebRTC for data streams is what
prompted me to present it for consideration.

It might be a suitable streamProtocol among several, not appropriate or
workable but potentially replaced by something more appropriate in the
future. My understanding is the stream contents can vary and not
restricted to multimedia communication.
 

On Thu, 2018-10-04 at 11:19 +0000, Björkengren, Ulf wrote:
> MO׾M8מ<۾�QEMA{tӍDQ83L(#After looking at this page
> https://www.innoarchitech.com/what-is-webrtc-and-how-does-it-work/
> one question is whether webRTC may be overqualified for our use
> cases? 
> Can it be efficiently scaled down to what we need?
> Or do we need "real-time peer-to-peer multimedia communication"?
> 
> BR
> Ulf
> 
> 
> Ulf Björkengren Ph. D.
> Connectivity Strategist
> 
> M +4553562142
> ulf.bjorkengren@volvocars.com
>  
> VOLVO CAR CORPORATION
> 94014 Lund R&D Tech Center 
> Frederikskaj 10A
> Copenhagen, Denmark
> volvocars.com
> 
> 
> -----Original Message-----
> From: Björkengren, Ulf [mailto:ulf.bjorkengren@volvocars.com] 
> Sent: den 4 oktober 2018 10:59
> To: ted@w3.org; public-automotive <public-automotive@w3.org>
> Subject: RE: Streaming sensor support?
> 
> Hi,
> 
> Regarding questions to Dominique, I think we could describe the idea
> of using a VSS node to configure a WebRTC session. 
> If we follow my proposal to have a key named streamConfig, and its
> value pair to be a JSON string, in its turn maybe containing
> "streamProtocol" = "webRTC"
> "streamSpecificConfig" = "xxx"
> Then then question could be how should xxx look like to contain the
> data necessary to set up a webRTC session (using a key-value pair
> syntax)? 
> 
> Other questions could be about security in this context. Key
> management for encrypted streams, ...
> 
> WebRTC resilience when run over an unreliable transport channel? 
> 
> BTW, the link
> 
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FAPI%2FWebRTC_API%2FUsing_data&amp;data=02%7C01%7Culf.bjorkengren%40volvocars.com%7Ccbed931eb04d4b2e1d3a08d629d7c1ad%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636742403973214038&amp;sdata=oMMnDwWKLvH9RMPb%2FpSoNV2A4M%2BS%2FXVCX3I8xACoVJg%3D&amp;reserved=0
> seems broken.
> 
> BR
> Ulf
> 
> Ulf Björkengren Ph. D.
> Connectivity Strategist
> 
> M +4553562142
> ulf.bjorkengren@volvocars.com
>  
> VOLVO CAR CORPORATION
> 94014 Lund R&D Tech Center
> Frederikskaj 10A
> Copenhagen, Denmark
> volvocars.com
> 
> 
> -----Original Message-----
> From: Ted Guild [mailto:ted@w3.org] 
> Sent: den 2 oktober 2018 16:35
> To: Björkengren, Ulf <ulf.bjorkengren@volvocars.com>; public-
> automotive <public-automotive@w3.org>
> Subject: Re: Streaming sensor support?
> 
> Excerpt of an exchange with a colleague below and pointer to further
> reading regarding potential applicability of WebRTC for data
> streaming to/from vehicle. Continental, who is presently inactive
> within W3C, had previously expressed interest in WebRTC for this
> purpose.
> 
> To keep things together here are the minutes for this topic as
> prompted by Ulf's email.
> 
> 
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F09%2F11-auto-minutes.html%23item04&amp;data=02%7C01%7Culf.bjorkengren%40volvocars.com%7Ccbed931eb04d4b2e1d3a08d629d7c1ad%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636742403973214038&amp;sdata=COrxnXRXiMl0fLvW91kcglMjoTmALlyIXWD7Ccwnzbo%3D&amp;reserved=0
> 
> Dominique, who leads WebRTC, could potentially join us at TPAC to
> discuss further and would like us to consider explicit questions we
> might have of him. 
> 
> On Thu, 2018-09-27 at 16:01 +0200, Dominique Hazael-Massieux wrote:
> > Le 19/09/2018 à 18:53, Ted Guild a écrit :
> 
> []
> > > Also any primers on data streams in
> > > WebRTC or pointers to other potential auto/WebRTC intersections 
> > > would be appreciated.
> > 
> > 
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FAPI%2FWebRTC_API%2FUsing_data&amp;data=02%7C01%7Culf.bjorkengren%40volvocars.com%7Ccbed931eb04d4b2e1d3a08d629d7c1ad%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636742403973214038&amp;sdata=oMMnDwWKLvH9RMPb%2FpSoNV2A4M%2BS%2FXVCX3I8xACoVJg%3D&amp;reserved=0
> > _channels is a reasonably good technical intro. That being said,
> > at 
> > the very high level, WebRTC data streams are an exact replica of
> > Web 
> > sockets, with the addition of being configurable to be UDP-like
> > (where 
> > web sockets can only be TCP-like, i.e. ordered and reliable).
> > 
> > There are more tentative discussions to design WebRTC data streams 
> > built on QUIC, but I'm not sure how directly relevant to auto that 
> > would be.
> > 
> 
> 
> 
> On Tue, 2018-09-11 at 13:38 +0000, Björkengren, Ulf wrote:
> > Hi,
> >  
> > I happened to look at 
> > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2F5g-ppp.eu%2F5gcar%2F&amp;data=02%7C01%7Culf.bjorkengren%40volvocars.com%7Ccbed931eb04d4b2e1d3a08d629d7c1ad%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636742403973214038&amp;sdata=G2lD5mbtZdU%2B0dQ2ArL0qeTQm5ISE1hqFsaOcODBwdk%3D&amp;reserved=0
> > , and saw that they 
> > describe use cases where one car transmits a video stream showing
> > what 
> > is in front of it, to cars behind it. Which got me to think about 
> > supporting streaming sensors in our API.
> >  
> > I do not think we should try to invent any new streaming protocol,
> > the 
> > idea I got was to use our API as the “control channel” for setting
> > up 
> > the video stream (using any established streaming protocol). This 
> > could be realized by adding a new value to the “function” key that
> > I 
> > have proposed to add to VSS, the value being called e.g. 
> > “streamsensor”, and the add a new key with the name
> > “streamconfig”, 
> > having as value a JSON-formatted string containing the data needed
> > to 
> > connect to the streaming server.
> >  
> > I hope to get feedback to this idea at the WG meeting todayJ.
> >  
> > BR
> > Ulf
> >  
> >  
> > Ulf Björkengren Ph. D.
> > Connectivity Strategist
> >  
> > M +4553562142
> > ulf.bjorkengren@volvocars.com
> >  
> > VOLVO CAR CORPORATION
> > 94014 Lund R&D Tech Center
> > Frederikskaj 10A
> > Copenhagen, Denmark
> > volvocars.com
> > 
> >  
> 
> --
> Ted Guild <ted@w3.org>
> W3C Automotive Lead
> 
https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org&amp;data=02%7C01%7Culf.bjorkengren%40volvocars.com%7Ccbed931eb04d4b2e1d3a08d629d7c1ad%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636742403973214038&amp;sdata=Ca%2BcGQJQGa0B7FTjVW6trHY9NRU8fYBk3ZQJ4b35bs4%3D&amp;reserved=0
> 
-- 
Ted Guild <ted@w3.org>
W3C Automotive Lead
http://www.w3.org