CONTENT URL AUTHENTICATION FOR DASH

• US 20150350205A1
• Filed: 12/20/2013
• Published: 12/03/2015
• Est. Priority Date: 01/17/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: OYMAN, Ozgur
• Granted Patent: US 9,419,973 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 63/1483 service impersonation, e.g. phishing, pharming or web spoofing detection of rogue wireless access points H04W12/12
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/762 at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 12/106 Packet or message integrity
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

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.

Claims

1. A client device operable for content uniform resource locator (URL) authentication for dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH), having 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, wherein the received content URL signature is derived at the server from the content URL contained within the DASH segment URL; and

receive a DASH segment using the authenticated content URL.

2. The computer circuitry of claim 1, wherein the computer circuitry configured to receive the URL authentication key indicator and the content URL signature indicator is further configured to:

receive the URL authentication key indicator or the content URL signature indicator via a media presentation description (MPD) metadata file.

3. The computer circuitry of claim 2, wherein the URL authentication key indicator includes a URL authentication key, or the content URL signature indicator includes a content URL signature.

4. The computer circuitry of claim 2, wherein the URL authentication key indicator includes a pointer key URL that points to the URL authentication key, or the content URL signature indicator includes a pointer signature URL that points to the content URL signature, wherein the computer circuitry is further configured to:

obtain the URL authentication key using the pointer key URL;

or

obtain the content URL signature using the pointer signature URL.

5. The computer circuitry of claim 2, wherein the URL authentication key indicator includes a URL construction rule that provides a template to construct the authentication key URLs, or the content URL signature indicator includes a URL construction rule that provides a template to construct the URLs for the content URL signatures, wherein the computer circuitry is further configured to:

generate the authentication key URLs using the URL construction rule;

or

generate the URLs for the content URL signatures using the URL construction rule.

6. The computer circuitry of claim 2, wherein a URL Authenticity descriptor is used to declare an authentication framework via the URL authentication key indicator or the content URL signature indicator, wherein the URL Authenticity descriptor includes a URL Digest element or a URL Signature element, wherein the computer circuitry is further configured to:

construct a signature URL using a template from the URL Digest element, and

download a content URL signature from the signature URL;

or

construct an authentication key URL from the URL Signature element,

download a URL authentication key from the authentication key URL,

construct a signature URL using a template from the URL Signature element, and

download a content URL signature from the signature URL.

7. The computer circuitry of claim 2, wherein the URL authentication key indicator or the content URL signature indicator is used to authenticate a base URL for a DASH MPD, period, adaption set, or representation level, or the URL authentication key indicator, or the content URL signature indicator is used to authenticate a segment URL of the MPD.

8. The computer circuitry of claim 2, wherein the URL authentication key indicator or the content URL signature indicator is used to authenticate a DASH playlist, including a plurality of DASH segment URLs, wherein the URL authentication key indicator or the content URL signature indicator is used to authenticate each playlist-specific URL in the DASH playlist.

9. The computer circuitry of claim 2, wherein the URL authentication key indicator or the content URL signature indicator is used to generate a DASH template for a plurality of DASH segment URLs, wherein the URL authentication key indicator or the content URL signature indicator indicates a predefined rule used to authenticate each template-specific URL.

10. The computer circuitry of claim 1, wherein:

the computer circuitry configured to receive a URL authentication key indicator and a content URL signature indicator is further configured to;

receive a media presentation description (MPD) metadata file including the URL authentication key indicator or the content URL signature indicator, wherein the URL authentication key indicator indicates that the URL authentication key is embedded in the DASH segment, or the content URL signature indicator indicates that the content URL signature is embedded in the DASH segment; and

the computer circuitry configured to receive the DASH segment is further configured to;

receive the URL authentication key or the content URL signature within the DASH segment.

11. The computer circuitry of claim 1, wherein the computer circuitry configured to receive a URL authentication key indicator and a content URL signature indicator is further configured to:

receive the URL authentication key indicator or the content URL signature indicator via file-level International Organization for Standardization (ISO) base media file format (ISO-BMFF) file box in the DASH segment, wherein the URL authentication key indicator includes a URL authentication key, or the content URL signature indicator includes a content URL signature, wherein the DASH segment includes an initialization segment or a moov box for the ISO-BMFF, or the DASH segment includes a media segment or a moof box for the ISO-BMFF.

