Method of using tokens and policy descriptors for dynamic on demand session management

• US 10,230,799 B2
• Filed: 07/15/2013
• Issued: 03/12/2019
• Est. Priority Date: 12/16/2005
• Status: Active Grant

• Current Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Original Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Inventors: Mao, Weidong, Black, Neville A., Compton, Charles L.
• Primary Examiner(s): Neurauter, Jr., George C
• Application Number:
  US13/942,680
• Publication Number:
  US 20130304854A1
• Time in Patent Office: 2,066 Days
• Field of Search: 709231, 709229, 709219, 709225, 709227, 705 52, 705 59, 705 54, 705 57, 705 50, 726 9, 713182, 713185, 713156, 725 88, 725 95, 370328
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 65/1066 Session management
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• 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/2543 Billing , e.g. for subscription services payment schemes, architectures or protocols G06Q20/00; e-commerce G06Q30/00; arrangements for billing for the use of broadcast information or broadcast-related information H04H60/21
• CPC Class Codes: H04N 21/2747 Remote storage of video programs received via the downstream path, e.g. from the server
• CPC Class Codes: H04N 21/47202 for requesting content on demand, e.g. video on demand
• CPC Class Codes: H04N 21/8355 involving usage data, e.g. number of copies or viewings allowed
• 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

Tokens and policy descriptors are used for dynamic on demand session management in a distributed and scalable architecture for on demand sessions and resource management. The architecture includes an on demand client, a purchase server, and a session manager. A purchase token is generated at the purchase server and assigned to the on demand client. The purchase token represents at least one requested asset. In response to an on demand session set-up request corresponding to the purchase token from the on demand client to the session manager, the purchase token is expanded to generate at least one dynamic policy management descriptor for the on demand session. This provides token-based purchase authorization and policy management for on demand services.

Claims

1. A method comprising:

receiving, in a first session, a first request by a user, the first request indicating a token;

determining, based at least in part on the token, a first transmission control protocol type;

determining, based at least in part on the token and the first transmission control protocol type, by a system comprising at least one computing device, a first one or more content assets;

causing, by the system, at least one of the first one or more content assets to be sent via a network;

receiving, in a second session different from the first session, a second request by the user, the second request indicating the token;

determining, based at least in part on the token indicated by the second request, by the system, a second one or more content assets different from the first one or more content assets; and

causing, by the system, at least one of the second one or more content assets to be sent via the network.

2. The method of claim 1, further comprising determining based at least in part on the token, a second transmission control protocol type different from the first transmission control protocol type, wherein the determining the second one or more content assets comprises determining the second one or more content assets further based in part on the second transmission control protocol type.

3. The method of claim 1, further comprising determining based at least in part on the token, a first bandwidth, wherein the causing the at least one of the first one or more content assets to be sent comprises sending the at least one of the first one or more content assets within the first bandwidth.

4. The method of claim 3, further comprising determining based at least in part on the token, a second bandwidth different from the first bandwidth, wherein the causing the at least one of the second one or more content assets to be sent comprises sending the at least one of the second one or more content assets within the second bandwidth.

5. The method of claim 1, wherein the first one or more content assets comprises a first plurality of content assets, the method further comprising generating, based at least in part on the token indicated by the first request, a first asset list descriptor that indicates start times of the first plurality of content assets.

6. The method of claim 5, wherein the second one or more content assets comprises a second plurality of content assets, the method further comprising generating, based at least in part on the token indicated by the second request, a second asset list descriptor different from the first asset list descriptor, wherein the second asset list descriptor indicates start times of the second plurality of content assets, at least some of the start times of the second plurality of content assets being different from at least some of the start times of the first plurality of content assets.

7. The method of claim 1, wherein the causing the at least one of the first one or more content assets to be sent comprises causing the at least one of the first one or more content assets to be sent via the network to a client device, and wherein the causing the at least one of the second one or more content assets to be sent comprises causing the at least one of the second one or more content assets to be sent via the network to the client device.

8. A method comprising:

receiving, in a first session, a first request by a user, the first request indicating a token;

determining, based at least in part on the token indicated by the first request, a first codec;

determining, based at least in part on the token indicated by the first request, by a system comprising at least one computing device, a first one or more content assets;

sending, by the system and via a network, at least one of the first one or more content assets encoded by the first codec;

receiving, in a second session different from the first session, a second request by the user, the second request indicating the token;

determining, based at least in part on the token indicated by the second request, by the system, a second one or more content assets different from the first one or more content assets; and

causing, by the system, at least one of the second one or more content assets to be sent via the network.

9. The method of claim 8, further comprising determining based at least in part on the token indicated by the second request, a second codec different from the first codec, wherein the causing the at least one of the second one or more content assets to be sent comprises sending the at least one of the second one or more content assets encoded by the second codec.

10. A method comprising:

sending to a user, by a system comprising at least one computing device, a message indicating a token, the token being associated with a content asset;

based at least in part on receiving, from the user, a request indicating the token, determining, by the system, a plurality of content assets including the content asset associated with the token;

determining, based at least in part on the token indicated by the request, a codec;

encoding, by the system and using the codec, the plurality of content assets;

determining, by the system and based at least in part on the token, start times of the plurality of content assets; and

causing, by the system, at least some of the plurality of content assets to be sent via a network in accordance with corresponding one of the start times.

11. The method of claim 10, further comprising determining, based at least in part on the token, a transmission control protocol type, wherein the causing the at least some of the plurality of content assets to be sent comprises sending the at least some of the plurality of content assets via the network based on the transmission control protocol type.

12. The method of claim 10, wherein the determining the plurality of content assets and the determining the start times are performed based at least in part on the request.

13. The method of claim 10, further comprising determining, based at least in part on the token, a bandwidth, wherein the causing the at least some of the plurality of content assets to be sent comprises sending the at least some of the plurality of content assets within the bandwidth.

14. A method comprising:

sending to a user, by a system comprising at least one computing device, an indication of a token;

based on each of a plurality of requests from the user in different sessions indicating the token, processing, by the system, information associated with the token; and

for each of the plurality of requests in each of the different sessions;

determining, by the system and based at least in part on the token, one or more content assets different from one or more content assets determined for a remainder of the requests;

determining, by the system and based at least in part on the token, a codec different from one or more codecs determined for the remainder of the requests; and

causing, by the system, at least one of the one or more content assets determined for request and encoded by the codec determined for the request to be sent via a network.

15. The method of claim 14, further comprising, for at least some of the plurality of requests:

determining, for at least one of the plurality of requests, a bandwidth based at least in part on the token, wherein the causing the at least one of the one or more content assets to be sent comprises causing the at least one of the one or more content assets to be sent within the bandwidth.

16. The method of claim 14, further comprising, for each of the plurality of requests:

determining, based at least in part on the token, a transmission control protocol type different from one or more transmission control protocol types determined for the remainder of the requests, wherein the causing the at least one of the one or more content assets to be sent comprises causing the at least one of the one or more content assets to be sent based on the transmission control protocol type different from one or more transmission control protocol types determined for the remainder of the requests.

17. The method of claim 14, wherein for each of the plurality of requests, the different one or more content assets comprises a different plurality of content assets, the method further comprising:

determining, based at least in part on the token, for each of the plurality of requests, an asset list descriptor, wherein each of the asset list descriptors indicates start times of the plurality of content assets determined for the requests; and

sending, for each of the plurality of requests, a respective one of the plurality of content assets at corresponding ones of the start times associated with the plurality of content assets.