Content URL authentication for dash
Technology for content uniform resource locator (URL) authentication for dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) is disclosed. In an example, a client device can include computer circuitry configured to: Receive a URL authentication key indicator and a content URL signature indicator from a server; generate a calculated URL signature for a URL in a DASH media presentation description (MPD) from the URL authentication key indicator; request the DASH segment when the calculated URL signature matches the received content URL signature, thereby authenticating content URL; and receive a DASH segment using the authenticated content URL. The received content URL signature is derived at the server from the content URL contained within the DASH segment URL.
1. An apparatus of a client device operable to perform uniform resource indicator (URI) authentication for dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH), the apparatus comprising:
memory; and
one or more hardware processors configured to:
decode a media presentation description (MPD) file received from a server in a content delivery network (CDN), wherein the MPD file includes:
a URI, a URI signature associated with the URI, and a URI key indicator associated with the URI, wherein the URI key indicator is used to generate the URI signature;
store the MPD file in the memory; and
authenticate by the client device the URI included in the MPD file using the URI signature and the URI key indicator included in the MPD file for requesting from the server a DASH segment.
2. The apparatus of claim 1 , wherein the one or more processors are further configured to:
request, from the server, a DASH segment associated with the URI, and the DASH segment is requested after the URI is authenticated using the URI signature and the URI key indicator; and
process the DASH segment received from the server.
3. The apparatus of claim 2 , further comprising a transceiver configured to:
receive the MPD file from the server;
transmit, to the server, the request for the DASH segment associated with the URI included in the MPD file; and
receive the DASH segment from the server.
4. The apparatus of claim 1 , wherein the one or more processors are configured to perform URI signing for URIs included in the MPD file received from the server.
5. The apparatus of claim 1 , wherein the one or more processors are further configured to process an additional MPD file that includes additional URIs that point to URI signatures associated with URIs included in the additional MPD file.
6. The apparatus of claim 1 , wherein the one or more processors are further configured to process DASH segments received from the server that include URI signatures and URI key indicators to be utilized for URI authentication.
7. The apparatus of claim 1 , wherein the client device is a DASH client.
8. The apparatus of claim 1 , wherein the server is included in a content delivery network (CDN).
9. A dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) client device operable to perform uniform resource indicator (URI) authentication, the DASH client device comprising:
memory; and
one or more hardware processors configured to;
decode a media presentation description (MPD) file received from a server in a content delivery network (CDN), wherein the MPD the includes:
a URI, a URI signature associated with the URI, and a URI key indicator associated with the URI, wherein the URI key indicator is used to generate the URI signature; and
authenticate by the client device the URI included in the MPD file using the URI signature and the URI key indicator included in the MPD file for requesting from the server a DASH segment.
10. The DASH client of claim 9 , wherein the one or more processors are further configured to:
request, from the server, a DASH segment associated with the URI, and the DASH segment is requested after the URI is authenticated using the URI signature and the URI key indicator; and
process the DASH segment received from the server.
11. The DASH client of claim 10 , further comprising a transceiver configured to:
receive the MPD file from the server;
transmit, to the server, the request for the DASH segment associated with the URI included in the MPD file; and
receive the DASH segment from the server.
12. The DASH client of claim 9 , wherein the one or more processors are configured to perform URI signing for URIs included in the MPD file received from the server.
13. The DASH client of claim 9 , wherein the one or more processors are further configured to process an additional MPD file that includes additional URIs that point to URI signatures associated with URIs included in the additional MPD file.
14. The DASH client of claim 9 , wherein the one or more processors are further configured to process DASH segments received from the server that include URI signatures and URI key indicators to be utilized for URI authentication.
15. The DASH client of claim 9 , wherein the DASH client includes an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, an internal memory, a non-volatile memory port, or combinations thereof.
16. At least one non-transitory machine readable storage medium having instructions embodied thereon for performing uniform resource indicator (URI) authentication for dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) at a client device, the instructions when executed by one or more processors cause the cent device to perform the following:
decoding a media presentation description (MPD) file received from a server in a content delivery network (CDN), wherein the MPD file includes:
a URI, a URI signature associated with the URI, and a URI key indicator associated with the URI, wherein the URI key indicator is used to generate the URI signature;
storing the MPD the in a memory of the cent device; and
authenticate by the client device the URI included in the MPD file using the URI signature and the URI key indicator included in the MPD file for requesting from the server a DASH segment.
17. The at least one non-transitory machine readable storage medium of claim 16 , further comprising instructions which when executed by the one or more processors cause the client device to perform the following:
requesting, from the server, a DASH segment associated with the URI, and the DASH segment is requested after the URI is authenticated using the URI signature and the URI key indicator; and
processing the DASH segment received from the server.
18. The at least one non-transitory machine readable storage medium of claim 16 , wherein the one or more processors are configured to perform URI signing for URIs included in the MPD file received from the server.
19. The at least one non-transitory machine readable storage medium of claim 16 , further comprising instructions which when executed by the one or more processors cause the client device to perform the following: processing an additional MPD file that includes additional URIs that point to URI signatures associated with URIs included in the additional MPD file.
20. The at least one non-transitory machine readable storage medium of claim 16 , further comprising instructions which when executed by the one or more processors cause the client device to perform the following: processing DASH segments received from the server that include URI signatures and URI key indicators to be utilized for URI authentication.