System and method for accessing private digital content

• US 9,071,593 B2
• Filed: 10/15/2010
• Issued: 06/30/2015
• Est. Priority Date: 10/26/2009
• Status: Active Grant

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Vrancken, Bart, Theeten, Bart
• Primary Examiner(s): Le, David
• Application Number:
  US13/502,187
• Publication Number:
  US 20120210448A1
• Time in Patent Office: 1,719 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources

Abstract

A system, method and computer program product for providing access to private digital content are disclosed. The private digital content is owned by an owner and installed on a content server and access is provided to a first client which is capable of rendering said digital content. Predetermined information required for gaining authorized access to said content server by said first client is generated by a second client. The predetermined information is transferred from said second client to said first client then used by said first client to get access to said private digital content.

Claims

1. A method for providing access to private digital content, owned by an owner and installed on a content server, to a digital media player (DMP) which is capable of rendering said digital content but not capable of generating authentication information, comprising the steps of:

sending DMP specific information from the DMP to a digital media controller (DMC);

receiving authentication information generated by the DMC from said DMP credentials, said authentication information required for gaining authorized access to private digital content on said content server;

using said authentication information by said DMP to request a first token from the content server;

using the first token to request approval for access to the private digital content from the owner;

sending the first token and the DMP specific information to the DMC for the generation of second authentication information;

using the second authentication to request a second token from the content server; and

using the second token to access the private digital content from the content server.

2. A method according to claim 1, wherein said authentication information is dependent on DMC specific information.

3. A method according to claim 1, wherein said authentication information comprises owner specific information.

4. A method according to claim 1, wherein said authentication information is generated by the DMC from said DMP specific information using one or more standard Open Authentication calls.

5. A method according to claim 1, wherein said authentication information is generated by the DMC from said DMP specific information by interacting with a content management server.

6. A computer program product embodied on a non-transitory computer readable medium a digital media player (DMP) which is capable of rendering said digital content but not capable of generating authentication information, said computer program product comprising:

computer code for transferring DMP specific information from said DMP to a digital media controller (DMC);

computer code for receiving authentication information generated by said DMC from said DMP specific information, said authentication information required for gaining authorized access to private digital content on a content server by said DMP;

computer code for using said authentication information by said DMP to request a first token from the content server;

computer code for using the first token, by the DMP, to get access to the private digital content from the owner;

computer code for sending the first token and the DMP specific information to the DMC for the generation of second authentication information;

computer code for using the second authentication to request a second token from the content server; and

computer code for using the second token to access the private digital content from the content server.

7. The computer program product as recited in claim 6, wherein said authentication information is dependent on DMC specific information.

8. The computer program product as recited in claim 6, wherein said authentication information comprises owner specific information.

9. The computer program product as recited in claim 6, wherein said authentication information is generated by the DMC from said DMP specific information using one or more standard Open Authentication calls.

10. The computer program product as recited in claim 6, wherein said authentication information is generated by the DMC from said DMP specific information by interacting with a content management server.

15. The DMP as recited in claim 6, wherein said authentication information is generated by the DMC from said DMP specific information by interacting with a content management server.

11. A digital media player (DMP) for rendering private digital content installed on a content server and protected by authentication information, the DMP lacking authentication capabilities, said DMP is configured to perform the following steps:

transferring DMP specific information from said DMP to a digital media controller (DMC) capable of generating authentication information;

receiving authentication information generated by said DMC from said DMP specific information, said authentication information required for gaining access to said private digital content;

using said authentication information by said DMP to request a first token from the content server;

using the first token, by the DMP, to get access to the private digital content from an owner of the private digital content;

transferring the first token and the DMP specific information to the DMC for the generation of second authentication information;

requesting, by the DMP, a second token from the content server; and

using the second token to get access to the private digital content from the content server.

12. The DMP as recited in claim 11, wherein said authentication information is dependent on DMC specific information.

13. The DMP as recited in claim 11, wherein said authentication information comprises owner specific information.

14. The DMP as recited in claim 11, wherein said information is generated by the DMC from said DMP specific information using one or more standard Open Authentication calls.