Dash-aware network application function (D-NAF)

1. A server comprising a network application function (NAF), the server comprising one or more processors and memory configured to:

authenticate a client using a Generic Bootstrapping Architecture (GBA)-based authentication and authorization procedure;

authorize the client for access to dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) content subject to content-specific policy information using the GBA-based authentication and authorization procedure, wherein the content-specific policy information is for a specific bitrate or resolution of the DASH content;

receive, using the NAF, DASH authentication information for the DASH content and a DASH content information location in a media presentation description (MPD), 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, using the NAF, the client for access to the DASH content based upon the received DASH authentication information and the received DASH content information;

deliver the DASH content to the client when the client is successfully authenticated and authorized using the GBA-based authentication and authorization procedure; and

provide operator network authentication and authorization for a DASH service provider, wherein the NAF receives the content-specific policy information from the DASH service provider.

2. The server of claim 1 , wherein the one or more processors and memory are further configured to parse, using the NAF, a DASH media presentation description (MPD) for DASH content information that includes the content-specific policy information.

3. The server of claim 1 , wherein the one or more processors and memory are further configured to parse, using the NAF, a DASH media presentation description (MPD) for DASH content information that 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 1 , wherein the one or more processors and memory are further configured to:

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

retrieve, using the NAF, a content key from the BSF including a NAF key material for DASH content information.

5. The server of claim 1 , wherein the one or more processors and memory are further configured to override, using the NAF, the GAA-based authentication and authorization procedure via a bootstrapping server function (BSF) or a home subscriber subsystem (HSS).

6. The server of claim 1 , wherein the one or more processors and memory are further configured to receive, using the NAF, an authentication and authorization policy of a DASH service provider in a DASH media presentation description (MPD).

7. The server of claim 1 , wherein the one or more processors and memory are further configured to authorize, using the NAF, the client for access to the DASH content subject to a streaming plan associated with the client, wherein the streaming plan describes acceptable bitrates and resolutions for accessing the DASH content at the client.

8. The server of claim 1 , wherein the one or more processors and memory are further configured to validate, using the NAF, an integrity of delivered DASH content to ensure a defined level of content delivery accuracy.

9. The server of claim 1 , wherein the one or more processors and memory are further configured to validate, using the NAF, an integrity of a DASH media presentation description (MPD) for DASH content information.

10. The server of claim 1 , wherein the one or more processors and memory are further configured to: calculate, using the NAF, a URL signature based on the DASH content URL and the authentication key; and

reject, using the NAF, the DASH content when the calculated URL signature does not match the signature received in the DASH authentication information.

11. At least one non-transitory machine readable storage medium having instructions embodied thereon for authenticating and authorizing a client to receive dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) content, the instructions when executed by one or more processors of a server performs the following:

authenticating, at the server that includes a network application function (NAF), a client using a Generic Bootstrapping Architecture (GBA)-based authentication and authorization procedure;

authorizing, at the server that includes the NAF, the client for access to dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) content subject to content-specific policy information using the GBA-based authentication and authorization procedure, wherein the content-specific policy information is for a specific bitrate or resolution of the DASH content;

receive, using the NAF, DASH authentication information for the DASH content and a DASH content information location in a media presentation description (MPD), 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, using the NAF, the client for access to the DASH content based upon the received DASH authentication information and the received DASH content information;

delivering, from the server that includes the NAF, the DASH content to the client when the client is successfully authenticated and authorized using the GBA-based authentication and authorization procedure; and

providing, from the server that includes the NAF, operator network authentication and authorization for a DASH service provider, wherein the NAF received the content-specific policy information from the DASH service provider.

12. The at least one non-transitory machine readable storage medium of claim 11 , further comprising instructions when executed by the one or more processors performs the following: receiving an authentication and authorization policy of a DASH service provider in a DASH media presentation description (MPD).

13. The at least one non-transitory machine readable storage medium of claim 11 , further comprising instructions when executed by the one or more processors performs the following: authorizing the client for access to the DASH content subject to a streaming plan associated with the client, wherein the streaming plan describes acceptable bitrates and resolutions for accessing the DASH content at the client.

14. The at least one non-transitory machine readable storage medium of claim 11 , further comprising instructions when executed by the one or more processors performs the following: validating an integrity of delivered DASH content to ensure a defined level of content delivery accuracy.

15. The at least one non-transitory machine readable storage medium of claim 11 , further comprising instructions when executed by the one or more processors performs the following: validating an integrity of a DASH media presentation description (MPD) for DASH content information.

16. A server that includes a network application function (NAF), the server comprising one or more processors and memory configured to:

authenticate, using the NAF, a client using a Generic Bootstrapping Architecture (GBA)-based authentication and authorization procedure;

authorize, using the NAF, the client for access to dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) content subject to content-specific policy information using the GBA-based authentication and authorization procedure, wherein the content-specific policy information is for a specific bitrate or resolution of the DASH content;

receive DASH authentication information for the DASH content and a DASH content information location in a media presentation description (MPD), 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, using the NAF, the client for access to the DASH content based upon the received DASH authentication information and the received DASH content information;

deliver the DASH content to the client when the client is successfully authenticated and authorized via the NAF using the GBA-based authentication and authorization procedure; and

provide operator network authentication and authorization for a DASH service provider, wherein the NAF receives the content-specific policy information from the DASH service provider.

17. The server of claim 16 , wherein the one or more processors and memory are further configured to parse, using the NAF, a DASH media presentation description (MPD) for DASH content information that includes the content-specific policy information.

18. The server of claim 16 , wherein the one or more processors and memory are further configured to parse, using the NAF, a DASH media presentation description (MPD) for DASH content information that 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.

19. The server of claim 16 , wherein the one or more processors and memory are further configured to:

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

retrieve, using the NAF, a content key from the BSF including a NAF key material for DASH content information.

20. The server of claim 16 , wherein the one or more processors and memory are further configured to authorize, using the NAF, the client for access to the DASH content subject to a streaming plan associated with the client, wherein the streaming plan describes acceptable bitrates and resolutions for accessing the DASH content at the client.

21. The server of claim 16 , wherein the one or more processors and memory are further configured to:

validate, using the NAF, an integrity of delivered DASH content to ensure a defined level of content delivery accuracy; or

validate, using the NAF, an integrity of a DASH media presentation description (MPD) for DASH content information.