Open dsilhavy opened 4 months ago
@jordijoangimenez @rjb1000 @davidjwbbc : Only added you as observers here in case you have a comment especially on:
Moreover, we should discuss if we can provide an endpoint to create the m8.json automatically similar to what the msaf-configuration tool is doing today
There are a few things to clarify going into the direction of automating the setup or at least providing some clear steps what to do.
Another thing to check is that the m8.json should be created with all the information and parameters needed for the consumptions reports, QoE metrics, services, etc.
In an ideal world, we would ditch the m8.json
file altogether in favour of a DVB-I Service List that is automatically generated by a simple service management system that also provisions the 5GMSd AF.
On the client side, this would drive the user experience of a DVB-I Client that would then initiate downlink media streaming sessions by means of a 5GMS Service URL embedded in the DVB-I Service List metadata.
Description
For playback of 5GMS content on the client-side, information provided via the
M8
interface is required. Our current implementation relies on anm8.json
file with the following structure:Problem Description
Currently, only the
msaf-configuration
tool is capable of creating them8.json
file automatically. If the configuration of the AF is done via Postman, curl or any other REST client, the M8 information needs to be created manually and placed on a webserver for the 5GMS Aware Application to download.Feature Request
Document how to create an
m8.json
file based on the configuration of the AF. Moreover, we should discuss if we can provide an endpoint to create them8.json
automatically similar to what themsaf-configuration
tool is doing today.