DASH-aware network application function (D-NAF)

• US 9,906,526 B2
• Filed: 12/23/2013
• Issued: 02/27/2018
• Est. Priority Date: 01/17/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Oyman, Ozgur
• Primary Examiner(s): Lynch, Sharon
• Application Number:
  US14/653,779
• Publication Number:
  US 20150326572A1
• Time in Patent Office: 1,527 Days
• 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/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0869 for achieving mutual authentication cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• 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/765 intermediate
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04N 21/23439 for generating different versions
• CPC Class Codes: H04N 21/25816 involving client authentication restricting access to computer systems by authenticating users using a predetermined code G06F21/33; cryptographic authentication protocols H04L9/32; networks authentication protocols H04L63/08; authentication in wireless network security H04W12/06
• CPC Class Codes: H04N 21/41407 embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop constructional details of equipment or arrangements specially adapted for portable computer application G06F1/1626; arrangements specially adapted for mobile receivers in broadcast systems H04H20/57
• CPC Class Codes: H04N 21/4621 Controlling the complexity of the content stream or additional data, e.g. lowering the resolution or bit-rate of the video stream for a mobile client with a small screen arrangements for using the results of monitoring on user's side in broadcast systems H04H60/65; flow control in packet networks H04L47/10
• CPC Class Codes: H04N 21/6175 involving transmission via Internet broadcast-related systems characterised by the transmission system being the Internet H04H60/82
• CPC Class Codes: H04N 21/6181 involving transmission via a mobile phone network arrangements for providing broadcast or conference services to substation in data switching networks in combination with wireless systems H04L12/189; wireless uplink channel access H04W74/004
• CPC Class Codes: H04N 21/64322 IP
• CPC Class Codes: H04N 21/8456 : by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Technology for a dynamic adaptive streaming over hypertext transfer protocol (HTTP) aware (DASH-aware) network application function (D-NAF) on a server is disclosed. In an example, the D-NAF can include a network application function (NAF) for authenticating a client and a DASH proxy for delivering DASH content and authentication information for the client.

Claims

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.