DASH-aware network application function (D-NAF)

1. A server comprising a dynamic adaptive streaming over hypertext transfer protocol (HTTP) aware (DASH-aware) network application function (D-NAF), the server comprising:

memory; and a processor coupled to the memory, configured to:

authenticate a client using a network application function (NAF);

transmit using a DASH proxy for DASH content and authentication information for the client;

parse a DASH media presentation description (MPD) metadata file for a DASH content information including content-specific authentication policy information; and

override a generic authentication architecture-based (GAA-based) authentication procedure via a bootstrapping server function (BSF) or home subscriber subsystem (HSS).

2. The server of claim 1 , wherein:

the DASH proxy is further configured to:

update the MPD to include authentication policy information from the NAF;

the D-NAF is further configured to:

authorize the client for access to DASH content subject to content-specific authentication policies.

3. The server of claim 2 , wherein the DASH content information includes a DASH content information uniform resource locator (URL), wherein the DASH content information URL is used to authenticate a base URL for a DASH MPD, period, adaption set, or representation level, or the DASH content information URL is used to authenticate a segment URL of the MPD.

4. The server of claim 2 , wherein:

the NAF is further configured to:

retrieve a session key from a bootstrapping server function (BSF) including a NAF key material (Ks_NAF), profile, bootstrapping time, or key lifetime; and

the DASH proxy is further configured to:

retrieve content keys for the DASH content information.

5. The server of claim 2 , wherein:

the NAF or the DASH proxy is further configured to:

retrieve a content key from a bootstrapping server function (BSF) including a NAF key material (Ks_NAF) for the DASH content information.

6. The server of claim 2 , wherein:

the D-NAF is further configured to:

receive DASH-specific authentication policy from a DASH service provider for DASH content.

7. The server of claim 2 , wherein:

the DASH proxy or the NAF is further configured to:

receive DASH-specific authentication policy from a DASH service provider for DASH content;

incorporate the DASH-specific authentication policy into a user authentication policy;

authorize client access to the DASH content by enforcing both the DASH-specific authentication policy and the user authentication policy for the DASH content information and the client authentication; and

indicate the enforced authentication policies in the DASH MPD.

8. The server of claim 7 , wherein the D-NAF provides operator network authentication for the DASH service provider.

9. The server of claim 7 , wherein the D-NAF receives the authentication policy for the DASH service provider in the DASH MPD.

10. The server of claim 1 , wherein:

the DASH proxy is further configured to:

receive DASH authentication information for DASH content and a DASH content information location in a media presentation description (MPD) metadata file, wherein the DASH authentication information includes a signature and an authentication key, and the DASH content information location includes a DASH content information uniform resource locator (URL);

authorize the client for access to DASH content based upon enforcing a received authentication policy; and

indicate the enforced authentication policy in the DASH MPD.

11. The server of claim 10 , wherein:

the DASH proxy is further configured to:

calculate a URL signature locally based on the DASH content URL and the authentication key; and

reject the DASH content when the locally calculated URL signature does not match the received signature.

12. The server of claim 1 , wherein the D-NAF is hosted on a network element.