This document summarizes a framework for fully interoperable streaming of media resources in heterogeneous environments. The framework uses various MXM engines and protocols to allow a client to query for and request streaming of digital media items based on their capabilities. It retrieves media descriptions using MPEG Query Format and streams adapted content using capabilities exchanged via MPEG-21 Digital Item Adaptation protocols. The Virtual Light Client is extended to provide the streaming functionality using these standards.

1. Fully Interoperable Streaming of Media Resources in Heterogeneous Environments Michael Eberhard MXM Streaming Framework 1 Michael Eberhard Christian Timmerer Hermann Hellwagner Institute of Information Technology Klagenfurt University Klagenfurt, Austria Thisworkissupported in thecontextofthe P2P-Next project (FP7-ICT-216217)

2. Overview Motivation List of Technologies / MXM Engines Architecture of the Streaming Framework Demo of the Streaming Framework Conclusions Michael Eberhard MXM Streaming Framework 2

3. Motivation Thereis a strong needfor Quality of Service and Universal Multimedia Access Whenconsumingcontent, thecapabilitiesoftheuser‘sterminalsandnetworkconnectionsare diverse The contenthastobeprovidedoverheterogeneousnetworkslikethe Internet An interoperable solutiontomatchtheuser‘scontextandthequalityofthecontentisdesired. Michael Eberhard MXM Streaming Framework 3

4. Technologies / MXM Engines MPEG Query Format Performqueriesfor a listof Digital Items Provide a playlistwithidentifierand title MXM Request Content Protocol Request a Digital Item andprovidethe UED/UCD Return the URL forthestreamingsession MPEG-21 Digital Item Adaptation UED, UCD, andAQoS MXM Media Framework Engine Media resourceadaptation, streaming & decoding Michael Eberhard MXM Streaming Framework 4

5. Architecture of the Streaming Framework (1) The VLC provides the streaming capabilities for both, the server and the client. The VLC is extended with an MXM interface on theserver-side to enable the setup of Video on Demand sessions utilizing MXM protocols. The VLC GUI is extended with an MXM dialog on theclient-side to provide the user with access to the Digital Items at the server. Michael Eberhard MXM Streaming Framework 5

6. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 6

7. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 7 Request Playlist

8. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 8 MPQF Request <mpqf:Query> <mpqf:Input> <mpqf:OutputDescription> <mpqf:ReqFieldtypeName="did:StatementType"> /dii:Identifier </mpqf:ReqField> <mpqf:ReqFieldtypeName="mpeg7:CreationInformationType"> /mpeg7:Creation/mpeg7:Title </mpqf:ReqField> </mpqf:OutputDescription> </mpqf:Input> </mpqf:Query>

9. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 9 Retrieve DIs

10. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 10 MPQF Response <mpqf:MpegQuery> … <mpqf:ResultItemrecordNumber="1"> … <did:Descriptor> <did:StatementmimeType="text/xml"> <dii:Identifier>exampleId</dii:Identifier> </did:Statement> </did:Descriptor> <did:Descriptor> <did:StatementmimeType="text/xml"> <mpeg7:Mpeg7> … <mpeg7:Title>exampleTitle</mpeg7:Title> … </mpeg7:Mpeg7> </did:Statement> </did:Descriptor> …

11. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 11 Return Playlist

12. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 12 ID, Preferences, Capabilites

13. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 13 Request Content <RequestContent> <mxmbp:TransactionID>rc1</mxmbp:TransactionID> <ContentIdentifier> <mxmbp:ContentItemIdentifier> exampleId </mxmbp:ContentItemIdentifier> </ContentIdentifier> <UsageEnvironmentDescription> … <UniversalConstraintDescription> … </RequestContent>

14. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 14 Request Content Response <RequestContentResponse> <mxmbp:TransactionID>rc2</mxmbp:TransactionID> <ContentURL> <MimeType>video/mp4</MimeType> <URL>rtsp://143.205.123.54:5444/ID346582</URL> </ContentURL> </RequestContentResponse>

15. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 15 UED, UCD, DI-ID AQoS

16. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 16 Request Stream

17. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 17 Stream Adapted Media

18. Architecture of the Streaming Framework (2) Michael Eberhard MXM Streaming Framework 18

19. Architecture of the Streaming Framework (3) The media resources available at the server are requested using the MPEG Query Format (MPQF). The request for the desired sequence is performed utilizing MXM‘s Request Content Protocol (including the usage environment conditions formatted according to MPEG-21 DIA). The streaming and adaptation capabilities are provided by the VLC and ffmpeg. Michael Eberhard MXM Streaming Framework 19

20. Demo ofthe Streaming Framework Michael Eberhard MXM Streaming Framework 20

21. Whyshouldweusethe MXM Engines? Itmakestheimplementationofcustomizedmultimediademos/frameworks a loteasier Itensuresfullinteroperabilitythanksto MPEG, IETF, and W3C An open sourceimplementationisprovided Michael Eberhard MXM Streaming Framework 21

22. Questions? Michael Eberhard MXM Streaming Framework 22 Thankyouforyourattention!