Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DVB-I Service using 5G Media Streaming - Reference service list #27

Open
dsilhavy opened this issue Sep 7, 2023 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@dsilhavy
Copy link
Contributor

dsilhavy commented Sep 7, 2023

Background

TR 103972 v1.1.1 Section 6.3.3.2 describes the service discovery procedure that a DVB-I client uses to discover the set of available DVB-I services. DVB-I services are described in a DVB-I service list.

Feature Description

For development and demonstration purposes, 5G-MAG should host a reference DVB-I Service List (for instance a Linode instance). The reference DVB-I Service List can contain new parameters related to 5G Media Streaming such as the 5GMS AF host address and the provisioning session ID (see Section 6.3.4).

@dsilhavy dsilhavy added the enhancement New feature or request label Sep 7, 2023
@dsilhavy
Copy link
Contributor Author

We have received reference endpoints from https://slrdb.org/ , I am pasting the description here:

Providers

This implements the F1/F2 interface in the DVB-I specification TS 103 770 / A177 Rev.5 section 5.1.3.2.
The providers endpoint accepts a http query and returns an XML response containing matching providers with references to service lists. This allows a client device to discover relevant and compatible services that are available. This may include service provider or language preferences supplied by the client. The response may contain multiple service offerings, from which the user may select a service. This might be performed when initially configuring a client device or when a user changes settings. Note that the mobile use case implies the ability to roam geographically, which is not specifically anticipated in the DVB-I specification. This query may therefore be performed more frequently to discover available services. The Service List Registry can optionally support automatic geolocation based on IP address if required.

There is currently a single 5G-MAG service provider offering. It is currently hidden from public view. Accessing this therefore currently requires specifying the ProviderName and an additional parameter Test=456.
GET
https://query.slrdb.org/providers?ProviderName=5G-MAG&Test=456

This will return an XML response with ServiceListEntryPoints as described in section 5.3.2.

Services

This implements the B1/B2 interface in the DVB-I specification TS 103 770 / A177 Rev.5 section 5.5.
The services endpoint accepts a request for a specific service list and returns an XML response with a service list containing services and information about how to access them.

There is currently a single service list for 5G-MAG. The URL for the service list may be obtained from the above query for providers.
GET
https://query.slrdb.org/services/5g/5g-mag

This will return an XML response with information about services and how to access them as described insection 5.5.

There is currently a single service list with two test services. We can add or replace these test streams as required. There are corresponding links to identifying graphics. These can be replaced if there are concerns about how these are represented.

Note that the DVB-I specification includes provision for server-side regionalisation of the service list. We can support this but it needs further consideration, given the roaming potential of mobile services.

Open Items

Note the reference to other "baseline Service Access Information parameters, namely the available 5GMSd AF host address(es) and the Provisioning Session identifier of the 5GMSd downlink streaming service corresponding to the DVB-I service”.

At this point it is not clear exactly how these fit with the DVB-I specification, which is generally stateless and anonymous. This is also an open gap in TR 103972 v1.1.1 Section 6.3.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant