D4.2.1 Version Author Dissemination Date Status

1.0 NAEVATEC PU 27/01/1015 Final

D4.2.1: Multisensory and Multi-Domain Media Element Middleware v1

Project  acronym:   Project title: Project duration: Project type: Project reference: Project web page: Work package WP leader Deliverable nature: Lead editor: Planned delivery date Actual delivery date Keywords

NUBOMEDIA   NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud for interactive social multimedia 2014-02-01 to 2016-09-30 STREP 610576 http://www.nubomedia.eu WP4 Javier López Prototype Javier López 01/2015 27/01/2015 Kurento, media server, multisensory, multidomain

The research leading to these results has been funded by the European Union’s Seventh Framework Programme (FP7/2007-2013) under grant agreement nº 610576

FP7 ICT-2013.1.6. Connected and Social Media

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

This is a public deliverable that is provided to the community under a Creative Commons Attribution-ShareAlike 4.0 International License http://creativecommons.org/licenses/by-sa/4.0/ You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material for any purpose, even commercially. The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. Notices: You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation. No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material. For a full description of the license legal terms, please refer to: http://creativecommons.org/licenses/by-sa/4.0/legalcode

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

2

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

Contributors: Javier Lopez (NAEVATEC) Ivan Gracia (NAEVATEC) J. A. Santos Cadenas (NAEVATEC) Miguel París Díaz (URJC)

Internal Reviewer(s): Luis Lopez (URJC)

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

3

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

Version History Version Date 0.1 03-01-2015 0.2 10-01-2015

Authors F. Javier Lopez Ivan Gracia

1.0

Ivan Gracia

22-01-2015

Comments Initial Version Contributions to architecture and software implementation. Final picture added.

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

4

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

Table of contents 1   Executive  summary  ..............................................................................................  8   2   Introduction  .........................................................................................................  8   2.1   State-­‐of-­‐the-­‐art  on  multisensory  multimedia  ................................................................................  8   2.2   State-­‐of-­‐the-­‐art  on  multi-­‐domain  multimedia  ...............................................................................  9   3   Objectives  ..........................................................................................................  10   4   Implementation  strategy  ...................................................................................  10   4.1   Implementing  multisensory  media  elements  ...............................................................................  10   4.2   Implementing  multi-­‐domain  media  elements  ..............................................................................  11   5   Software  architecture  ........................................................................................  11   5.1   Multisensory  media  elements  .............................................................................................................  11   5.2   Multi-­‐domain  media  elements  ............................................................................................................  11   6   Implementation  status  (NUBOMEDIA  Release  3)  ................................................  12   7   References  .........................................................................................................  13  

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

5

Luis López F Eliminado:

Luis López F Eliminado:

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

List of Figures:   Figure  1.  WebRtcEndpoint  internal  structure  expressed  in  term  of  GStreamer  media  elements.  ..............  11   Figure  2.  KmsElement  connection  graph  expressed  in  term  of  GStreamer  media  elements.  .....................  12  

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

6

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

Acronyms and abbreviations: API AR IMS IoT KMS RTC RTP SCTP VCA WebRTC

Application Programming Interface Augmented Reality IP Multimedia Subsystem Internet of Things Kurento Media Server Real-Time Communications Real-time Transport Protocol Stream Control Transmission Protocol Video Content Analysis Web Real Time Communications

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

7

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

1 Executive  summary   This document contains a description of the extensions to be created to the Kurento Media Server (KMS), as described in deliverable D4.1.1 providing multisensory and multi-domain capabilities. These extensions take the form of KMS modules and have two different natures: • Multisensory extensions: This refers to the capability of managing multimedia flows containing more than audio and video information. In general, multisensory extensions are related to the integration on the multimedia stream of additional sensor data (i.e. biomedical sensors, smart-city sensors, etc.) • Multi-domain extensions: This refers to the capability of transducing (i.e. translating) multisensory information into audio-visual information comprehensive for a human receiver. In other words, multi-domain extensions are KMS filters capable of representing sensor data, or other data, to the human receiver using some kind of Augmented Reality (AR) mechanism.

