Discussion Item: Signaling of DRM information via ServiceAccessInformation #49
Labels
3GPP Rel-19
Issues relating to 3GPP Release 19 specifications.
3GPP TS 26.512
Issues relating to SA4's "5G Media Streaming (5GMS); Protocols" specification.
5GMS Service Access/Launch
Discussion
Topic for discussion.
New Feature
Milestone
Problem description
TS 26.512 defines a way to signal the MPD URL as part of the
ServiceAccessInformation
resource. For that reason, theStreamingAccess.mediaPlayerEntry
field can be used. To my best knowledge there is no similar mechanism to signal the corresponding DRM license server and DRM custom headers via theServiceAccessInformation
resource. Consequently, this information needs to be embedded in the DASH manifest or the DASH segments or provided via a different interface.While a Playready DRM allows signaling the license server URL using the
pssh
box of the segments, this is not possible for Widevine.For manifest files the DASH-IF Content Protection guidelines define the
dashif:Laurl
element to specify the license server:However, this might not be supported by all media players, for instance I did not find any usage of the
dashif:Laurl
element in Exoplayer.In addition, the DASH-IF Content Protection guidelines define the
dashif:Authzurl
element to retrieve authorization tokens that may be required for requesting a license from a license server:Again client support might be limited.
Suggested solution description
This is more a suggestion to discuss if it could be useful to signal DRM information as part of the
ServiceAccessInformation
resource. That would allow applications to pass the required parameters to the media player instead of expecting the media player to derive the required information from the manifest or the segments. In addition, it would allow for changes of the DRM information without touching the manifest or the segments.The text was updated successfully, but these errors were encountered: