In-Memory Personalized Content Delivery Architecture

• US 20140095712A1
• Filed: 09/28/2012
• Published: 04/03/2014
• Est. Priority Date: 09/28/2012
• Status: Active Grant

• Current Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Original Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Inventors: Moore, Jonathan
• Granted Patent: US 11,431,763 B2
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/765 intermediate

Abstract

A content network is presented where at least one of non-personalized data commonly applicable to a user base and personalized data is maintained. In an aspect, each element of the personalized data may be applicable to at least one, but less than all, of users within the user base. The non-personalized data may be stored across a plurality of servers included in a group, and the personalized data is stored across at least one, but less than all, of the plurality of computing devices included in the group. An update to data stored may be received and a determination made as to whether the update to data is to the non-personalized data or the personalized data. Then, one of the non-personalized data or the personalized data set stored in the server may be updated.

Claims

1. A method comprising:

maintaining in-memory at least one of non-personalized data commonly applicable to a user base and a personalized data set, where each element of the personalized data set is applicable to at least one, but less than all, of users within the user base,

wherein the non-personalized data is stored across a plurality of computing devices included in a group, and

wherein the personalized data is stored across at least one, but less than all, of the plurality of computing devices included in the group.

2. The method claim 1, further comprising maintaining in an external datastore the other of the at least one of non-personalized data commonly applicable to the user base and the personalized data set.

3. The method of claim 1, further comprising receiving a specific user request to access the personalized data and the non-personalized data stored in-memory.

4. The method of claim 3, further comprising identifying the specific user and combining the non-personalized data and the personalized data into combined data, wherein the personalized data is personalized data of the specific user.

5. The method of claim 4, further comprising designating a server of the plurality of servers as a primary server for storing the personalized data of the specific user.

6. The method of claim 5, further comprising designating at least one second server of the plurality of servers as at least one secondary server for storing the personalized data of the specific user.

7. The method of claim 6, further comprising:

receiving an update to data stored in the primary server;

identifying the update as an update to the non-personalized data; and

updating the non-personalized data in the primary server.

8. The method of claim 6, further comprising:

receiving an update to data stored in the primary server;

identifying the update as an update to the personalized data;

updating the personalized data in the primary server; and

coordinating with the at least one secondary server to update the personalized data in the at least one secondary server.

9. A method comprising:

receiving, at a computing device, an update to data stored in the computing device, the computing device being configured to maintain in-memory non-personalized data commonly applicable to a user base and a personalized data, where each element of the personalized data is applicable to at least one, but less than all, of users within the user base;

determining whether the update is an update to the non-personalized data or an update to the personalized data; and

based upon the determining, updating the non-personalized data or the personalized data set stored in the computing device,

wherein the non-personalized data is stored across a plurality of computing devices included in a group; and

wherein the personalized data is stored across at least one, but less than all, of the plurality of servers included in the group.

10. The method of claim 9, further comprising based upon determining that the update is an update to the non-personalized data, determining a position of the update in an order of updates to the server and distributing the update to the non-personalized data to all other servers of the plurality of servers.

11. The method of claim 10, further comprising updating an in-memory model of the server with the updated non-personalized data.

12. The method of claim 9, further comprising performing a hash function to locate the server maintaining the personalized data of a specific user.

13. The method of claim 12, further comprising determining at least one second server as at least one secondary server for maintaining the personalized data of the specific user.

14. The method of claim 9, further comprising coordinating an update of personalized data set stored in the at least one second server.

15. The method of claim 9, further comprising designating the server of a plurality of servers as a primary server for storing personalized data of a specific user within the user base.

16. The method of claim 15, further comprising designating at least one second server of the plurality of servers as at least one secondary server for storing the personalized data of the specific user.

17. A method comprising:

receiving, at an application computing device, a specific user request to access content;

determining personalized data of the specific user and non-personalized data associated with the content maintained in-memory at the application computing device; and

sending the content to the specific user,

wherein the non-personalized data is stored across a plurality of application computing devices included in a group, and

wherein the personalized data is stored across at least one, but less than all, of a plurality of application computing devices included in the group.

18. The method of claim 17, further comprising designating the application computing device as a primary application computing device for storing the personalized data of the specific user.

19. The method of claim 17, further comprising identifying the specific user and combining the non-personalized data and the personalized data into combined data.

20. The method of claim 17, further comprising:

receiving an update to data stored in the application computing device;

identifying the update as an update to the personalized data;

updating the personalized data in the application computing device; and

coordinating with at least one second application computing device, of the at least one, but less than all, of the plurality of application computing devices to update the personalized data in the at least one second application computing device.