2 Introduction   2.1 State-­‐of-­‐the-­‐art  on  multisensory  multimedia   The pervasive presence of sensors and the emergence of the IoT model have added pressure from users and providers to combine sensor data with audiovisual information. This combination, which is sometimes referred as the cross media model or as the multisensory multimedia model, requires new types of technologies capable of transporting and managing arbitrary sensor data or arbitrary metadata as part of the multimedia stream, which traditionally has only contained audio and video. In current state-of-the-art, there are two possible strategies for implementing multisensory multimedia: in-band and out-of-band. The in-band strategy consists on extending current media formats to be able to manage sensor data into the same protocols and formats used by audiovisual data. In other words, the in-band strategy uses the same channel (i.e. band) for audio, video, sensor and other data. This approach has a number of advantages • Synchronization is simplified as all streams may share common clock references. • Transport is simplified as all streams share the same low level channel But also has drawbacks: • It requires huge modifications on the client applications using traditional audiovisual-based multimedia to support the new standards and models. This strategy is the one used by standards such as MPEG-21, where different types of media data can be inserted as “Digial Items” into the same shared medium. It is also used for video subtitling as specified in RFC 4103 (i.e. ITU T.140), where meta-data information is transported using common RTC audiovisual transport protocols (i.e. RTP) and mechanisms. The out-of-band strategy consists on letting untouched current (and common) audiovisual formats and use additional channels, which may use different protocols and formats, for the transport and management of sensor and metadata. This approach has a number of advantages

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

8

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1 It maintains compatibility with current state-of-the-art multimedia technologies, so that you don’t need to modify them for supporting the integration of sensor data. • It is more simple and efficient to implement, given that the additional channels and formats can be designed specifically adapted to the characteristics of the target data. This model is currently being used in most IoT deployments involving multimedia communications, including many transport-agnostic XML formats (e.g. NGSI, BiTXML). •

In particular, the emergence of WebRTC technologies has brought a revolution to the multisensory multimedia arena with the introduction of the WebRTC DataChannel standards. RTCDataChannels are an out-of-band technology with a number of very relevant advantages: • They provide low-latency transports based on RTP and SCTP compatible with the low-latency ones of audiovisual data. • They are implemented in all WWW browsers compatible with WebRTC standards. • They have been designed for sharing the same ICE channels of the WebRTC multimedia audiovisual information, so they inherit all their properties (i.e. NAT traversal, compatibility with P2P communication models, etc.) • The W3C has standardized a coherent API for accessing them. • It is WWW friendly, meaning that it is fully compatible with well known data representation formats such as XML and JSON. However, it is agnostic to such formats, being possible to exchange any kind of data including binary blobs. • There are currently hundreds of developers creating multisensory applications basing on RTCDataChannels, which guarantees its support and maturity. Hence, the adoption of RTCDataChannels does not require any modification of the audiovisual capabilities of the clients, just the addition of an additional channel for the communication and management of the desired data and meta-data.

2.2 State-­‐of-­‐the-­‐art  on  multi-­‐domain  multimedia   The representation of sensor data in a human comprehensive way through Augmented Reality (AR) techniques is quite in the mood in the last few years, and the scientific and engineering bibliography contains many references related to technologies and use cases for it [1-4]. In particular, the emergence of new AR wearable devices such as glasses or helmets is bringing a new gold era to these types of technologies. There are different approaches for facing this technological problem, however, in general all of them are based on implementing the following methodology: • First, data is captured by some kind of sensor either remotely or at the device of the end-user. In the former case, a specific protocol is required for the transport of the sensor data and, eventually, of the media data, as described above in this document. • Second, some kind of AR object is created representing data in a human comprehensive way. This AR object may have different natures including: o Text showing the data in numeric or verbal format. o 2D graphs, which may include gauges, pie-charts, bar-charts, linegraphs, etc. NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

9

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1



o 3D objects, which may represent the status of the sensor through some kind of reality (e.g. a heat-beating, a car running, etc.) Third, the AR object is rendered on top of the video stream visualized by the end-user either floating at some specific coordinates either hooked through some kind of marker or marker-less mechanism.