12. The computer circuitry of claim 1, wherein the client device includes a mobile terminal (MT), a user equipment (UE), or a mobile station (MS);

and the client device includes an antenna, a camera, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, or a non-volatile memory port.

13. A method for providing content uniform resource locator (URL) authentication for dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) at a client device, comprising:

receiving a URL validation key indicator from an authentication server;

calculating a calculated URL signature for a URL in a DASH media presentation description (MPD) using the URL validation key indicator; and

requesting the DASH segment when the DASH segment URL is validated using the calculated URL signature.

14. The method of claim 13, wherein receiving the URL validation key indicator further comprises:

receiving the URL validation key indicator via a media presentation description (MPD) metadata file.

15. The method of claim 14, wherein the URL validation key indicator includes a URL validation key or a content URL signature, wherein validating the DASH segment URL using the calculated URL signature further comprises:

comparing a server-generated content URL signature with the client device calculated URL signature.

16. The method of claim 14, wherein the URL validation key indicator includes a pointer key URL that points to the URL validation key or a pointer signature URL that points to the content URL signature, and further comprising:

retrieving the URL validation key using the pointer key URL;

or

retrieving the content URL signature using the pointer signature URL.

17. The method of claim 14, wherein the URL validation key indicator includes a URL construction rule that provides a template to construct the authentication key URLs or a URL construction rule that provides a template to construct the URLs for the content URL signature, and further comprising:

constructing a validation key URLs using the URL construction rule;

or

constructing the URLs for the content URL signatures using the URL construction rule.

18. The method of claim 14, wherein the URL validation key indicator is used to authenticate a base URL for a DASH MPD, period, adaption set, or representation level, or the URL validation key indicator is used to authenticate a segment URL of the MPD.

19. At least one non-transitory machine readable storage medium comprising a plurality of instructions adapted to be executed to implement the method of claim 13.

20. A server for content uniform resource locator (URL) authentication for dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH), comprising:

a processor to;

generate a content URL signature, a URL authentication key indicator, and a content URL signature indicator for a DASH segment URL, wherein the URL authentication key indicator or a content URL signature indicator can be used by a client device to generate a calculated URL signature for the DASH segment URL; and

a transceiver to;

transmit a URL authentication key indicator and a content URL signature indicator to the client device;

receive a URL request from the client device for the DASH segment; and

transmit a DASH segment to the client device associated with the URL request.

21. The server of claim 20, wherein:

the transceiver is further configured to;

transmit the URL authentication key indicator and the content URL signature indicator via a media presentation description (MPD) metadata file.

22. The server of claim 21, wherein the URL authentication key indicator includes a URL authentication key, or the content URL signature indicator includes a content URL signature.

23. The server of claim 21, wherein the URL authentication key indicator includes a pointer key URL that points to the URL authentication key, or the content URL signature indicator includes a pointer signature URL that points to the content URL signature, and

the transceiver is further configured to:

transmit the URL authentication key when the pointer key URL is received;

or

transmit the content URL signature when the pointer signature URL is received.

24. The server of claim 21, wherein the URL authentication key indicator includes a URL construction rule that provides a template to construct the authentication key URLs, or the content URL signature indicator includes a URL construction rule that provides a template to construct the URLs for the content URL signatures.

25. The server of claim 21, wherein the URL authentication key indicator or the content URL signature indicator is used to authenticate a base URL for a DASH MPD, period, adaption set, or representation level, or the URL authentication key indicator or the content URL signature indicator is used to authenticate a segment URL of the MPD.

26. The server of claim 20, wherein:

the transceiver is further configured to;

receive the calculated URL signature from the client device; and

the processor is further configured to;

validate the client device with the calculated URL signature.

27. The server of claim 20, wherein the server includes a web server, a media server, an authentication server, a third generation partnership project (3GPP) long term evolution (LTE) packet switched streaming service (PSS) server, a dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) server, or an integrated multimedia subsystem (IMS) based PSS and multimedia broadcast and multicast service (MBMS) (IMS_PSS_MBMS) server.