[Fiware-robotics] Robot characteristics

[Luis López Fernández]

Hi Roberto,
Please, take into consideration the following information for having an understanding on how to use Kurento:

Kurento is:
- A server infrastructure (it receives streams from clients and "do things" with those streams such as transcoding, processing, recording, distributing, etc)
- A WebRTC capable server (it's capable of receiving WebRTC streams, among other types of streams)

Kurento is not:
- A WebRTC client (it cannot "open a webcam" and send the stream to a remote party)


Hence, in your architecture, you need two ingredients:
- A WebRTC client catching the stream from a Camera and sending the stream using WebRTC standard protocols
- A WebRTC server, for receiving the stream and "do things" with that stream.


The "WebRTC server" part is already solved by Kurento and you'll not need to do much for integrating with it.

The "WebRTC client" part is not solved by Kurento. You'll need to have your very own client and in my last e-mail I just provided different alternatives that you have. Kurento is not one of them because Kurento is not a client.

I hope this clarifies the issues.

Best.


El 17/02/2015, a las 16:12, Antonini Roberto <roberto1.antonini at telecomitalia.it> escribió:

> Hi Luis,
> thanks for having promptly answered my e-mail .
> Amongst the solutions you’ve proposed, it’s not clear (at least to me) which of these are using KURENTO GE.
> I figured out that you provided us with some code snippet (with apposite KURENTO API usage) to build a client and connect your GE from our robot, I guess these are only a test cases to validate WebRTC technology on the scenario we shared, so I suppose I miss the link between these tests and KURENTO.
>  
> Anyway, just to better clarify what we meant to do:
> On our side, we would like to use KURENTO javascript clients (through Google Chrome) to connect to your KURENTO media server (using WebRTC technology), is it feasible?
> Please, let us know which are the steps (and consequently the complexity) to integrate the components above in our scenario, if we understand well.  
>  
> BR
> Roberto and Davide
>  
> Da: Luis López Fernández [mailto:luis.lopez at urjc.es] 
> Inviato: giovedì 12 febbraio 2015 16:29
> A: Antonini Roberto
> Cc: Garino Pierangelo; Colombatto Davide; fabio.dibenedetto at consoft.it; Bollano Gianmario; Angel Hernandez; Iñigo Gonzalez (igonzalez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); Fernando Herranz (fherranz at ikergune.com); fiware-robotics at lists.fi-ware.org
> Oggetto: Re: Robot characteristics
>  
> Hi Roberto,
>  
> basing on the specifications you are providing, my recommendation is to integrate WebRTC support into the robot in a native way. For this, you have several options.
>  
> 1. Use the WebRTC Google stack. 
> * This is the most mature WebRTC stack providing lots of advanced features
> * It's the stack used by Chrome
> * Can be compiled and used independently on the browser (with some work)
> * Only supports VP8 codec. Supporting H264 requires some complex integrations
> * Details of it can be found here: http://www.webrtc.org/
>  
> 2. Use the WebRTC Ericsson Stack
> * Less mature but also less heavy
> * Supports natively H.264, which is a more performant codec for your use case.
> * Details can be found here: http://www.openwebrtc.io/
>  
> Here, my choice would be option 1, but you may wish to perform a deeper analysis.
>  
>  
> For validating that you webcam works correctly with WebRTC, do the following:
>  
> - Provide internet connectivity to the robot
> - Install chrome on it
> - Open this URL
> -- https://talky.io/
> - Fill a string in the form (e.g. "aaa") and press the button.
> - Accept to share the webcam
> - The video should appear
> - Open another browser into another computer with Internet connectivity and a webcam
> - Open the url https://talky.io/aaa (where "aaa" is the string you filled previously in the form)
> - Accept to share the webcam
> - You should have a video conference between the two browsers
>  
> Best.
>  
>  
> -----------------------------------------------------------
> Luis López Fernández
> Subdirector de Investigación y Relaciones con la Empresa
> Escuela Técnica Superior de Ingenieros de Telecomunicación
> Universidad Rey Juan Carlos
> http://www.etsit.urjc.es
> e-mail: luis.lopez at urjc.es
> Tf1: +34 914 888 747 
> Tf2: + 34 914 888 713
> 
> 
> 
> 
> 
>  
> El 11/02/2015, a las 13:54, Antonini Roberto <roberto1.antonini at telecomitalia.it> escribió:
> 
> 
> Hi Luis
> As agreed, we start sending to you the characteristics of the robot we have here, that’s a turtlebot2  and the PC on board has Ubuntu 12.04 OS (more details available athttp://www.clearpathrobotics.com/turtlebot_2/tech-specs/))
> The camera we intend to use is a Logitech c270 (more details available at http://www.logitech.com/it-it/product/hd-webcam-c270).
>  
> Let us know if this’s enough, we wait for instructions on how to setup a WebRTC video streaming, in order to solve technical issues and test the end-to-end communication.
> Thank you.
> Davide and Roberto
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
> 
> <logo Ambiente_foglia2.jpg>Rispetta l'ambiente. Non stampare questa mail se non è necessario.
> <logo Ambiente_foglia2.jpg>
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150217/eec1a4ad/attachment.html>