3 Objectives     The objective of this deliverable is to design, implement, integrate, specify and document the appropriate multisensory and multi-domain technologies suitable to be used in NUBOMEDIA and accordingly to NUBOMEDIA partners’ requirements. The execution of this objective requires the fulfillment of a number of sub-objectives, which include: • To determine the better technological approach for providing multisensory transport for NUBOMEDIA. • To design the appropriate software architecture for implementing such transport onto NUBOMEDIA client and server platforms. • To create the appropriate implementation as KMS modules and endpoints. • To determine the better technological approach for providing multi-domain capabilities for NUBOMEDIA. • To design the appropriate software architecture for implementing such capabilities into the NUBOMEDIA infrastructure. • To implement the architecture through the creation of the necessary KMS modules. • To integrate into such modules the associated AR capabilities providing sensor data transducing and translation.

4 Implementation  strategy   4.1 Implementing  multisensory  media  elements   As we have discussed in sections above, for the implementation of NUBOMEDIA multisensory capabilities we have two options: in-band and out-of-band mechanism. The former has the advantage of being more compact and solving better synchronization issues (e.g. rendering of the sensor data synchronized with the audiovisual data). However, they have a clear an important disadvantage: lack of universal support. Currently, very few platforms and applications support such types of formats and implementing them for all NUBOMEDIA target platforms is out of the reach of a small project like NUBOMEDIA. Hence, the best option for us is to make use of out-of-band mechanism, so that NUBOMEDIA multisensory technologies can coexist with state-of-the-art video technologies (i.e. players, recorders, endpoints, etc.) Following the discussion above, the most reasonable strategy to follow is to provide support for WebRTC (RTC) DataChannels and inherit all the advantages of standardized (although standards are still under development, they are maturing quite fast) WWW technologies. This implementation strategy requires integrating RTCDataChannel capabilities at KMS. For achieving this, we propose the following methodology: NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

10

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1 • •

To integrate RTCDataChannel support into KMS WebRtcEndpoint. This integration must expose, as a minimum, SCTP transport capabilities. To expose RTCDataChannel capabilities through a simple to use API accessible from the WebRtcEndpoint. This API needs to make possible to receive and send arbitrary data based on both textual and binary formats.

4.2 Implementing  multi-­‐domain  media  elements   In the case of multi-domain media elements, or transducing multisensory information into audio-visual information, the media server’s elements need to be able to send and receive data from and to other media elements. The data sent could then be overlaid on a media stream, being passed through the media element that is receiving this data.

5 Software  architecture   5.1 Multisensory  media  elements   The WebRTC standard defines a mechanism to exchange not only media, but also data. It is a feature called Data Channels, that is to be implemented in the short-medium term. This element is basically a Session Control Transmission Protocol (SCTP) connection encrypted using DTLS. In consonance with the existing structure of the WebRtcEndpoint, the approach is to create two GStreamer elements (KmsSctpDec and KmsSctpEnc) that will marshall and unmarshall SCTP packets. These two elements will be then connected to the existing GstDtlsSrtpDec and GstDtlsSrtpEnc, where the packets will be encrypted or decrypted. The following diagram shows the internal structure of the WebRtcEndpoint, where the new GStreamer elements would be placed.

Figure 1. WebRtcEndpoint internal structure expressed in term of GStreamer media elements.

5.2 Multi-­‐domain  media  elements   In order to support data flow, it is needed to provide KmsElement with a data channel. These modifications are depicted in the connection graph in the following figure.

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

11

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

Figure 2. KmsElement connection graph expressed in term of GStreamer media elements.

