Data request multiplexing

• US 10,044,832 B2
• Filed: 08/30/2016
• Issued: 08/07/2018
• Est. Priority Date: 08/30/2016
• Status: Active Grant

• Current Assignee: Home Box Office Incorporated (Warner Bros. Discovery, Inc.)
• Original Assignee: Home Box Office Incorporated (Warner Bros. Discovery, Inc.)
• Inventors: Gay, Allen Arthur, Busayarat, Sata
• Primary Examiner(s): Nguyen, Quang N
• Application Number:
  US15/252,166
• Publication Number:
  US 20180063280A1
• Time in Patent Office: 707 Days
• Field of Search: 709203, 709213, 709217, 709219, 709223, 709224, 709226, 709228, 709231, 709232, 709238, 707737, 714 13, 455519
• 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/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/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

Abstract

The described technology is generally directed towards combining (multiplexing) two or more pending data requests for the same data item into a single request that is sent to a data providing entity such as a back-end data service. Described is maintaining a mapping of the requests to requesting entities so that a single response to a multiplexed request having data for a requested data item may be re-associated (de-multiplexed) to each requesting entity that requested that data item. Also described is batching a plurality of requests, which may include one or more multiplexed requests, into a batch request sent to a data providing entity.

Claims

1. A method comprising:

receiving a first request for data associated with a first data identifier from a first requesting entity;

maintaining mapping information for the first request that associates the first data identifier with the first requesting entity;

receiving a second request for the data associated with the first data identifier from a second requesting entity;

maintaining mapping information for the second request that associates the first data identifier with the second requesting entity;

determining that the first data identifier applies to the first request and to the second request;

requesting the data associated with the first data identifier from a data-providing entity in a multiplexed request;

receiving a response to the multiplexed request from the data-providing entity, the response including the data associated with the first data identifier;

returning a first response to the first request, including accessing the mapping information to include the data associated with the first data identifier in the first response;

returning a second response to the second request, including accessing the mapping information to include the data associated with the first data identifier in the second response;

adding the first data identifier to a pending set, and wherein determining that the first data identifier applies to the first request and the second request comprises detecting the first data identifier in the pending set as being present in the second request; and

determining that no other request needs a response that includes the data associated with the first data identifier, and removing the first data identifier from the pending set.

2. The method of claim 1 further comprising, receiving a third request for data associated with the first data identifier from a third requesting entity before removing the first data identifier from the pending set, and returning a third response to the third request that includes the data associated with the first data identifier in the third response.

3. The method of claim 1 wherein requesting the data associated with the first data identifier in the multiplexed request comprises including the multiplexed request as part of a batch request, and communicating the batch request to the data-providing entity.

4. The method of claim 3 wherein including the multiplexed request as part of the batch request comprises adding the multiplexed request to a batch buffer, and further comprising, adding the first data identifier to a pending set in conjunction with adding the multiplexed request to the batch buffer.

5. The method of claim 1 wherein the first request is part of a batch request from a client requesting entity, and further comprising, building a batch response that includes the data associated with the first data identifier and other data associated with at least one other identifier, and wherein returning the first response to the first request comprises returning the batch response.

6. The method of claim 1 further comprising, breaking the multiplexed request into a plurality of corresponding sub-requests, and reassembling responses to the plurality of corresponding sub-requests into a response to the request.

7. The method of claim 6 further comprising, multiplexing a sub-request with at least one other matching sub-request to obtain a single response to the multiplexed sub-request, and de-multiplexing the single response into sub-responses to the sub-request and to the at least one other matching sub-request.

8. The method of claim 6 further comprising, responding to at least one sub-request from data in a cache.

9. A system comprising:

a request handling entity that receives requests for data items from requesting entities;

a request manager of the request handling entity, the request manager including;

a request multiplexer that that maintains a set of zero or more pending requests, and for each request for a data item, associates that data item request with its requesting entity in a map, and evaluates the set of pending data item requests to not request that data item more than once from a data-providing entity when another request for that data item is pending; and

a request de-multiplexer that de-multiplexes responses from the data-providing entity, including for each data item received in each response, to access the map to re-associate that data item with each requesting entity that requested the data item for returning in a response to that requesting entity;

wherein the request manager further comprises a batching process coupled to the request multiplexer, the batching process configured to combine a plurality of requests for data items from the request multiplexer into a batch request to the data-providing entity;

wherein the request multiplexer considers another request for a data item to not be pending if an already pending request for that data item has been pending too long.

10. The system of claim 9 wherein the requesting entities comprise clients, wherein the request handling entity comprises a front-end data service, and wherein the data-providing entity comprises a back-end data service.

11. The system of claim 9 wherein the requesting entities comprise front-end data servers, wherein the request handling entity comprises a back-end data service, and wherein the data-providing entity comprises one or more backing data stores.

12. The system of claim 9 wherein a data item is requested as part of a batch request from a requesting entity.

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

receiving a first request for a first data item from a first requestor;

maintaining a mapping that associates the first requestor with the first request;

determining for the first request whether another request for the first data item is already pending, and if not, adding an identifier of the first data item to a pending set and making a single request for the first data item to a data-providing entity, and if so, awaiting a response to the other request for the first data item;

receiving a second request for the first data item from a second requestor;

maintaining a mapping that associates the second requestor with the second request;

determining for the second request that a request for the first data item is already pending, and awaiting a response to the other request for the first data item;

receiving response data corresponding to the single request for the first data item;

accessing the mapping to return the response data received for the first data item in a response to the first request from the first requestor;

accessing the mapping to return the response data received for the first data item in a response to the second request from the second requestor; and

determining that no other request needs a response that includes the data associated with the first data identifier, and removing the first data identifier from the pending set;

wherein making the single request for the first data item comprises adding an identifier of the first data item to a batch request, and sending the batch request to the data-providing entity.

14. The non-transitory one or more machine-readable storage media of claim 13 having further machine-executable instructions comprising breaking the request for the first data item into a plurality of sub-requests.