Graph for data interaction

• US 10,277,704 B2
• Filed: 10/12/2016
• Issued: 04/30/2019
• Est. Priority Date: 10/13/2015
• Status: Active Grant

• Current Assignee: Home Box Office Incorporated (Warner Bros. Discovery, Inc.)
• Original Assignee: Home Box Office Incorporated (Warner Bros. Discovery, Inc.)
• Inventors: Busayarat, Sata, Bellingham, Gregory John, Furtwangler, Brandon C., Gay, Allen Arthur
• Primary Examiner(s): Chen, Yu
• Application Number:
  US15/291,247
• Publication Number:
  US 20170103553A1
• Time in Patent Office: 930 Days
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06T 1/20 Processor architectures; Processor configuration, e.g. pipelining
• CPC Class Codes: G06T 1/60 Memory management
• CPC Class Codes: G06T 11/206 Drawing of charts or graphs
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/55 Testing of service level quality, e.g. simulating service usage
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04N 21/251 Learning process for intelligent management, e.g. learning user preferences for recommending movies details of learning user preferences for the retrieval of video data in a video database G06F16/739; computer systems using learning methods G06N3/08
• CPC Class Codes: H04N 21/43 : Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware real-time communication protocols in data switching networks H04L65/00
• CPC Class Codes: H04N 21/4332 : by placing content in organized collections, e.g. local EPG data repository interfaces, Database management systems or updating for information retrieval G06F16/23; details of retrieval of video data and associated meta data in video database G06F16/739
• CPC Class Codes: H04N 21/4821 : using a grid, e.g. sorted out by channel and broadcast time
• CPC Class Codes: H04N 21/4826 : using recommendation lists, e.g. of programs or channels sorted out according to their score

Abstract

The described technology is directed towards having user interface objects rendered on a client device based upon provider data of at least part of a client provider graph. The client provider graph comprises a plurality of providers (graph nodes), in which each provider has provider data corresponding to user interface object data. The data of one provider has a reference set containing one or more references (e.g., edges) that each identify another provider, thus forming the graph. Client requests for other provider data are made based upon the reference set. The other provider data is received in response to the client requests, and is maintained at the client (e.g., in a client cache) to build the client graph.

Claims

1. A method comprising:

building a client provider graph comprising a plurality of providers, each provider having provider data, including accessing the data of one provider, the data of the one provider including a reference set containing one or more references that each identify another provider, making a client request for other provider data corresponding to the one or more of the other providers identified in the reference set, and receiving the other provider data in response to the client request;

rendering one or more user interface objects based upon provider data of at least part of the client provider graph; and

maintaining provider information in a client cache, comprising maintaining a first provider in a dehydrated state corresponding to needing at least some provider data, maintaining a second provider in a partially hydrated state corresponding to having provider data in an unparsed provider data form, and maintaining a third provider in a hydrated state corresponding to having data in a parsed object form.

2. The method of claim 1 wherein making the client request for the other provider data comprises communicating with a data service.

3. The method of claim 1 wherein the other provider data corresponds to at least two providers identified in the reference set, and wherein making the client request comprises making a requestor batch request.

4. The method of claim 3 further comprising, returning a batch response to the requestor batch request, including building one part of the batch response with provider data from the client cache, and communicating with a data service to obtain provider data for another part of the batch response.

5. The method of claim 1 wherein making the client request for the other provider data comprises batching a plurality of requests into a batch request to a data service, and receiving a streamed response from the data service corresponding to the batch request.

6. The method of claim 1 wherein making the client request for the other provider data comprises multiplexing the client request with another client request for a same provider into a multiplexed request to a data service, receiving a response corresponding to the multiplexed request from the data service, and de-multiplexing the response to return one response to the client request and another response to the other client request.

7. The method of claim 1 further comprising, receiving expanded data in response to the client request, the expanded data corresponding to a provider that was not requested in the client request.

8. The method of claim 7 further comprising, maintaining the expanded data corresponding to the provider in a partially hydrated state in the client cache.

9. The method of claim 8 further comprising, parsing the expanded data in the partially hydrated state into object data in a hydrated state, and maintaining the object data in the hydrated state in the client cache.

10. A system comprising:

a client software platform on a client device, the client software platform including;

a request manager, the request manager configured to communicate with a data service to obtain one or more providers from the data service, each provider including associated provider data;

a cache coupled to the request manager to maintain the providers obtained by the request manager, in which at least some of the providers each include a reference set in its associated provider data that references one or more other providers, to form a client graph, the cache configured to maintain a first provider in a dehydrated state corresponding to needing at least some provider data, maintain a second provider in a partially hydrated state corresponding to having provider data in an unparsed provider data form, and maintain a third provider in a hydrated state corresponding to having data in a parsed object form; and

a plurality of user interface objects, including a user interface object that corresponds to a provider, the user interface object configured to request data associated with its corresponding provider, and to receive and use its provider'"'"'s associated data to display a rendered representation of at least one user interface element on a user interface, and to request one or more other providers based upon a reference set in its corresponding provider'"'"'s associated data.

11. The system of claim 10 wherein the user interface object is coupled to the request manager to request provider data, and to respond to the request, the request manager obtains the provider data from the cache if the provider data is cached, and obtains the provider data from the data service if not cached.

12. The system of claim 10 wherein the request manager batches and multiplexes a plurality of requests to the data service.

13. The system of claim 10 wherein the request manager batches a plurality of provider requests to the data service in a single batch request, and receives at least two streamed responses from the data service in response to the single batch request.

14. The system of claim 10 wherein in response to a request for an identified provider from the batch manager to the data service, the data service returns the provider and an expanded provider that is not identified in the request.

15. The system of claim 14 wherein the expanded provider is cached in a partially hydrated state until data of that expanded provider is requested by a user interface object.

16. One or more non-transitory machine-readable storage media having machine-executable instructions, which when executed perform operations, the operations comprising:

maintaining a plurality of providers, in which at least some of the providers each contain a reference set that references at least one other provider to form a graph of providers, wherein maintaining the plurality of providers comprises maintaining, in a client cache, a first provider in a dehydrated state corresponding to needing at least some provider data, maintaining a second provider in a partially hydrated state corresponding to having provider data in an unparsed provider data form, and maintaining a third provider in a hydrated state corresponding to having data in a parsed object form;

making a client request for provider data corresponding to an identified provider, the request including a provider identifier; and

receiving the provider data for the identified provider in a response to the request, in which the response includes provider data including the identified provider'"'"'s identifier and other provider data of the identified provider, the other provider data including a reference set comprising at least one reference to another provider.

17. The one or more non-transitory machine-readable storage media of claim 16 wherein the operations further comprise, selecting another identified provider from the reference set, and making another client request for the other identified provider.

18. The one or more non-transitory machine-readable storage media of claim 16 wherein the operations further comprise, caching the provider data in the client cache, including determining a cache location based upon the provider identifier, and writing at least some of the provider data to the cache location.

19. The one or more non-transitory machine-readable storage media of claim 16 wherein making the client request for the provider data comprises including the request as part of a batch request to a data service, and wherein receiving the response comprises receiving the provider data in a streamed partial response to the batch request from the data service.