METHOD TO REQUEST DELIVERY OF A MEDIA ASSET, MEDIA SERVER, APPLICATION SERVER AND CLIENT DEVICE

• US 20070118849A1
• Filed: 11/16/2006
• Published: 05/24/2007
• Est. Priority Date: 11/18/2005
• Status: Abandoned Application

• Current Assignee: Alcatel SA (Nokia Corporation)
• Original Assignee: Alcatel SA (Nokia Corporation)
• Inventors: Robinson, David, KISEL, Andrey
• Application Number:
  US11/560,759
• Publication Number:
  US 20070118849A1
• Time in Patent Office: Days
• US Class Current: 725/25
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/062 for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04N 21/2407 Monitoring of transmitted content, e.g. distribution time, number of downloads arrangements for monitoring programmes for broadcast or for distribution combined with broadcast H04H20/14
• CPC Class Codes: H04N 21/2541 Rights Management protecting software against unauthorised usage in a vending or licensing environment G06F21/10; security in data switching network management H04L41/28; security management or policies for network security H04L63/20; access security in wireless networks H04W12/08
• CPC Class Codes: H04N 21/47202 for requesting content on demand, e.g. video on demand
• CPC Class Codes: H04N 21/84 Generation or processing of descriptive data, e.g. content descriptors systems specially adapted for using meta-information in broadcast systems H04H60/73
• CPC Class Codes: H04N 7/165 Centralised control of user terminal subsequent to an upstream request signal H04N7/17345; Registering at central by two-way working H04N7/17309

Abstract

In requesting delivery of an on-demand media asset from a media server (102)—like a request to stream a movie from a video-on-demand server—the client (101) submits to the media server (102) a token that is in advance associated with the requested media asset. The media server (102) then verifies the token against token related metadata credentials—e.g. maximum number of deliveries, expiry date, etc.—before granting the request and executing the requested operation, for example delivery of the media asset to the client (101).

Claims

1. A method for a client (101) to request delivery of a media asset to a media server (102) in an on-demand network,

CHARACTERIZED in that said client (101) submits a token in advance associated with said media asset to said media server (102), and said media server (102) verifies said token against token related metadata before delivery of said media asset.

2. A method according to claim 1,

CHARACTERIZED IN THAT said token comprises a token ID and a token signature.

3. A method according to claim 1,

CHARACTERIZED IN THAT said token is generated and associated with said media asset in advance by an application server (103).

4. A method according to claim 1,

CHARACTERIZED IN THAT said token related metadata are stored in advance in said media server (102).

5. A method according to claim 1,

CHARACTERIZED IN THAT said token related metadata comprise a maximum number of deliveries.

6. A method according to claim 1,

CHARACTERIZED IN THAT said token related metadata comprise an expiry date.

7. A method according to claim 1,

CHARACTERIZED IN THAT said token related metadata comprise a maximum duration of a single media delivery.

8. A method according to claim 1,

CHARACTERIZED IN THAT said client (101) submits said token upon challenge by said media server (102).

9. A method according to claim 1,

CHARACTERIZED IN THAT requesting delivery of a media asset entails requesting playout of said media asset.

10. A method according to claim 1,

CHARACTERIZED IN THAT requesting delivery of a media asset entails requesting restart of said media asset.

11. A method according to claim 1,

CHARACTERIZED IN THAT requesting delivery of a media asset entails requesting stopping playout of said media asset.

12. A method according to claim 1,

CHARACTERIZED IN THAT requesting delivery of a media asset entails requesting pausing playout of said media asset.

13. A method according to claim 1,

CHARACTERIZED IN THAT said media asset is a video asset or a picture asset or a game asset or a music asset.

14. A media server (102) for use in an on-demand network, able to handle a request from a client (101) for delivery of a media asset, and to deliver said media asset to said client (101),

CHARACTERIZED IN THAT

said media server (102) comprises:

a. receiving means for receiving a token from said client (101) when requesting delivery of said media asset, said token being associated in advance with said media asset; and

b. verification means for verifying said token against token related metadata before delivery of said media asset.

15. A media server (102) according to claim 14,

CHARACTERIZED IN THAT said media server further comprises:

c. storage means (104) for storing said token related metadata.

16. An application server (103) for use in an on-demand network, able to receive a request from a client (101) for delivery of a media asset,

CHARACTERIZED IN THAT

said application server (103) is operationally coupled to:

a. token generating means for generating a token and for associating said token in advance with said media asset; and

said application server (103) comprises;

b. token sharing means for sharing said token with said client (101).

17. A client device (101) for use in an on-demand network, said client device (101) being able to request delivery of a media asset to a media server (102),

CHARACTERIZED IN THAT said client device (101) further comprises:

a. means for requesting a token in advance associated with said media asset to an application server (103); and

b. means for submitting said token with said media server (102) when requesting delivery of said media asset.