There will be only one kind of data by default, meaning that each buffer will be considered as an independent message. It is the receiver of the buffer the one in charge of providing semantics to each message, be it a remote receiver or another internal GStreamer element. In this way, data are just non-changing streams for GStreamer, so they don’t require any special negotiation. As for synchronization, buffers in data channels are marked with a pts, analogous to the ones that audio and video buffers have. This mark allows an element to synchronize in case it is required. For this purpose, the receiver element will be responsible of keeping the packages of a certain type during a variable amount of time, until it is considered that no new buffers of the type to synchronize with arrive. For instance, video packages are retained for a couple of milliseconds, in case a data package arrives and synchronization with this data package is required. This mechanism does not guarantee synchronization in every circumstance, because if the media that is being awaited takes too long to arrive, there could be a desynchronization. In this case, each element will decide if the data is shown even if it did arrive late, or if it is critical to show data in perfect synchronization.

6 Implementation  status  (NUBOMEDIA  Release  3)   Implementation efforts of multisensory and multi-domain media elements are planned o start during NUBOMEDIA Release 4.

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

12

D4.2.1: Multisensory and Multi-domain Media Element Middleware v1

7 References   [1] Payton, David W., et al. "Pheromone robotics." Intelligent Systems and Smart Manufacturing. International Society for Optics and Photonics, 2001. [2] Narzt, Wolfgang, et al. "Augmented reality navigation systems." Universal Access in the Information Society 4.3 (2006): 177-187. [3] Vazquez-Alvarez, Yolanda, Ian Oakley, and Stephen A. Brewster. "Auditory display design for exploration in mobile audio-augmented reality." Personal and Ubiquitous computing 16.8 (2012): 987-999. [4] Akinbiyi, Takintope, et al. "Dynamic augmented reality for sensory substitution in robot-assisted surgical systems." Engineering in Medicine and Biology Society, 2006. EMBS'06. 28th Annual International Conference of the IEEE. IEEE, 2006.

NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia

13

D4.2.1 official deliverable (PDF) - NUBOMEDIA

Jan 27, 2015 - D4.2.1: Multisensory and Multi-Domain Media Element ... NUBOMEDIA: an elastic PaaS cloud for interactive social ... 10-01-2015 Ivan Gracia.

639KB Sizes 0 Downloads 244 Views

Recommend Documents

D6.1.2 official deliverable (PDF) - NUBOMEDIA
Jan 31, 2016 - D6.1.2: NUBOMEDIA Testbed and simulated load validation v2. 1. NUBOMEDIA: an ... NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud ...... extension with at least 1 network adapter for single node deployment.

D2.4.2 official deliverable (PDF) - NUBOMEDIA
Jan 25, 2016 - NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud .... 4.3.3 Network Function Virtualization Orchestrator . .... Figure 1. The NUBOMEDIA development model (right) is based on the popular tree tier development.

D3.4.1 official deliverable (PDF) - NUBOMEDIA
Jan 27, 2015 - D3.4.1: Elastic Media Manager v1. NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia. 2 ...... Figure,10,Run,time,structure,of,a,topology,. .... network configuration to a new virtual resource. Therefore in ..... Openst

D4.5.1 official deliverable (PDF) - NUBOMEDIA
Jan 27, 2015 - 610576. Project web page: ... Adapt — remix, transform, and build upon the material for any purpose, even .... 10. 2.5 Implementation status: ar-‐markerdetector . ..... an image on top of every face detected in video frames.

D3.1.1 official deliverable (PDF) - NUBOMEDIA
Jan 22, 2014 - D3.1.1: NUBOMEDIA virtual infrastructure v1. 1. NUBOMEDIA: an elastic ... NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud ..... The Networking service, code-named neutron, provides an API that lets you define.

D2.2.2 official deliverable (PDF) - NUBOMEDIA
Jan 31, 2016 - NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud for interactive social .... 3.1.1 Description of current SoTA . ... 3.2 Orchestration and Management of Real-‐Time Network Functions with guaranteed QoS14. 3.2.1 ...

D3.6.1 official deliverable (PDF) - NUBOMEDIA
Jan 27, 2014 - NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud ...... extension with at least 1 network adapter for single node deployment.

D2.4.3 official deliverable (PDF) - NUBOMEDIA
May 4, 2017 - Query deployment status: Depending on the application specific deployment configuration requirements, the deployment procedure on the PaaS and on the media plane could take a few seconds or longer. For long procedures, the user always h

