L.3 MBMS User Service Discovery / Announcement Profile 1b

26.3463GPPMultimedia Broadcast/Multicast Service (MBMS)Protocols and codecsRelease 17TS

The function of Service Discovery is to allow UEs to find the available MBMS User Services defined on the MBMS enabled network and the associated service access information (e.g. FLUTE session parameters, TMGI, file repair servers, etc.) for MBMS User Services of interest. The UE needs the service access information to initiate the reception of a particular MBMS User Service, and to find the data associated with the MBMS User Service on the radio interface.

The Service Announcement Profile defined in this clause follows the principles of the Service Announcement Profile 1a as defined in clause L.2 with the following constraints:

– Service Announcement metadata fragments shall be delivered as one SA file.

– In the case of Live DASH Services, the SA file shall contain the Media Presentation Description (MPD) fragment for the MBMS User Service, referenced by the r9:mediaPresentationDescription element in the USBD. If the USBD also references an Application Service Description fragment with the r12:appService element, the SA file shall also contain the Application Service Description fragment whose content is the unified MPD fragment.

– In the case of Live HLS Services, the SA file shall contain the Application Service Description fragment whose content is a Master Playlist as defined in [144] for the MBMS User Service, referenced by the r12:appService element in the USBD.

– In the case of Live hybrid DASH/HLS Services, the SA file shall contain:

– the Media Presentation Description (MPD) fragment for the MBMS User Service, referenced by the r9:mediaPresentationDescription element;

– the Application Service Description (ASD) fragment whose content is the unified MPD, if the USBD also references an ASD fragment with the r12:appService element whose MIME type contains "application/dash+xml"; and

– the Application Service Description (ASD) fragment whose content is the HLS master playlist fragment for the MBMS User Service, referenced by the r12:appService element in the USBD, with the mimeType attribute set to "application/dash+xml profiles=’ urn:mpeg:dash:profile:cmaf:2019".

– In the case of Live DASH Services, the SA file shall contain (all) needed Initialization Segment Description (ISD) fragments for the MBMS User Service.

In the case of Live HLS Services, the SA file shall contain (all) needed Initialization Segment Description (ISD) fragments whose content is a Media Initialization Section ([144]) for the MBMS User Service.-

In the case of Live hybrid DASH/HLS Services, the SA file shall contain (all) needed Initialization Segment Description (ISD) fragments for the MBMS user service, used as Initialization Segment by the DASH clients, and used as Media Initialization Section by the HLS clients.

– Each In-Band Fragment shall be embedded in one Metadata Envelope as defined in clause 11.1.4. Each metadata envelope shall contain exactly one metadata fragment.

– The feature child element of the requiredCapabilities element shall have the value "23", corresponding to the "MBMS User Service Discovery / Announcement Profile 1b", as defined in clause 11.9.