D6.1.1 official deliverable (PDF) - NUBOMEDIA
Jan 7, 2014 - NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia. D6.1.1. Version. 1.0 ... Connected and Social Media ... 2.1 Network connectivity . ... 10. Setup testbed . ..... describe the best method to replicate the testbed.

D2.2.1 official deliverable (PDF) - NUBOMEDIA
Jan 22, 2015 - D2.1: State-of-the-art revision document v1. NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia. 10 have one or more copies ...

D3.3.1 official deliverable (PDF) - NUBOMEDIA
Jan 27, 2015 - NUBOMEDIA. Project title: NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud ..... Figure 1: Software Defined Network Architecture [1] .

D4.1.1 official deliverable (PDF) - NUBOMEDIA
Jan 27, 2015 - D4.1: Distributed Media Pipeline Middleware v1. Project acronym: NUBOMEDIA. Project title: NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud ...... processes belonging to different computers in an IP network.

D4.3.1 official deliverable (PDF) - NUBOMEDIA
Jan 27, 2015 - D4.3.1: Media Elements for Social and Immersive Environments v1. NUBOMEDIA: an .... 10. 4.1 Implementing social and group real-‐time communications . .... the most popular are the transcoding and mixing ones. .... networks, depend he

D3.2.1 official deliverable (PDF) - NUBOMEDIA
Jan 27, 2015 - Connected and Social Media ... NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia ..... Figure 10 Shared cluster architecture .Missing:

D2.2.3 - NUBOMEDIA
Nov 30, 2016 - NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia. 2. DISCLAIMER ...... data point is the arithmetic mean obtained from ten runs. Error bars indicate the ...... (2012), http://datasys.cs.iit.edu/events/MTAGS12/p07.pdf

D3.5.1 - NUBOMEDIA
Jan 27, 2015 - NUBOMEDIA. Project title: NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud ..... 6.2.1 Current Application Function . ..... for developing loosely coupled and cloud enabled network service applications. OpenXSP is ...

D6.1.3 - NUBOMEDIA
Jan 31, 2017 - NUBOMEDIA: an elastic PaaS cloud for interactive social ... 18/10/2016 Cristian Spoiala (USV) ...... Figure 21 Media topology of the nubomedia-network-benchmark .... Daily, weekly & monthly Reports for each application, in PDF or HTML

Project Deliverable Report Deliverable 2.3 – Services v1 integrated
Feb 12, 2010 - fault a course is automatically provided with a customized semantic space, ..... uploading a widget to the Wookie engine it adds lines to HTML files loading ..... six in ten have never considered that what they put online now ...

Project Deliverable Report Deliverable 2.3 – Services v1 integrated
Feb 12, 2010 - The second part deals with the services used while using the ..... aspect by providing a built-in proxy service that allows the calling of services.

D1.2 NUBOMEDIA WEB PAGE
Mar 29, 2014 - Provide project vision and benefits in plain and understandable language. • Provide project technological vision and roadmap in publishable format. • Provide reference information about the project in publishable format. • Descri

d1.1 project presentation - NUBOMEDIA
Feb 28, 2014 - ... ICT-2013.1.6. Connected and Social Media ... NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia. 2 .... around 10 minutes.Missing:

D7.5: NUBOMEDIA WWW community sites
Jan 31, 2017 - NUBOMEDIA: an elastic PaaS cloud for interactive social multimedia. 2 ..... Community popularity indicators . .... Figure 10 NUBOMEDIA Media Plane . .... the most active communities in the WebRTC ecosystem arena.

D3.2 Cloud Platform v2 - NUBOMEDIA
Jan 27, 2015 - NUBOMEDIA: an elastic Platform as a Service (PaaS) cloud ..... 4.1.1 Network Service Record (NSR) deployment sequence diagram . ...... 3 https://www.openstack.org/assets/pdf-downloads/Containers-and-OpenStack.pdf ...

D6.6: NUBOMEDIA Social Game Demonstrator
Mar 2, 2017 - and Android platforms and a server part that will run as a client service .... 10. Once Upon a Time, tale mode. FREE MODE. A multimedia video ...